GPIO/IRQ QOMification: Phase 2 - Getting rid of SYSBUS IRQs
v2 cover GPIO/IRQ QOMification: Phase 2 - Getting rid of SYSBUS IRQs
Hi All,
So phase one was the QOMification of qemu_irq. This is the next step. We start to setup GPIOs as proper QOM objects. Inputs are child objects of their device. Outputs are settable Links and connection is made via proper setting of a QOM link.
We then cleanup Sysbus to simply re-use device level GPIOs and get rid of it's special IRQ handling code.
Depends of my pending QOM array property stuff (the "[*]" series):
https://lists.nongnu.org/archive/html/qemu-devel/2014-07/msg04116.html
Changed since v1:
Addressed Alex review
Dropped IRQ g_new0 changes
Peter Crosthwaite (14):
qdev: gpio: Don't allow name share between I and O
qdev: gpio: Register GPIO inputs as child objects
qdev: gpio: Register GPIO outputs as QOM links
qmp: qstring: Handle NULL strings
qom: Allow clearing of a Link property
qom: Demote already-has-a-parent to a regular error
qdev: gpio: Re-impement qdev_connect_gpio QOM style
qdev: gpio: Add API for intercepting a GPIO qtest/irq: Rework IRQ interception
irq: Remove qemu_irq_intercept_out
qdev: gpio: delete NamedGPIOList::out
qdev: gpio: Remove qdev_init_gpio_out x1 restriction
qdev: gpio: Define qdev_pass_gpios()
sysbus: Use TYPE_DEVICE GPIO functionality
hw/core/irq.c | 8 +---- hw/core/qdev.c | 90 ++++++++++++++++++++++++++++++++++++++++++++++---- hw/core/sysbus.c | 20 ++--------- include/hw/irq.h | 1 - include/hw/qdev-core.h | 6 +++- include/hw/sysbus.h | 6 ++-- qobject/qstring.c | 12 ++++--- qom/object.c | 10 ++++-- qtest.c | 15 ++++++--- 9 files changed, 120 insertions(+), 48 deletions(-)
Signature · 1 line
2.0.1.1.gfbfc394
PATCH v2 1/14 qdev: gpio: Don't allow name share between I and O
Only allow a GPIO name to be one or the other. Inputs and outputs are functionally different and should be in different namespaces. Prepares support for the QOMification of IRQs as Links or Child objects.
The alternative is to munge names .e.g. with "-in" or "-out" suffixes when giving QOM names. But that reduces clarity and if there are cases out there where users want I and O with same name they can manually add their own suffixes.
---
hw/core/qdev.c | 2 ++ 1 file changed, 2 insertions(+)
hw/core/qdev.c +2 -0
@@ -339,6 +339,7 @@ void qdev_init_gpio_in_named(DeviceState *dev, qemu_irq_handler handler, {NamedGPIOList *gpio_list =qdev_get_named_gpio_list (dev, name); +assert (gpio_list->num_out ==0 || !name); gpio_list->in =qemu_extend_irqs (gpio_list->in, gpio_list->num_in, handler, dev, n); gpio_list->num_in += n;
@@ -354,6 +355,7 @@ void qdev_init_gpio_out_named(DeviceState *dev, qemu_irq *pins, {NamedGPIOList *gpio_list =qdev_get_named_gpio_list (dev, name); +assert (gpio_list->num_in ==0 || !name);assert (gpio_list->num_out ==0 ); gpio_list->num_out = n; gpio_list->out = pins;
Signature · 1 line
2.0.1.1.gfbfc394
PATCH v2 2/14 qdev: gpio: Register GPIO inputs as child objects
In reply to Peter CrosthwaiteTo the device that contains them. This will allow for referencing a GPIO input from it's canonical path (exciting for dynamic machine generation!)
---
Define propname variable at start of function.
hw/core/qdev.c | 9 +++++++++ 1 file changed, 9 insertions(+)
hw/core/qdev.c +9 -0
@@ -337,11 +337,20 @@ static NamedGPIOList *qdev_get_named_gpio_list(DeviceState *dev,void qdev_init_gpio_in_named (DeviceState *dev,qemu_irq_handler handler,const char *name,int n) { +int i;NamedGPIOList *gpio_list =qdev_get_named_gpio_list (dev, name); +char *propname =g_strdup_printf ("%s[*]" , name ? name :"unnamed-gpio-in" );assert (gpio_list->num_out ==0 || !name); gpio_list->in =qemu_extend_irqs (gpio_list->in, gpio_list->num_in, handler, dev, n); + +for (i = gpio_list->num_in; i < gpio_list->num_in + n; i++) { +object_property_add_child (OBJECT (dev), propname, +OBJECT (gpio_list->in[i]), &error_abort); + } +g_free (propname); + gpio_list->num_in += n; }
Signature · 1 line
2.0.1.1.gfbfc394
PATCH v2 3/14 qdev: gpio: Register GPIO outputs as QOM links
In reply to Peter CrosthwaiteWithin the object that contains the GPIO output. This allows for connecting GPIO outputs via setting of a Link property.
Also clear the link value to zero. This catch-alls the case where a device improperly inits a gpio_out (malloc instead of malloc0).
---
Changed since v1:
Clear the irq when initing the GPIO.
Define propname at start of function.
hw/core/qdev.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
hw/core/qdev.c +12 -0
@@ -362,12 +362,24 @@ void qdev_init_gpio_in(DeviceState *dev, qemu_irq_handler handler, int n)void qdev_init_gpio_out_named (DeviceState *dev,qemu_irq *pins,const char *name,int n) { +int i;NamedGPIOList *gpio_list =qdev_get_named_gpio_list (dev, name); +char *propname =g_strdup_printf ("%s[*]" , name ? name :"unnamed-gpio-out" );assert (gpio_list->num_in ==0 || !name);assert (gpio_list->num_out ==0 ); gpio_list->num_out = n; gpio_list->out = pins; + +for (i =0 ; i < n; ++i) { +memset (&pins[i],0 ,sizeof (*pins)); +object_property_add_link (OBJECT (dev), propname,TYPE_IRQ , + (Object **)&pins[i], + object_property_allow_set_link, +OBJ_PROP_LINK_UNREF_ON_RELEASE , + &error_abort); + } +g_free (propname); }void qdev_init_gpio_out (DeviceState *dev,qemu_irq *pins,int n)
Signature · 1 line
2.0.1.1.gfbfc394
PATCH v2 4/14 qmp: qstring: Handle NULL strings
In reply to Peter CrosthwaiteCreate a valid qobject even if the input string is null. qstring->string will be NULL and length will be 0.
This prepares support for clearing of QOM Link properties where NULL canonical path string will be passes through this API.
---
qobject/qstring.c | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-)
qobject/qstring.c +7 -5
@@ -48,14 +48,16 @@ QString *qstring_from_substr(const char *str, int start, int end) {QString *qstring; - qstring =g_malloc (sizeof (*qstring)); + qstring =g_malloc0 (sizeof (*qstring)); qstring->length = end - start +1 ; qstring->capacity = qstring->length; - qstring->string =g_malloc (qstring->capacity +1 ); -memcpy (qstring->string, str + start, qstring->length); - qstring->string[qstring->length] =0 ; +if (str) { + qstring->string =g_malloc (qstring->capacity +1 ); +memcpy (qstring->string, str + start, qstring->length); + qstring->string[qstring->length] =0 ; + }QOBJECT_INIT (qstring, &qstring_type);
@@ -69,7 +71,7 @@ QString *qstring_from_substr(const char *str, int start, int end)*/ QString *qstring_from_str (const char *str) { -return qstring_from_substr (str,0 ,strlen (str) -1 ); +return qstring_from_substr (str,0 , (str ?strlen (str) :0 ) -1 ); }static void capacity_increase (QString *qstring,size_t len)
Signature · 1 line
2.0.1.1.gfbfc394
PATCH v2 5/14 qom: Allow clearing of a Link property
In reply to Peter CrosthwaiteBy passing in NULL to object_property_set_link.
The lead user of this is the QDEV GPIO framework which will implement GPIO disconnects via an "unlink".
---
qom/object.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
qom/object.c +2 -2
@@ -881,7 +881,7 @@ char *object_property_get_str(Object *obj, const char *name,void object_property_set_link (Object *obj,Object *value,const char *name,Error **errp) { -gchar *path =object_get_canonical_path (value); +gchar *path = value ?object_get_canonical_path (value) :NULL ;object_property_set_str (obj, path, name, errp);g_free (path); }
@@ -1172,7 +1172,7 @@ static void object_set_link_property(Object *obj, Visitor *v, void *opaque,visit_type_str (v, &path, name, &local_err); -if (!local_err &&strcmp (path,"" ) !=0 ) { +if (!local_err && path &&strcmp (path,"" ) !=0 ) { new_target =object_resolve_link (obj, name, path, &local_err); }
Signature · 1 line
2.0.1.1.gfbfc394
PATCH v2 6/14 qom: Demote already-has-a-parent to a regular error
In reply to Peter CrosthwaiteRather than an abort(). This allows callers to decide whether parenting an already-parented object is a fatal error condition.
Useful for providing a default value for an object's parent in the case where you want to set one iff it doesn't already have one.
---
qom/object.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
qom/object.c +5 -1
@@ -1074,6 +1074,11 @@ void object_property_add_child(Object *obj, const char *name,gchar *type;ObjectProperty *op; +if (child->parent !=NULL ) { +error_setg (errp,"child object is already parented" ); +return ; + } + type =g_strdup_printf ("child<%s>" ,object_get_typename (OBJECT (child))); op = object_property_add(obj, name, type, object_get_child_property, NULL,
@@ -1085,7 +1090,6 @@ void object_property_add_child(Object *obj, const char *name, op->resolve = object_resolve_child_property;object_ref (child); -g_assert (child->parent ==NULL ); child->parent = obj; out:
Signature · 1 line
2.0.1.1.gfbfc394
PATCH v2 7/14 qdev: gpio: Re-impement qdev_connect_gpio QOM style
In reply to Peter CrosthwaiteRe-implement as a link setter. This should allow the QOM framework to keep track of ref counts properly etc.
We need to add a default parent for the connecting input incase it's coming from a non-qdev source. We simply parent the IRQ to the machine in this case.
---
hw/core/qdev.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
hw/core/qdev.c +8 -4
@@ -403,10 +403,14 @@ qemu_irq qdev_get_gpio_in(DeviceState *dev, int n)void qdev_connect_gpio_out_named (DeviceState *dev,const char *name,int n,qemu_irq pin) { -NamedGPIOList *gpio_list =qdev_get_named_gpio_list (dev, name); - -assert (n >=0 && n < gpio_list->num_out); - gpio_list->out[n] = pin; +char *propname =g_strdup_printf ("%s[%d]" , + name ? name :"unnamed-gpio-out" , n); +if (pin) { +object_property_add_child (qdev_get_machine (),"non-qdev-gpio[*]" , +OBJECT (pin),NULL ); + } +object_property_set_link (OBJECT (dev),OBJECT (pin), propname, &error_abort); +g_free (propname); }void qdev_connect_gpio_out (DeviceState * dev,int n,qemu_irq pin)
Signature · 1 line
2.0.1.1.gfbfc394
PATCH v2 8/14 qdev: gpio: Add API for intercepting a GPIO
In reply to Peter CrosthwaiteTo replace the old qemu_irq intercept API (which had users reaching into qdev private state for GPIOs).
---
changed since v1 (Alex review):
Accept an alredy inited qemu_irq as arg and return the disconnected (allow arbitrary opaque setting).
s/irq/gpio in commit msg
hw/core/qdev.c | 25 +++++++++++++++++++++++++ include/hw/qdev-core.h | 2 ++ 2 files changed, 27 insertions(+)
hw/core/qdev.c +25 -0
@@ -413,6 +413,31 @@ void qdev_connect_gpio_out_named(DeviceState *dev, const char *name, int n,g_free (propname); } +/* disconnect a GPIO ouput, returning the disconnected input (if any) */ + +static qemu_irq qdev_disconnect_gpio_out_named (DeviceState *dev, +const char *name,int n) +{ +char *propname =g_strdup_printf ("%s[%d]" , + name ? name :"unnamed-gpio-out" , n); + +qemu_irq ret = (qemu_irq )object_property_get_link (OBJECT (dev), propname, +NULL ); +if (ret) { +object_property_set_link (OBJECT (dev),NULL , propname,NULL ); + } +g_free (propname); +return ret; +} + +qemu_irq qdev_intercept_gpio_out (DeviceState *dev,qemu_irq icpt, +const char *name,int n) +{ +qemu_irq disconnected =qdev_disconnect_gpio_out_named (dev, name, n); +qdev_connect_gpio_out_named (dev, name, n, icpt); +return disconnected; +} +void qdev_connect_gpio_out (DeviceState * dev,int n,qemu_irq pin) {qdev_connect_gpio_out_named (dev,NULL , n, pin);
include/hw/qdev-core.h +2 -0
@@ -274,6 +274,8 @@ qemu_irq qdev_get_gpio_in_named(DeviceState *dev, const char *name, int n);void qdev_connect_gpio_out (DeviceState *dev,int n,qemu_irq pin);void qdev_connect_gpio_out_named (DeviceState *dev,const char *name,int n,qemu_irq pin); +qemu_irq qdev_intercept_gpio_out (DeviceState *dev,qemu_irq icpt, +const char *name,int n);BusState *qdev_get_child_bus (DeviceState *dev,const char *name);
Signature · 1 line
2.0.1.1.gfbfc394
PATCH v2 9/14 qtest/irq: Rework IRQ interception
In reply to Peter CrosthwaiteChange the qtest intercept handler to accept just the individual IRQ being intercepted as opaque. n is still expected to be correctly set as for the original intercepted irq. qemu_intercept_irq_in is updated accordingly.
Then covert the qemu_irq_intercept_out call to use qdev intercept version. This stops qtest from having to mess with the raw IRQ pointers (still has to mess with names and counts but a step in the right direction).
---
changed since v1:
Create IRQ before intercept call and add extra layer of indirection on opaque data.
hw/core/irq.c | 2 +- qtest.c | 15 +++++++++++---- 2 files changed, 12 insertions(+), 5 deletions(-)
hw/core/irq.c +1 -1
@@ -140,7 +140,7 @@ void qemu_irq_intercept_in(qemu_irq *gpio_in, qemu_irq_handler handler, int n)for (i =0 ; i < n; i++) { *old_irqs[i] = *gpio_in[i]; gpio_in[i]->handler = handler; - gpio_in[i]->opaque = old_irqs; + gpio_in[i]->opaque = &old_irqs[i]; } }
qtest.c +11 -4
@@ -200,8 +200,8 @@ static void GCC_FMT_ATTR(2, 3) qtest_send(CharDriverState *chr,static void qtest_irq_handler (void *opaque,int n,int level) { -qemu_irq *old_irqs = opaque; -qemu_set_irq (old_irqs[n], level); +qemu_irq old_irq = *(qemu_irq *)opaque; +qemu_set_irq (old_irq, level);if (irq_levels[n] != level) {CharDriverState *chr = qtest_chr;
@@ -263,8 +263,15 @@ static void qtest_process_command(CharDriverState *chr, gchar **words)continue ; }if (words[0 ][14 ] =='o' ) { -qemu_irq_intercept_out (&ngl->out, qtest_irq_handler, - ngl->num_out); +int i; +for (i =0 ; i < ngl->num_out; ++i) { +qemu_irq *disconnected =g_new0 (qemu_irq,1 ); +qemu_irq icpt =qemu_allocate_irq (qtest_irq_handler, + disconnected, i); + + *disconnected =qdev_intercept_gpio_out (dev, icpt, + ngl->name, i); + } }else {qemu_irq_intercept_in (ngl->in, qtest_irq_handler, ngl->num_in);
Signature · 1 line
2.0.1.1.gfbfc394
PATCH v2 10/14 irq: Remove qemu_irq_intercept_out
In reply to Peter CrosthwaiteNo more users left and obsoleted by qdev_intercept_gpio_out.
---
hw/core/irq.c | 6 ------ include/hw/irq.h | 1 - 2 files changed, 7 deletions(-)
hw/core/irq.c +0 -6
@@ -144,12 +144,6 @@ void qemu_irq_intercept_in(qemu_irq *gpio_in, qemu_irq_handler handler, int n) } } -void qemu_irq_intercept_out (qemu_irq **gpio_out,qemu_irq_handler handler,int n) -{ -qemu_irq *old_irqs = *gpio_out; - *gpio_out =qemu_allocate_irqs (handler, old_irqs, n); -} -static const TypeInfo irq_type_info = { .name =TYPE_IRQ , .parent =TYPE_OBJECT ,
include/hw/irq.h +0 -1
@@ -61,6 +61,5 @@ qemu_irq *qemu_irq_proxy(qemu_irq **target, int n);/* For internal use in qtest. Similar to qemu_irq_split, but operating on an existing vector of qemu_irq. */ void qemu_irq_intercept_in (qemu_irq *gpio_in,qemu_irq_handler handler,int n); -void qemu_irq_intercept_out (qemu_irq **gpio_out,qemu_irq_handler handler,int n);#endif
Signature · 1 line
2.0.1.1.gfbfc394
PATCH v2 11/14 qdev: gpio: delete NamedGPIOList::out
In reply to Peter CrosthwaiteAll users of GPIO outputs are fully QOMified, using QOM properties to access the GPIO data. Delete.
---
hw/core/qdev.c | 1 - include/hw/qdev-core.h | 1 - 2 files changed, 2 deletions(-)
hw/core/qdev.c +0 -1
@@ -369,7 +369,6 @@ void qdev_init_gpio_out_named(DeviceState *dev, qemu_irq *pins,assert (gpio_list->num_in ==0 || !name);assert (gpio_list->num_out ==0 ); gpio_list->num_out = n; - gpio_list->out = pins;for (i =0 ; i < n; ++i) {memset (&pins[i],0 ,sizeof (*pins));
include/hw/qdev-core.h +0 -1
@@ -137,7 +137,6 @@ struct NamedGPIOList {char *name;qemu_irq *in;int num_in; -qemu_irq *out;int num_out;QLIST_ENTRY (NamedGPIOList) node; };
Signature · 1 line
2.0.1.1.gfbfc394
PATCH v2 12/14 qdev: gpio: Remove qdev_init_gpio_out x1 restriction
In reply to Peter CrosthwaitePreviously this was restricted to a single call per-dev/per-name. With the conversion of the GPIO output state to QOM the implementation can now handle repeated calls. Remove the restriction.
---
hw/core/qdev.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
hw/core/qdev.c +1 -2
@@ -367,8 +367,7 @@ void qdev_init_gpio_out_named(DeviceState *dev, qemu_irq *pins,char *propname =g_strdup_printf ("%s[*]" , name ? name :"unnamed-gpio-out" );assert (gpio_list->num_in ==0 || !name); -assert (gpio_list->num_out ==0 ); - gpio_list->num_out = n; + gpio_list->num_out += n;for (i =0 ; i < n; ++i) {memset (&pins[i],0 ,sizeof (*pins));
Signature · 1 line
2.0.1.1.gfbfc394
PATCH v2 13/14 qdev: gpio: Define qdev_pass_gpios()
In reply to Peter CrosthwaiteAllows a container to take ownership of GPIOs in a contained device and automatically connect them as GPIOs to the container.
This prepares for deprecation of the SYSBUS IRQ functionality, which has this feature. We push it up to the device level instead of sysbus level. There's nothing sysbus specific about passing GPIOs to containers so its a legitimate device-level generic feature.
---
changed since v1:
Variablised ? : string expressions (Alex review).
hw/core/qdev.c | 26 ++++++++++++++++++++++++++ include/hw/qdev-core.h | 3 +++ 2 files changed, 29 insertions(+)
hw/core/qdev.c +26 -0
@@ -441,6 +441,32 @@ void qdev_connect_gpio_out(DeviceState * dev, int n, qemu_irq pin)qdev_connect_gpio_out_named (dev,NULL , n, pin); } +void qdev_pass_gpios (DeviceState *dev,DeviceState *container, +const char *name) +{ +int i; +NamedGPIOList *ngl =qdev_get_named_gpio_list (dev, name); + +for (i =0 ; i < ngl->num_in; i++) { +const char *nm = ngl->name ? ngl->name :"unnamed-gpio-in" ; +char *propname =g_strdup_printf ("%s[%d]" , nm, i); + +object_property_add_alias (OBJECT (container), propname, +OBJECT (dev), propname, + &error_abort); + } +for (i =0 ; i < ngl->num_out; i++) { +const char *nm = ngl->name ? ngl->name :"unnamed-gpio-out" ; +char *propname =g_strdup_printf ("%s[%d]" , nm, i); + +object_property_add_alias (OBJECT (container), propname, +OBJECT (dev), propname, + &error_abort); + } +QLIST_REMOVE (ngl, node); +QLIST_INSERT_HEAD (&container->gpios, ngl, node); +} +BusState *qdev_get_child_bus (DeviceState *dev,const char *name) {BusState *bus;
include/hw/qdev-core.h +3 -0
@@ -289,6 +289,9 @@ void qdev_init_gpio_in_named(DeviceState *dev, qemu_irq_handler handler,void qdev_init_gpio_out_named (DeviceState *dev,qemu_irq *pins,const char *name,int n); +void qdev_pass_gpios (DeviceState *dev,DeviceState *container, +const char *name); +BusState *qdev_get_parent_bus (DeviceState *dev);/*** BUS API. ***/
Signature · 1 line
2.0.1.1.gfbfc394
PATCH v2 14/14 sysbus: Use TYPE_DEVICE GPIO functionality
In reply to Peter CrosthwaiteRe-implement the Sysbus GPIOs to use the existing TYPE_DEVICE GPIO named framework. A constant string name is chosen to avoid conflicts with existing unnamed GPIOs.
This unifies GPIOs are IRQs for sysbus devices and allows removal of all Sysbus state for GPIOs.
Any existing and future-added functionality for GPIOs is now also available for sysbus IRQs.
---
Changed since v1:
Named each IRQ individually.
hw/core/sysbus.c | 20 +++----------------- include/hw/sysbus.h | 6 +++--- 2 files changed, 6 insertions(+), 20 deletions(-)
hw/core/sysbus.c +3 -17
@@ -41,11 +41,7 @@ static const TypeInfo system_bus_info = {void sysbus_connect_irq (SysBusDevice *dev,int n,qemu_irq irq) { -assert (n >=0 && n < dev->num_irq); - dev->irqs[n] =NULL ; -if (dev->irqp[n]) { - *dev->irqp[n] = irq; - } +qdev_connect_gpio_out_named (DEVICE (dev),SYSBUS_DEVICE_GPIO_IRQ , n, irq); } static void sysbus_mmio_map_common(SysBusDevice *dev, int n, hwaddr addr,
@@ -89,22 +85,13 @@ void sysbus_mmio_map_overlap(SysBusDevice *dev, int n, hwaddr addr,/* Request an IRQ source. The actual IRQ object may be populated later. */ void sysbus_init_irq (SysBusDevice *dev,qemu_irq *p) { -int n; - -assert (dev->num_irq <QDEV_MAX_IRQ ); - n = dev->num_irq++; - dev->irqp[n] = p; +qdev_init_gpio_out_named (DEVICE (dev), p,SYSBUS_DEVICE_GPIO_IRQ ,1 ); }/* Pass IRQs from a target device. */ void sysbus_pass_irq (SysBusDevice *dev,SysBusDevice *target) { -int i; -assert (dev->num_irq ==0 ); - dev->num_irq = target->num_irq; -for (i =0 ; i < dev->num_irq; i++) { - dev->irqp[i] = target->irqp[i]; - } +qdev_pass_gpios (DEVICE (target),DEVICE (dev),SYSBUS_DEVICE_GPIO_IRQ ); }void sysbus_init_mmio (SysBusDevice *dev,MemoryRegion *memory)
@@ -210,7 +197,6 @@ static void sysbus_dev_print(Monitor *mon, DeviceState *dev, int indent)hwaddr size;int i; -monitor_printf (mon,"%*sirq %d\n" , indent,"" , s->num_irq);for (i =0 ; i < s->num_mmio; i++) { size =memory_region_size (s->mmio[i].memory); monitor_printf(mon, "%*smmio " TARGET_FMT_plx "/" TARGET_FMT_plx "\n",
include/hw/sysbus.h +3 -3
@@ -8,7 +8,6 @@#define QDEV_MAX_MMIO 32#define QDEV_MAX_PIO 32 -#define QDEV_MAX_IRQ 512#define TYPE_SYSTEM_BUS "System"#define SYSTEM_BUS (obj) OBJECT_CHECK(IDEBus, (obj), TYPE_IDE_BUS)
@@ -33,6 +32,9 @@ typedef struct SysBusDevice SysBusDevice;* SysBusDeviceClass is not overriding #DeviceClass.realize, so derived * classes overriding it are not required to invoke its implementation. */ + +#define SYSBUS_DEVICE_GPIO_IRQ "sysbus-irq" + typedef struct SysBusDeviceClass { /*< private >*/ DeviceClass parent_class;
@@ -47,8 +49,6 @@ struct SysBusDevice {/*< public >*/ int num_irq; -qemu_irq irqs[QDEV_MAX_IRQ ]; -qemu_irq *irqp[QDEV_MAX_IRQ ];int num_mmio;struct {hwaddr addr;
Signature · 1 line
2.0.1.1.gfbfc394
Re: [Qemu-devel] [PATCH v2 14/14] sysbus: Use TYPE_DEVICE GPIO functionality
Quoted 37 lines · Peter Crosthwaite
Re-implement the Sysbus GPIOs to use the existing
TYPE_DEVICEGPIO named framework. A constant string name is chosen to avoid conflicts with existing unnamed GPIOs.This unifies GPIOs are IRQs for sysbus devices and allows removal of all Sysbus state for GPIOs.
Any existing and future-added functionality for GPIOs is now also available for sysbus IRQs.
Signed-off-by Peter Crosthwaite <[email protected]>---
Changed since v1:
Named each IRQ individually.hw/core/sysbus.c | 20 +++----------------- include/hw/sysbus.h | 6 +++--- 2 files changed, 6 insertions(+), 20 deletions(-)hw/core/sysbus.c +1
-5@@ -41,11 +41,7 @@ static const TypeInfo system_bus_info = {void sysbus_connect_irq (SysBusDevice *dev,int n,qemu_irq irq) { -assert (n >=0 && n < dev->num_irq); - dev->irqs[n] =NULL ; -if (dev->irqp[n]) { - *dev->irqp[n] = irq; - } +qdev_connect_gpio_out_named (DEVICE (dev),SYSBUS_DEVICE_GPIO_IRQ , n, irq); } static void sysbus_mmio_map_common(SysBusDevice *dev, int n, hwaddr addr,
hw/core/sysbus.c void sysbus_mmio_map_overlap(SysBusDevice *dev, int n, hwaddr addr, · line 95
Quoted 7 lines
hw/core/sysbus.c +0
-4@@ -89,22 +85,13 @@ void sysbus_mmio_map_overlap(SysBusDevice *dev, int n, hwaddr addr,/* Request an IRQ source. The actual IRQ object may be populated later. */ void sysbus_init_irq (SysBusDevice *dev,qemu_irq *p) { -int n; - -assert (dev->num_irq <QDEV_MAX_IRQ ); - n = dev->num_irq++;
This renders dev->num_irq to always stay 0. Better remove it from the header.
Alex
Quoted 10 lines · Peter Crosthwaite
Hi All,
So phase one was the QOMification of
qemu_irq. This is the next step. We start to setup GPIOs as proper QOM objects. Inputs are child objects of their device. Outputs are settable Links and connection is made via proper setting of a QOM link.We then cleanup Sysbus to simply re-use device level GPIOs and get rid of it's special IRQ handling code.
Quoted 7 lines
Depends of my pending QOM array property stuff (the "[*]" series):
https://lists.nongnu.org/archive/html/qemu-devel/2014-07/msg04116.html
Changed since v1:
Addressed Alex review
Dropped IRQg_new0changes
Alex
Ping!
Andreas, are you able to take this?
Regards,
Peter
Quoted 26 lines · Alexander Graf
Quoted 10 lines · Peter Crosthwaite
Hi All,
So phase one was the QOMification of
qemu_irq. This is the next step. We start to setup GPIOs as proper QOM objects. Inputs are child objects of their device. Outputs are settable Links and connection is made via proper setting of a QOM link.We then cleanup Sysbus to simply re-use device level GPIOs and get rid of it's special IRQ handling code.
Quoted 7 lines
Depends of my pending QOM array property stuff (the "[*]" series):
https://lists.nongnu.org/archive/html/qemu-devel/2014-07/msg04116.html
Changed since v1:
Addressed Alex review
Dropped IRQg_new0changesReviewed-by Alexander Graf <[email protected]>Alex
Quoted 10 lines · Peter Crosthwaite
Hi All,
So phase one was the QOMification of
qemu_irq. This is the next step. We start to setup GPIOs as proper QOM objects. Inputs are child objects of their device. Outputs are settable Links and connection is made via proper setting of a QOM link.We then cleanup Sysbus to simply re-use device level GPIOs and get rid of it's special IRQ handling code.
Quoted 7 lines
Depends of my pending QOM array property stuff (the "[*]" series):
https://lists.nongnu.org/archive/html/qemu-devel/2014-07/msg04116.html
Changed since v1:
Addressed Alex review
Dropped IRQg_new0changes
With this patch set applied, the e500 machine fails to start:
$ ./ppc-softmmu/qemu-system-ppc -M ppce500 -nographic qemu-system-ppc: attempt to add duplicate property 'sysbus-irq[*]' to object (type 'openpic') Aborted
Alex
Quoted 21 lines · Alexander Graf
Quoted 10 lines · Peter Crosthwaite
Hi All,
So phase one was the QOMification of
qemu_irq. This is the next step. We start to setup GPIOs as proper QOM objects. Inputs are child objects of their device. Outputs are settable Links and connection is made via proper setting of a QOM link.We then cleanup Sysbus to simply re-use device level GPIOs and get rid of it's special IRQ handling code.
Quoted 7 lines
Depends of my pending QOM array property stuff (the "[*]" series):
https://lists.nongnu.org/archive/html/qemu-devel/2014-07/msg04116.html
Changed since v1:
Addressed Alex review
Dropped IRQg_new0changes
Quoted 6 lines
With this patch set applied, the e500 machine fails to start:
$ ./ppc-softmmu/qemu-system-ppc -M ppce500 -nographic qemu-system-ppc: attempt to add duplicate property 'sysbus-irq[*]' to object (type 'openpic') Aborted
Andreas pointed me to his qom-next branch where patches were that apparently are a prerequisite (doh, I should've read the cover letter).
Sorry for the fuss, it works like a charm ;).
Alex
Quoted 31 lines · Alexander Graf
Quoted 21 lines · Alexander Graf
Quoted 10 lines · Peter Crosthwaite
Hi All,
So phase one was the QOMification of
qemu_irq. This is the next step. We start to setup GPIOs as proper QOM objects. Inputs are child objects of their device. Outputs are settable Links and connection is made via proper setting of a QOM link.We then cleanup Sysbus to simply re-use device level GPIOs and get rid of it's special IRQ handling code.
Quoted 7 lines
Depends of my pending QOM array property stuff (the "[*]" series):
https://lists.nongnu.org/archive/html/qemu-devel/2014-07/msg04116.html
Changed since v1:
Addressed Alex review
Dropped IRQg_new0changesQuoted 6 lines
With this patch set applied, the e500 machine fails to start:
$ ./ppc-softmmu/qemu-system-ppc -M ppce500 -nographic qemu-system-ppc: attempt to add duplicate property 'sysbus-irq[*]' to object (type 'openpic') Aborted
Quoted 4 lines
Andreas pointed me to his qom-next branch where patches were that apparently are a prerequisite (doh, I should've read the cover letter).
Sorry for the fuss, it works like a charm ;).
Can I expect this to land upstream anytime soon? :)
Alex