linux-kernel - Re: [PATCH 11/18] ARM: at91/rtc-at91sam9: each SoC can select the RTT device to use

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120220012520.GB29599@game.jcrosoft.org>
Date:	Mon, 20 Feb 2012 02:25:20 +0100
From:	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>
To:	Ryan Mallon <rmallon@...il.com>
Cc:	Nicolas Ferre <nicolas.ferre@...el.com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 11/18] ARM: at91/rtc-at91sam9: each SoC can select the
 RTT device to use

On 11:32 Mon 20 Feb     , Ryan Mallon wrote:
> On 18/02/12 04:50, Nicolas Ferre wrote:
> 
> > From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>
> > 
> > For the RTT as RTC driver rtc-at91sam9, the platform_device structure
> > is filled during SoC initialization. This will allow to convert this
> > RTC driver as a standard platform driver.
> > 
> > Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>
> > Acked-by: Nicolas Ferre <nicolas.ferre@...el.com>
> > ---
> >  arch/arm/mach-at91/at91sam9260_devices.c |   11 +++++
> >  arch/arm/mach-at91/at91sam9261_devices.c |   10 +++++
> >  arch/arm/mach-at91/at91sam9263_devices.c |   25 ++++++++++++
> >  arch/arm/mach-at91/at91sam9g45_devices.c |   10 +++++
> >  arch/arm/mach-at91/at91sam9rl_devices.c  |   10 +++++
> >  drivers/rtc/rtc-at91sam9.c               |   61 ++++-------------------------
> >  6 files changed, 75 insertions(+), 52 deletions(-)
> > 
> > diff --git a/arch/arm/mach-at91/at91sam9260_devices.c b/arch/arm/mach-at91/at91sam9260_devices.c
> > index b93a337..2071017 100644
> > --- a/arch/arm/mach-at91/at91sam9260_devices.c
> > +++ b/arch/arm/mach-at91/at91sam9260_devices.c
> > @@ -728,8 +728,19 @@ static struct platform_device at91sam9260_rtt_device = {
> >  	.num_resources	= ARRAY_SIZE(rtt_resources),
> >  };
> >  
> > +
> > +#if IS_ENABLED(CONFIG_RTC_DRV_AT91SAM9)
> > +static void __init at91_add_device_rtt_rtc(void)
> > +{
> > +	at91sam9260_rtt_device.name = "rtc-at91sam9";
> > +}
> 
> 
> Nitpickish: This function doesn't _add_ anything. It would probably be
> better called at91_init_device_rtt_rtc. Same goes for the other "add"
> functions in this patch.
yes but an other patch update it to add gpbr resource

> 
> > +#else
> > +static void __init at91_add_device_rtt_rtc(void) {}
> > +#endif
> > +
> >  static void __init at91_add_device_rtt(void)
> >  {
> > +	at91_add_device_rtt_rtc();
> >  	platform_device_register(&at91sam9260_rtt_device);
> >  }
> 
> 
> Does this work by setting the rtt device name iff
> CONFIG_RTC_DRV_AT91SAM9 is set? If so, it seems a bit ugly. Why bother
> doing the platform_device_register at all if you know it isn't going to
> do anything? Shouldn't the at91sam9260_rrt_device struct declaration and
> the platform_device_register all be conditional on CONFIG_RTC_DRV_AT91SAM9?
no people use rtt for other purpose
RTT is a timer and the rtc use it

anyway this will be dropped via DT
and the resource will be optional

Best Regards,
J.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/