devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Gururaja Hebbar <gururaja.hebbar-l0cyMroinI0@public.gmane.org>
Cc: "davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org"
	<davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org>,
	"tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org"
	<tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
	"benoit.cousson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
	<benoit.cousson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"vaibhav.bedia-l0cyMroinI0@public.gmane.org"
	<vaibhav.bedia-l0cyMroinI0@public.gmane.org>,
	"benoit.cousson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
	<benoit.cousson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	"linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [Patch V2 4/4] ARM: dts: AM33XX: update rtc node compatibility
Date: Fri, 2 Aug 2013 12:20:18 +0100	[thread overview]
Message-ID: <20130802112018.GI2884@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <51FB92F8.9020801-l0cyMroinI0@public.gmane.org>

On Fri, Aug 02, 2013 at 12:07:36PM +0100, Gururaja Hebbar wrote:
> On 8/1/2013 10:35 PM, Mark Rutland wrote:
> > On Tue, Jul 30, 2013 at 05:21:14PM +0100, Sekhar Nori wrote:
> >> On 7/30/2013 8:25 PM, Mark Rutland wrote:
> >>> On Tue, Jul 30, 2013 at 06:05:52AM +0100, Gururaja Hebbar wrote:
> >>>> Hi,
> >>>>
> >>>> On 7/3/2013 2:17 PM, Hebbar Gururaja wrote:
> >>>>> Since AM33xx  RTC IP has RTC_IRQWAKEEN to support Alarm Wake-up.
> >>>>>
> >>>>> Update the rtc compatible property to "ti,am3352-rtc" to enable handling
> >>>>> of this feature inside rtc-omap driver.
> >>>>
> >>>> The other 2 rtc driver related patches have been pulled up. If you have
> >>>> no comments, can you please pull this up.
> >>>>
> >>>> Regards
> >>>> Gururaja
> >>>>
> >>>>>
> >>>>> Signed-off-by: Hebbar Gururaja <gururaja.hebbar-l0cyMroinI0@public.gmane.org>
> >>>>> ---
> >>>>> :100644 100644 77aa1b0... dde180a... M	arch/arm/boot/dts/am33xx.dtsi
> >>>>>    arch/arm/boot/dts/am33xx.dtsi |    2 +-
> >>>>>    1 file changed, 1 insertion(+), 1 deletion(-)
> >>>>>
> >>>>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> >>>>> index 77aa1b0..dde180a 100644
> >>>>> --- a/arch/arm/boot/dts/am33xx.dtsi
> >>>>> +++ b/arch/arm/boot/dts/am33xx.dtsi
> >>>>> @@ -297,7 +297,7 @@
> >>>>>    		};
> >>>>>
> >>>>>    		rtc@44e3e000 {
> >>>>> -			compatible = "ti,da830-rtc";
> >>>>> +			compatible = "ti,am3352-rtc";
> >>>
> >>> Given that this is backwards compatible with the old binding, it would
> >>> be nicer to have this as:
> >>>
> >>> 	compatible = "ti,am3352-rtc", "ti,da830-rtc";
> >>>
> >>> We must get into the habit of changing dts files in a
> >>> backwards-compatible fashion.
> >>
> >> Right, I suggested this when v1 was posted. It turns out the current
> >> kernel does not handle the compatilble list correctly and the string
> >> selected actually depends on the order in which it appears in match
> >> table in driver instead.
> >>
> >> I saw there were patches being discussed to fix this issue, but until
> >> that is fixed, we cannot really use what you (and I before) suggested.
> >
> > A temporary solution would be to list the "ti,am3352-rtc" first in the
> > of_match_table kernel-side.
> 
> If above method is followed, then it would cause trouble on davinci 
> platform because this rtc-omap driver is also used by Davinci platform.
> On davinci Plaform the driver would match with "ti,am3352-rtc" for 
> compatible.

Sorry, I don't follow. Does the davinci dt have "ti,am3352-rtc" in it's
compatible string list?

If so, and it's not compatible, the dts is wrong.

If not, then we won't use the behaviour specific to "ti,am3352-rtc", and
there's no problem.

What trouble would this cause?

Thanks,
Mark.

> 
> Regards
> Gururaja
> 
> > That way you can keep the old compatible
> > string in the dts compatible list, and maintain backwards compatibilty
> > with older kernels.
> >
> > Later if the way Linux matches compatible strings is changed, this
> > shouldn't break the probe order, and the of_match_table order could be
> > changed.
> >
> > Have I missed something?
> >
> > Thanks,
> > Mark.
> >
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

  parent reply	other threads:[~2013-08-02 11:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03  8:47 [Patch V2 0/4] rtc: omap: handle rtc wakeup support in driver Hebbar Gururaja
     [not found] ` <1372841225-18813-1-git-send-email-gururaja.hebbar-l0cyMroinI0@public.gmane.org>
2013-07-03  8:47   ` [Patch V2 1/4] rtc: omap: restore back (hard-code) wakeup support Hebbar Gururaja
2013-07-03  8:47   ` [Patch V2 2/4] ARM: Davinci: da8xx/omap-l1: Remove hard coding of rtc device wakeup Hebbar Gururaja
     [not found]     ` <1372841225-18813-3-git-send-email-gururaja.hebbar-l0cyMroinI0@public.gmane.org>
2013-08-16 12:02       ` Sekhar Nori
2013-07-03  8:47   ` [Patch V2 3/4] rtc: omap: add rtc wakeup support to alarm events Hebbar Gururaja
     [not found]     ` <1372841225-18813-4-git-send-email-gururaja.hebbar-l0cyMroinI0@public.gmane.org>
2013-07-24 13:14       ` Gururaja Hebbar
2013-07-03  8:47   ` [Patch V2 4/4] ARM: dts: AM33XX: update rtc node compatibility Hebbar Gururaja
     [not found]     ` <1372841225-18813-5-git-send-email-gururaja.hebbar-l0cyMroinI0@public.gmane.org>
2013-07-30  5:05       ` Gururaja Hebbar
2013-07-30 14:55         ` Mark Rutland
     [not found]           ` <20130730145501.GA29859-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-07-30 16:21             ` Sekhar Nori
2013-08-01 17:05               ` Mark Rutland
     [not found]                 ` <20130801170537.GF8095-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-08-02 11:07                   ` Gururaja Hebbar
     [not found]                     ` <51FB92F8.9020801-l0cyMroinI0@public.gmane.org>
2013-08-02 11:20                       ` Mark Rutland [this message]
     [not found]                         ` <20130802112018.GI2884-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-08-02 11:48                           ` Gururaja Hebbar
2013-08-02 12:40                             ` Mark Rutland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130802112018.GI2884@e106331-lin.cambridge.arm.com \
    --to=mark.rutland-5wv7dgnigg8@public.gmane.org \
    --cc=benoit.cousson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=benoit.cousson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=gururaja.hebbar-l0cyMroinI0@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org \
    --cc=vaibhav.bedia-l0cyMroinI0@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).