On 06/09/2016 09:46 AM, Geert Uytterhoeven wrote:
Hi Daniel,
On Wed, Jun 8, 2016 at 4:10 PM, Daniel Lezcano
wrote:
On 06/07/2016 11:54 AM, Geert Uytterhoeven wrote:
[ ... ]
in clockevents/clockevents/next breaks the boot on e.g. r8a7791/koelsch
(arm32) and
On 06/09/2016 09:46 AM, Geert Uytterhoeven wrote:
Hi Daniel,
On Wed, Jun 8, 2016 at 4:10 PM, Daniel Lezcano
wrote:
On 06/07/2016 11:54 AM, Geert Uytterhoeven wrote:
[ ... ]
in clockevents/clockevents/next breaks the boot on e.g. r8a7791/koelsch
(arm32) and r8a7795/salvator-x (arm64).
Hi Daniel,
On Wed, Jun 8, 2016 at 4:10 PM, Daniel Lezcano
wrote:
> On 06/07/2016 11:54 AM, Geert Uytterhoeven wrote:
>
> [ ... ]
>
>> in clockevents/clockevents/next breaks the boot on e.g. r8a7791/koelsch
>> (arm32) and r8a7795/salvator-x (arm64).
>>
>> Using
Hi Daniel,
On Wed, Jun 8, 2016 at 4:10 PM, Daniel Lezcano
wrote:
> On 06/07/2016 11:54 AM, Geert Uytterhoeven wrote:
>
> [ ... ]
>
>> in clockevents/clockevents/next breaks the boot on e.g. r8a7791/koelsch
>> (arm32) and r8a7795/salvator-x (arm64).
>>
>> Using "earlycon keep_bootcon" on koelsch
On 06/07/2016 11:54 AM, Geert Uytterhoeven wrote:
[ ... ]
in clockevents/clockevents/next breaks the boot on e.g. r8a7791/koelsch
(arm32) and r8a7795/salvator-x (arm64).
Using "earlycon keep_bootcon" on koelsch (this doesn't help on arm64)
reveals it's stuck at:
clocksource_probe: no
On 06/07/2016 11:54 AM, Geert Uytterhoeven wrote:
[ ... ]
in clockevents/clockevents/next breaks the boot on e.g. r8a7791/koelsch
(arm32) and r8a7795/salvator-x (arm64).
Using "earlycon keep_bootcon" on koelsch (this doesn't help on arm64)
reveals it's stuck at:
clocksource_probe: no
On 06/07/2016 11:54 AM, Geert Uytterhoeven wrote:
Hi Daniel,
Hi Geert,
[ ... ]
Using "earlycon keep_bootcon" on koelsch (this doesn't help on arm64)
reveals it's stuck at:
clocksource_probe: no matching clocksources found
sched_clock: 32 bits at 100 Hz, resolution 1000ns,
On 06/07/2016 11:54 AM, Geert Uytterhoeven wrote:
Hi Daniel,
Hi Geert,
[ ... ]
Using "earlycon keep_bootcon" on koelsch (this doesn't help on arm64)
reveals it's stuck at:
clocksource_probe: no matching clocksources found
sched_clock: 32 bits at 100 Hz, resolution 1000ns,
On 06/07/2016 11:54 AM, Geert Uytterhoeven wrote:
Hi Daniel,
On Wed, Jun 1, 2016 at 10:34 AM, Daniel Lezcano
wrote:
The macro CLOCKSOURCE_OF_DECLARE is widely used in the timer drivers.
Basically, this macro is defined to insert in a table a tuple name,function.
On 06/07/2016 11:54 AM, Geert Uytterhoeven wrote:
Hi Daniel,
On Wed, Jun 1, 2016 at 10:34 AM, Daniel Lezcano
wrote:
The macro CLOCKSOURCE_OF_DECLARE is widely used in the timer drivers.
Basically, this macro is defined to insert in a table a tuple name,function.
This function is an init
Hi Daniel,
On Wed, Jun 1, 2016 at 10:34 AM, Daniel Lezcano
wrote:
> The macro CLOCKSOURCE_OF_DECLARE is widely used in the timer drivers.
>
> Basically, this macro is defined to insert in a table a tuple name,function.
> This function is an init function called when
Hi Daniel,
On Wed, Jun 1, 2016 at 10:34 AM, Daniel Lezcano
wrote:
> The macro CLOCKSOURCE_OF_DECLARE is widely used in the timer drivers.
>
> Basically, this macro is defined to insert in a table a tuple name,function.
> This function is an init function called when the name matches the DT node
The macro CLOCKSOURCE_OF_DECLARE is widely used in the timer drivers.
Basically, this macro is defined to insert in a table a tuple name,function.
This function is an init function called when the name matches the DT node and
its signature is:
typedef void (*of_init_fn_1)(struct
The macro CLOCKSOURCE_OF_DECLARE is widely used in the timer drivers.
Basically, this macro is defined to insert in a table a tuple name,function.
This function is an init function called when the name matches the DT node and
its signature is:
typedef void (*of_init_fn_1)(struct
14 matches
Mail list logo