From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Igor Mitsyanko <i.mitsyanko@gmail.com>,
Alistair Francis <alistair@alistair23.me>,
QEMU Developers <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/3] hw/dma/pl330: Factor out pl330_init() from hw/arm/xilinx_zynq.c
Date: Tue, 30 Oct 2018 14:01:31 +0100 [thread overview]
Message-ID: <2aba69a5-c466-b94c-0d83-3f4fd9d1722c@redhat.com> (raw)
In-Reply-To: <CAFEAcA_6mDdxVU_TY583uOTgAX_eT-s52QRCDWTd0_uCrUTwhA@mail.gmail.com>
On 30/10/18 13:42, Peter Maydell wrote:
> On 30 October 2018 at 11:28, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>> On 30/10/18 10:36, Peter Maydell wrote:
>>>
>>> On 29 October 2018 at 23:20, Philippe Mathieu-Daudé <philmd@redhat.com>
>>> wrote:
>>>>
>>>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>>>> ---
>>>> MAINTAINERS | 1 +
>>>> hw/arm/xilinx_zynq.c | 18 ++----------------
>>>> hw/dma/pl330.c | 2 +-
>>>> include/hw/dma/pl330.h | 41 +++++++++++++++++++++++++++++++++++++++++
>>>> 4 files changed, 45 insertions(+), 17 deletions(-)
>>>> create mode 100644 include/hw/dma/pl330.h
>>>
>>>
>>>> +static inline void pl330_init(uint32_t base, qemu_irq irq, int nreq)
>>>> +{
>>>> + SysBusDevice *busdev;
>>>> + DeviceState *dev;
>>>> +
>>>> + dev = qdev_create(NULL, TYPE_PL330);
>>>> + qdev_prop_set_uint8(dev, "num_chnls", 8);
>>>> + qdev_prop_set_uint8(dev, "num_periph_req", nreq);
>>>> + qdev_prop_set_uint8(dev, "num_events", 16);
>>>> + qdev_prop_set_uint8(dev, "data_width", 64);
>>>> + qdev_prop_set_uint8(dev, "wr_cap", 8);
>>>> + qdev_prop_set_uint8(dev, "wr_q_dep", 16);
>>>> + qdev_prop_set_uint8(dev, "rd_cap", 8);
>>>> + qdev_prop_set_uint8(dev, "rd_q_dep", 16);
>>>> + qdev_prop_set_uint16(dev, "data_buffer_dep", 256);
>>>> + qdev_init_nofail(dev);
>>>
>>>
>>> These are the settings the Xilinx board uses, but are
>>> they really the settings every SoC that has a PL330 will use ?
>>
>>
>> Except "num_periph_req", all are pl330_properties defaults.
>
> If they're all the device's defaults there's not much point
> in setting them by hand. But my point is that the reason they're
> properties is that in the real hardware these are configurable
> values in the RTL. So any given SoC model needs to be able to
> set them appropriately. Having a helper function that doesn't
> let you set them makes it too easy for people modelling SoCs
> not to think about the question, I think...
Yes, I understood and agree.
I now respined v2 without this.
Thanks for your review!
Phil.
>
> thanks
> -- PMM
>
next prev parent reply other threads:[~2018-10-30 13:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 23:20 [Qemu-devel] [PATCH 0/3] hw/arm/exynos4: Add DMA support for SMDKC210 board Philippe Mathieu-Daudé
2018-10-29 23:20 ` [Qemu-devel] [PATCH 1/3] hw/arm/xilinx_zynq: Use the ARRAY_SIZE macro Philippe Mathieu-Daudé
2018-10-29 23:47 ` Alistair Francis
2018-10-30 8:16 ` Richard Henderson
2018-10-29 23:20 ` [Qemu-devel] [PATCH 2/3] hw/dma/pl330: Factor out pl330_init() from hw/arm/xilinx_zynq.c Philippe Mathieu-Daudé
2018-10-29 23:49 ` Alistair Francis
2018-10-30 8:18 ` Richard Henderson
2018-10-30 8:35 ` Philippe Mathieu-Daudé
2018-10-30 9:36 ` Peter Maydell
2018-10-30 11:28 ` Philippe Mathieu-Daudé
2018-10-30 12:42 ` Peter Maydell
2018-10-30 13:01 ` Philippe Mathieu-Daudé [this message]
2018-10-30 11:26 ` Philippe Mathieu-Daudé
2018-10-29 23:21 ` [Qemu-devel] [PATCH 3/3] arm: exynos4: Add dma support for smdkc210 Philippe Mathieu-Daudé
2018-10-29 23:47 ` Alistair Francis
2018-10-31 4:06 ` [Qemu-devel] [PATCH 0/3] hw/arm/exynos4: Add DMA support for SMDKC210 board no-reply
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=2aba69a5-c466-b94c-0d83-3f4fd9d1722c@redhat.com \
--to=philmd@redhat.com \
--cc=alistair@alistair23.me \
--cc=edgar.iglesias@gmail.com \
--cc=i.mitsyanko@gmail.com \
--cc=linux@roeck-us.net \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).