[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-arm] [Qemu-devel] [PATCH v5 0/9] Clock framework API.
From: |
Peter Maydell |
Subject: |
Re: [Qemu-arm] [Qemu-devel] [PATCH v5 0/9] Clock framework API. |
Date: |
Thu, 11 Oct 2018 17:23:20 +0100 |
On 11 October 2018 at 17:20, Damien Hedde <address@hidden> wrote:
>
> Hi Philippe,
>
> On 10/4/18 6:13 PM, Philippe Mathieu-Daudé wrote:
>> Hi Damien,
>>
>> On 02/10/2018 16:24, Damien Hedde wrote:
>>> This series aims to add a way to model clocks in qemu between devices.
>>> This allows to model the clock tree of a platform allowing us to inspect
>>> clock
>>> configuration and detect problems such as disabled clock or bad configured
>>> pll.
>>>
>>> [...]
>>>
>>> Any comments and suggestion are welcomed.
>>
>> How would you instanciate devices and connect their clocks from the
>> command line (with the -device option)?
> I didn't not thought about that. I'm not sure to understand how this is
> done for a gpio for example. Is this done by setting the link property
> manually ?
You can't wire up GPIOs on the command line. I don't think we
really need to be able to wire up clocks on the command line either,
do we?
> Should clocked devices have DeviceClass::user_creatable = false by default?
How many devices have a clock and nothing else that would cause
them to be non-user-creatable (ie no GPIOs, no IRQ lines, no
memory-mapped memory regions) ?
thanks
-- PMM
Re: [Qemu-arm] [PATCH v5 0/9] Clock framework API., Damien Hedde, 2018/10/12