From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Damien Hedde <damien.hedde@greensocs.com>, qemu-devel@nongnu.org
Cc: edgar.iglesias@xilinx.com, peter.maydell@linaro.org,
alistair@alistair23.me, mark.burton@greensocs.com,
saipava@xilinx.com, qemu-arm@nongnu.org, pbonzini@redhat.com,
konrad@adacore.com, luc.michel@greensocs.com
Subject: Re: [Qemu-devel] [PATCH v5 4/9] qdev-clock: introduce an init array to ease the device construction
Date: Wed, 3 Oct 2018 10:23:39 +0200 [thread overview]
Message-ID: <37f8bd6e-d4fa-76bd-ae9f-dfd4f856cf3c@redhat.com> (raw)
In-Reply-To: <20181002142443.30976-5-damien.hedde@greensocs.com>
On 02/10/2018 16:24, Damien Hedde wrote:
> Introduce a function and macro helpers to setup several clocks
> in a device from a static array description.
>
> An element of the array describes the clock (name and direction) as
> well as the related callback and an optional offset to store the
> created object pointer in the device state structure.
>
> The array must be terminated by a special element QDEV_CLOCK_END.
>
> This is based on the original work of Frederic Konrad.
>
> Signed-off-by: Damien Hedde <damien.hedde@greensocs.com>
> ---
> include/hw/qdev-clock.h | 67 +++++++++++++++++++++++++++++++++++++++++
> hw/core/qdev-clock.c | 26 ++++++++++++++++
> 2 files changed, 93 insertions(+)
>
> diff --git a/include/hw/qdev-clock.h b/include/hw/qdev-clock.h
> index d76aa9f479..fba907dee2 100644
> --- a/include/hw/qdev-clock.h
> +++ b/include/hw/qdev-clock.h
> @@ -59,4 +59,71 @@ void qdev_connect_clock(DeviceState *dev, const char *name,
> DeviceState *driver, const char *driver_name,
> Error **errp);
>
> +/**
> + * ClockInitElem:
> + * @name: name of the clock (can't be NULL)
> + * @output: indicates whether the clock is input or output
> + * @callback: for inputs, optional callback to be called on clock's update
> + * with device as opaque
> + * @offset: optional offset to store the clock pointer in device'state
... to store the the ClockIn or ClockOut pointer in device state
> + * structure (0 means unused)
> + */
> +struct ClockPortInitElem {
> + const char *name;
> + bool output;
Maybe name this 'is_output'
> + ClockCallback *callback;
> + size_t offset;
> +};
> +
> +#define clock_offset_value(_type, _devstate, _field) \
> + (offsetof(_devstate, _field) + \
> + type_check(_type *, typeof_field(_devstate, _field)))
> +
> +#define QDEV_CLOCK(_output, _type, _devstate, _field, _callback) { \
Ditto.
> + .name = (stringify(_field)), \
> + .output = _output, \
> + .callback = _callback, \
> + .offset = clock_offset_value(_type, _devstate, _field), \
> +}
> +
> +/**
> + * QDEV_CLOCK_(IN|OUT):
> + * @_devstate: structure type. @dev argument of qdev_init_clocks below must be
> + * a pointer to that same type.
> + * @_field: a field in @_devstate (must be ClockIn* or ClockOut*)
> + * @_callback: (for input only) callback (or NULL) to be called with the device
> + * state as argument
> + *
> + * The name of the clock will be derived from @_field
> + */
> +#define QDEV_CLOCK_IN(_devstate, _field, _callback) \
> + QDEV_CLOCK(false, ClockIn, _devstate, _field, _callback)
> +
> +#define QDEV_CLOCK_OUT(_devstate, _field) \
> + QDEV_CLOCK(true, ClockOut, _devstate, _field, NULL)
> +
> +/**
> + * QDEV_CLOCK_IN_NOFIELD:
> + * @_name: name of the clock
> + * @_callback: callback (or NULL) to be called with the device state as argument
> + */
> +#define QDEV_CLOCK_IN_NOFIELD(_name, _callback) { \
> + .name = _name, \
> + .output = false, \
> + .callback = _callback, \
> + .offset = 0, \
> +}
> +
> +#define QDEV_CLOCK_END { .name = NULL }
> +
> +typedef struct ClockPortInitElem ClockPortInitArray[];
> +
> +/**
> + * qdev_init_clocks:
> + * @dev: the device to add clocks
> + * @clocks: a QDEV_CLOCK_END-terminated array which contains the
> + * clocks information.
> + */
> +void qdev_init_clocks(DeviceState *dev, const ClockPortInitArray clocks);
> +
> #endif /* QDEV_CLOCK_H */
> diff --git a/hw/core/qdev-clock.c b/hw/core/qdev-clock.c
> index f0e4839aed..08afe3983d 100644
> --- a/hw/core/qdev-clock.c
> +++ b/hw/core/qdev-clock.c
> @@ -138,3 +138,29 @@ void qdev_connect_clock(DeviceState *dev, const char *name,
>
> clock_connect(ncl->in , drv_ncl->out);
> }
> +
> +void qdev_init_clocks(DeviceState *dev, const ClockPortInitArray clocks)
> +{
> + const struct ClockPortInitElem *elem;
> +
> + assert(dev);
> + assert(clocks);
> +
> + for (elem = &clocks[0]; elem->name != NULL; elem++) {
> + /* offset cannot be inside the DeviceState part */
> + assert(elem->offset == 0 || elem->offset > sizeof(DeviceState));
> + if (elem->output) {
> + ClockOut *clk;
> + clk = qdev_init_clock_out(dev, elem->name);
> + if (elem->offset) {
> + *(ClockOut **)(((void *) dev) + elem->offset) = clk;
> + }
> + } else {
> + ClockIn *clk;
> + clk = qdev_init_clock_in(dev, elem->name, elem->callback, dev);
> + if (elem->offset) {
> + *(ClockIn **)(((void *) dev) + elem->offset) = clk;
> + }
> + }
> + }
> +}
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2018-10-03 8:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 14:24 [Qemu-devel] [PATCH v5 0/9] Clock framework API Damien Hedde
2018-10-02 14:24 ` [Qemu-devel] [PATCH v5 1/9] hw/core/clock-port: introduce clock port objects Damien Hedde
2018-10-02 23:53 ` Philippe Mathieu-Daudé
2018-10-02 14:24 ` [Qemu-devel] [PATCH v5 2/9] qdev: add clock input&output support to devices Damien Hedde
2018-10-02 23:36 ` Philippe Mathieu-Daudé
2018-10-02 14:24 ` [Qemu-devel] [PATCH v5 3/9] qdev-monitor: print the device's clock with info qtree Damien Hedde
2018-10-02 22:42 ` Philippe Mathieu-Daudé
2018-10-12 10:20 ` Damien Hedde
2018-10-02 14:24 ` [Qemu-devel] [PATCH v5 4/9] qdev-clock: introduce an init array to ease the device construction Damien Hedde
2018-10-03 8:23 ` Philippe Mathieu-Daudé [this message]
2018-10-02 14:24 ` [Qemu-devel] [PATCH v5 5/9] docs/clocks: add device's clock documentation Damien Hedde
2018-10-02 23:48 ` Philippe Mathieu-Daudé
2018-10-03 8:18 ` Philippe Mathieu-Daudé
2018-10-02 14:24 ` [Qemu-devel] [PATCH v5 6/9] hw/misc/zynq_slcr: use standard register definition Damien Hedde
2018-10-04 17:24 ` Alistair Francis
2018-10-02 14:24 ` [Qemu-devel] [PATCH v5 7/9] hw/misc/zynq_slcr: add clock generation for uarts Damien Hedde
2018-10-02 23:10 ` Philippe Mathieu-Daudé
2018-10-12 13:24 ` Damien Hedde
2018-10-12 13:27 ` Peter Maydell
2018-10-02 14:24 ` [Qemu-devel] [PATCH v5 8/9] hw/char/cadence_uart: add clock support Damien Hedde
2018-10-02 23:26 ` Philippe Mathieu-Daudé
2018-10-12 13:42 ` Damien Hedde
2018-10-02 14:24 ` [Qemu-devel] [PATCH v5 9/9] hw/arm/xilinx_zynq: connect uart clocks to slcr Damien Hedde
2018-10-02 23:28 ` Philippe Mathieu-Daudé
2018-10-04 16:13 ` [Qemu-devel] [PATCH v5 0/9] Clock framework API Philippe Mathieu-Daudé
2018-10-11 16:20 ` Damien Hedde
2018-10-11 16:23 ` Peter Maydell
2018-10-11 17:00 ` Philippe Mathieu-Daudé
2018-10-11 17:12 ` Peter Maydell
2018-10-11 17:16 ` Philippe Mathieu-Daudé
2018-10-12 15:26 ` Damien Hedde
2018-10-16 15:48 ` Peter Maydell
2018-12-18 15:24 ` Damien Hedde
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=37f8bd6e-d4fa-76bd-ae9f-dfd4f856cf3c@redhat.com \
--to=philmd@redhat.com \
--cc=alistair@alistair23.me \
--cc=damien.hedde@greensocs.com \
--cc=edgar.iglesias@xilinx.com \
--cc=konrad@adacore.com \
--cc=luc.michel@greensocs.com \
--cc=mark.burton@greensocs.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=saipava@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).