Re: [Qemu-devel] [PATCH v5 0/9] Clock framework API.

2018-12-18 Thread Damien Hedde
On 10/16/18 5:48 PM, Peter Maydell wrote: > On 12 October 2018 at 16:26, Damien Hedde wrote: >> Hi Peter, >> >> Sorry to bother you with this, but you said some time ago you would >> write something about reset. > > Yeah, sorry about that. I haven't found (made) the time to think > the issues

Re: [Qemu-devel] [PATCH v5 0/9] Clock framework API.

2018-10-16 Thread Peter Maydell
On 12 October 2018 at 16:26, Damien Hedde wrote: > Hi Peter, > > Sorry to bother you with this, but you said some time ago you would > write something about reset. Yeah, sorry about that. I haven't found (made) the time to think the issues through yet. Let me just dump to email the notes I had. T

Re: [Qemu-devel] [PATCH v5 0/9] Clock framework API.

2018-10-12 Thread Damien Hedde
Hi Peter, Sorry to bother you with this, but you said some time ago you would write something about reset. On 10/2/18 4:24 PM, Damien Hedde wrote: > There is also the problem of initialization which is very much like the > migration. Currently, in the zynq example, clocks outputs are initialized

Re: [Qemu-devel] [PATCH v5 0/9] Clock framework API.

2018-10-11 Thread Philippe Mathieu-Daudé
On 11/10/2018 19:12, Peter Maydell wrote: > On 11 October 2018 at 18:00, Philippe Mathieu-Daudé wrote: >> On 11/10/2018 18:23, Peter Maydell wrote: >>> 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

Re: [Qemu-devel] [PATCH v5 0/9] Clock framework API.

2018-10-11 Thread Peter Maydell
On 11 October 2018 at 18:00, Philippe Mathieu-Daudé wrote: > On 11/10/2018 18:23, Peter Maydell wrote: >> 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

Re: [Qemu-devel] [PATCH v5 0/9] Clock framework API.

2018-10-11 Thread Philippe Mathieu-Daudé
On 11/10/2018 18:23, Peter Maydell wrote: > On 11 October 2018 at 17:20, Damien Hedde 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

Re: [Qemu-devel] [PATCH v5 0/9] Clock framework API.

2018-10-11 Thread Peter Maydell
On 11 October 2018 at 17:20, Damien Hedde 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

Re: [Qemu-devel] [PATCH v5 0/9] Clock framework API.

2018-10-11 Thread Damien Hedde
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 >> configurati

Re: [Qemu-devel] [PATCH v5 0/9] Clock framework API.

2018-10-04 Thread Philippe Mathieu-Daudé
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. > > Thi

[Qemu-devel] [PATCH v5 0/9] Clock framework API.

2018-10-02 Thread Damien Hedde
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. This series is a reroll of the v4 sent recently without the reset fe