On 11/10/2018 18:23, Peter Maydell wrote: > On 11 October 2018 at 17:20, Damien Hedde <damien.he...@greensocs.com> 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?
This would be a big mess. > >> 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) ? I'm not sure I understood your question. But I understand than as devices consuming GPIO/IRQ, clocked device can't be instantiate from command line, and I am happy with that.
