[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_Jsq+t+JqeS9+xUb2Fv=_3RRKx=c1Jssn4U3SpWu++zECfGw@mail.gmail.com>
Date: Wed, 16 Oct 2019 10:02:03 -0500
From: Rob Herring <robh@...nel.org>
To: Geert Uytterhoeven <geert+renesas@...der.be>
Cc: Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Chris Brandt <chris.brandt@...esas.com>,
Jacopo Mondi <jacopo+renesas@...ndi.org>,
"open list:MEDIA DRIVERS FOR RENESAS - FCP"
<linux-renesas-soc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 2/4] clocksource/drivers/timer-of: Use unique device
name instead of timer
On Wed, Oct 16, 2019 at 9:52 AM Geert Uytterhoeven
<geert+renesas@...der.be> wrote:
>
> If a hardware-specific driver does not provide a name, the timer-of core
> falls back to device_node.name. Due to generic DT node naming policies,
> that name is almost always "timer", and thus doesn't identify the actual
> timer used.
>
> Fix this by using device_node.full_name instead, which includes the unit
> addrees.
>
> Example impact on /proc/timer_list:
>
> -Clock Event Device: timer
> +Clock Event Device: timer@...ec400
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
> ---
> v4:
> - New.
> ---
> drivers/clocksource/timer-of.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Good. One less device_node.name pointer use to get rid of. I want to
drop it from the struct and stop storing both node name strings.
Reviewed-by: Rob Herring <robh@...nel.org>
Rob
Powered by blists - more mailing lists