From: Paolo Bonzini <pbonzini@redhat.com>
To: xiaoqiang zhao <zxq_yx_007@163.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, agraf@suse.de, michael@walle.cc,
edgar.iglesias@gmail.com, cornelia.huck@de.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3 2/4] hw/char: QOM'ify etraxfs_ser.c
Date: Tue, 17 May 2016 14:51:29 +0200 [thread overview]
Message-ID: <573B13D1.2070805@redhat.com> (raw)
In-Reply-To: <1463108878-15956-3-git-send-email-zxq_yx_007@163.com>
On 13/05/2016 05:07, xiaoqiang zhao wrote:
> * Drop the old SysBus init function and use instance_init
> * Call qemu_chr_add_handlers in the realize callback
> * Use qdev chardev prop instead of qemu_char_get_next_serial
>
> Signed-off-by: xiaoqiang zhao <zxq_yx_007@163.com>
> ---
> hw/char/etraxfs_ser.c | 27 +++++++++++++++++----------
> 1 file changed, 17 insertions(+), 10 deletions(-)
>
> diff --git a/hw/char/etraxfs_ser.c b/hw/char/etraxfs_ser.c
> index 146b387..6957c68 100644
> --- a/hw/char/etraxfs_ser.c
> +++ b/hw/char/etraxfs_ser.c
> @@ -159,6 +159,11 @@ static const MemoryRegionOps ser_ops = {
> }
> };
>
> +static Property etraxfs_ser_properties[] = {
> + DEFINE_PROP_CHR("etraxfs-serial", ETRAXSerial, chr),
The usual name for this property is "chardev".
> + DEFINE_PROP_END_OF_LIST(),
> +};
> +
> static void serial_receive(void *opaque, const uint8_t *buf, int size)
> {
> ETRAXSerial *s = opaque;
> @@ -209,40 +214,42 @@ static void etraxfs_ser_reset(DeviceState *d)
>
> }
>
> -static int etraxfs_ser_init(SysBusDevice *dev)
> +static void etraxfs_ser_init(Object *obj)
> {
> - ETRAXSerial *s = ETRAX_SERIAL(dev);
> + ETRAXSerial *s = ETRAX_SERIAL(obj);
> + SysBusDevice *dev = SYS_BUS_DEVICE(obj);
>
> sysbus_init_irq(dev, &s->irq);
> - memory_region_init_io(&s->mmio, OBJECT(s), &ser_ops, s,
> + memory_region_init_io(&s->mmio, obj, &ser_ops, s,
> "etraxfs-serial", R_MAX * 4);
> sysbus_init_mmio(dev, &s->mmio);
> +}
> +
> +static void etraxfs_ser_realize(DeviceState *dev, Error **errp)
> +{
> + ETRAXSerial *s = ETRAX_SERIAL(dev);
>
> - /* FIXME use a qdev chardev prop instead of qemu_char_get_next_serial() */
> - s->chr = qemu_char_get_next_serial();
> if (s->chr) {
> qemu_chr_add_handlers(s->chr,
> serial_can_receive, serial_receive,
> serial_event, s);
> }
> - return 0;
> }
>
> static void etraxfs_ser_class_init(ObjectClass *klass, void *data)
> {
> DeviceClass *dc = DEVICE_CLASS(klass);
> - SysBusDeviceClass *k = SYS_BUS_DEVICE_CLASS(klass);
>
> - k->init = etraxfs_ser_init;
> dc->reset = etraxfs_ser_reset;
> - /* Reason: init() method uses qemu_char_get_next_serial() */
> - dc->cannot_instantiate_with_device_add_yet = true;
> + dc->props = etraxfs_ser_properties;
> + dc->realize = etraxfs_ser_realize;
> }
>
> static const TypeInfo etraxfs_ser_info = {
> .name = TYPE_ETRAX_FS_SERIAL,
> .parent = TYPE_SYS_BUS_DEVICE,
> .instance_size = sizeof(ETRAXSerial),
> + .instance_init = etraxfs_ser_init,
> .class_init = etraxfs_ser_class_init,
> };
>
>
I'm sorry, this is not enough. You need to learn how to test this
device. CRIS images are available at http://wiki.qemu.org/Testing.
You have not added a replacement for the call to
qemu_char_get_next_serial(). The board code in hw/cris/axis_dev88.c
needs to use qemu_char_get_next_serial().
I suggest creating a function like
void etraxfs_ser_create(hwaddr addr, qemu_irq irq,
CharDriverState *chr) {
DeviceState *dev;
SysBusDevice *s;
qemu_irq irq;
dev = qdev_create(NULL, "extrafs,serial");
s = SYS_BUS_DEVICE(dev);
qdev_prop_set_chr(s, "chardev", chr);
qdev_init_nofail(dev);
sysbus_mmio_map(s, 0, addr);
sysbus_connect_irq(s, 0, irq);
}
and using it with qemu_char_get_next_serial() as the "chr" parameter.
Note that this code is untested.
Thanks,
Paolo
next prev parent reply other threads:[~2016-05-17 12:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 3:07 [Qemu-devel] [PATCH v3 0/4] QOM'ify hw/char devices xiaoqiang zhao
2016-05-13 3:07 ` [Qemu-devel] [PATCH v3 1/4] hw/char: QOM'ify escc.c xiaoqiang zhao
2016-05-13 3:07 ` [Qemu-devel] [PATCH v3 2/4] hw/char: QOM'ify etraxfs_ser.c xiaoqiang zhao
2016-05-17 12:51 ` Paolo Bonzini [this message]
2016-05-18 10:33 ` xiaoqiang zhao
2016-05-13 3:07 ` [Qemu-devel] [PATCH v3 3/4] hw/char: QOM'ify lm32_juart.c xiaoqiang zhao
2016-05-13 3:07 ` [Qemu-devel] [PATCH v3 4/4] hw/char: QOM'ify lm32_uart.c xiaoqiang zhao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=573B13D1.2070805@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=cornelia.huck@de.ibm.com \
--cc=edgar.iglesias@gmail.com \
--cc=michael@walle.cc \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=zxq_yx_007@163.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.