On Wed, Oct 29, 2014 at 12:12:42AM +0000, Andrew Bresticker wrote:
> Parse the GIC timer frequency and interrupt from the device-tree.
>
> Signed-off-by: Andrew Bresticker <abrestic@xxxxxxxxxxxx>
> ---
> New for v3.
> ---
> drivers/clocksource/Kconfig | 1 +
> drivers/clocksource/mips-gic-timer.c | 37 +++++++++++++++++++++++++++++-------
> 2 files changed, 31 insertions(+), 7 deletions(-)
>
[...]
> +static void __init gic_clocksource_of_init(struct device_node *node)
> +{
> + if (of_property_read_u32(node, "clock-frequency", &gic_frequency)) {
> + pr_err("GIC frequency not specified.\n");
> + return;
> + }
> + gic_timer_irq = irq_of_parse_and_map(node, 0);
> + if (!gic_timer_irq) {
> + pr_err("GIC timer IRQ not specified.\n");
> + return;
> + }
> +
> + __gic_clocksource_init();
> +}
> +CLOCKSOURCE_OF_DECLARE(mips_gic_timer, "mti,interaptiv-gic-timer",
> + gic_clocksource_of_init);
Your binding document expected the timer node under the GIC node, and it
looks like this relies on GIC internals. Hwoever, this allows for people
to put the timer node anywhere (and it turns out people are _really_ bad
at putting things together as the binding author expected).
It might be better if the GIC driver detected the sub node and probed
the clocksource driver (or registered a platform device that the
clocksource driver gets registered from). that could prevent some
horrible issues with probe ordering and/or bad dts.
Mark.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
