From: jhovold@gmail.com (Johan Hovold)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 4/5] RTC: rtc-at91sam9: add device-tree support
Date: Thu, 11 Apr 2013 14:57:26 +0200 [thread overview]
Message-ID: <20130411125726.GC21305@localhost> (raw)
In-Reply-To: <20130408111113.GX20693@game.jcrosoft.org>
On Mon, Apr 08, 2013 at 01:11:13PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 12:38 Mon 08 Apr , Johan Hovold wrote:
> > On Mon, Apr 08, 2013 at 11:57:06AM +0200, Nicolas Ferre wrote:
> > > On 04/08/2013 11:00 AM, Johan Hovold :
> > > > On Mon, Apr 08, 2013 at 09:38:07AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > >> On 17:12 Sun 07 Apr , Johan Hovold wrote:
[...]
> > > >>> +rtt at fffffd20 {
> > > >>> + compatible = "atmel,at91sam9g45-rtt", "atmel,at91sam9260-rtt";
> > >
> > > No, there is no visible difference between the sam9g45 RTT and the
> > > sam9260 one. So the most precise compatibility string is still sam9260.
> > > If one day we feel the need for a advanced feature that exists on a more
> > > recent SoC, we have the possibility to add it at that time...
> >
> > Yes, this should be just "atmel,at91sam9260-rtt" to follow the current
> > practise in AT91. However, as I mentioned in an earlier mail one could
> > interpret
> >
> > "The first string in the list specifies the exact device that
> > the node represents in the form "<manufacturer>,<model>". The
> > following strings represent other devices that the device is
> > compatible with.
> >
> > For example, the Freescale MPC8349 System on Chip (SoC) has a
> > serial device which implements the National Semiconductor
> > ns16550 register interface. The compatible property for the
> > MPC8349 serial device should therefore be: compatible =
> > "fsl,mpc8349-uart", "ns16550". In this case, fsl,mpc8349-uart
> > specifies the exact device, and ns16550 states that it is
> > register-level compatible with a National Semiconductor 16550
> > UART."
> >
> > http://www.devicetree.org/Device_Tree_Usage#Understanding_the_compatible_Property
> >
> > to mean that the compatible property should always be exact SoC-IP
> > followed by the first (most generic) compatible one.
>
> here you describe compatible IP not drivers implementation
I'm referring to the IP and not drivers.
> they are both usuart IP that are compatible at IP level.
Fair enough, I see how this can be considered to be in accordance with
the above quotation.
Johan
WARNING: multiple messages have this Message-ID (diff)
From: Johan Hovold <jhovold@gmail.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: Johan Hovold <jhovold@gmail.com>,
dgilbert@interlog.com, Nicolas Ferre <nicolas.ferre@atmel.com>,
Robert Nelson <Robert.Nelson@digikey.com>,
devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 4/5] RTC: rtc-at91sam9: add device-tree support
Date: Thu, 11 Apr 2013 14:57:26 +0200 [thread overview]
Message-ID: <20130411125726.GC21305@localhost> (raw)
In-Reply-To: <20130408111113.GX20693@game.jcrosoft.org>
On Mon, Apr 08, 2013 at 01:11:13PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 12:38 Mon 08 Apr , Johan Hovold wrote:
> > On Mon, Apr 08, 2013 at 11:57:06AM +0200, Nicolas Ferre wrote:
> > > On 04/08/2013 11:00 AM, Johan Hovold :
> > > > On Mon, Apr 08, 2013 at 09:38:07AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > >> On 17:12 Sun 07 Apr , Johan Hovold wrote:
[...]
> > > >>> +rtt@fffffd20 {
> > > >>> + compatible = "atmel,at91sam9g45-rtt", "atmel,at91sam9260-rtt";
> > >
> > > No, there is no visible difference between the sam9g45 RTT and the
> > > sam9260 one. So the most precise compatibility string is still sam9260.
> > > If one day we feel the need for a advanced feature that exists on a more
> > > recent SoC, we have the possibility to add it at that time...
> >
> > Yes, this should be just "atmel,at91sam9260-rtt" to follow the current
> > practise in AT91. However, as I mentioned in an earlier mail one could
> > interpret
> >
> > "The first string in the list specifies the exact device that
> > the node represents in the form "<manufacturer>,<model>". The
> > following strings represent other devices that the device is
> > compatible with.
> >
> > For example, the Freescale MPC8349 System on Chip (SoC) has a
> > serial device which implements the National Semiconductor
> > ns16550 register interface. The compatible property for the
> > MPC8349 serial device should therefore be: compatible =
> > "fsl,mpc8349-uart", "ns16550". In this case, fsl,mpc8349-uart
> > specifies the exact device, and ns16550 states that it is
> > register-level compatible with a National Semiconductor 16550
> > UART."
> >
> > http://www.devicetree.org/Device_Tree_Usage#Understanding_the_compatible_Property
> >
> > to mean that the compatible property should always be exact SoC-IP
> > followed by the first (most generic) compatible one.
>
> here you describe compatible IP not drivers implementation
I'm referring to the IP and not drivers.
> they are both usuart IP that are compatible at IP level.
Fair enough, I see how this can be considered to be in accordance with
the above quotation.
Johan
next prev parent reply other threads:[~2013-04-11 12:57 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 3:54 [PATCH] rtc: rtc-at91sam9.c add DT support Douglas Gilbert
2013-04-04 8:11 ` Nicolas Ferre
2013-04-04 8:11 ` Nicolas Ferre
2013-04-04 13:25 ` Douglas Gilbert
2013-04-04 13:25 ` Douglas Gilbert
2013-04-04 14:08 ` Nicolas Ferre
2013-04-04 14:08 ` Nicolas Ferre
2013-04-04 19:14 ` Douglas Gilbert
2013-04-04 19:14 ` Douglas Gilbert
2013-04-07 15:09 ` Johan Hovold
2013-04-07 15:09 ` Johan Hovold
[not found] ` <1365347572-14972-1-git-send-email-jhovold@gmail.com>
2013-04-08 7:33 ` [RFC 1/5] ARM: at91: add general purpose backup register (GPBR) support Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 7:33 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 8:46 ` Johan Hovold
2013-04-08 8:46 ` Johan Hovold
2013-04-08 10:04 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:04 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-11 12:39 ` Johan Hovold
2013-04-11 12:39 ` Johan Hovold
2013-04-11 14:53 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-11 14:53 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <1365347572-14972-2-git-send-email-jhovold@gmail.com>
2013-04-08 7:35 ` [RFC 2/5] ARM: at91/dts: " Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 7:35 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <1365347572-14972-4-git-send-email-jhovold@gmail.com>
2013-04-08 7:38 ` [RFC 4/5] RTC: rtc-at91sam9: add device-tree support Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 7:38 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 9:00 ` Johan Hovold
2013-04-08 9:00 ` Johan Hovold
2013-04-08 9:57 ` Nicolas Ferre
2013-04-08 9:57 ` Nicolas Ferre
2013-04-08 10:03 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:03 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:42 ` Nicolas Ferre
2013-04-08 10:42 ` Nicolas Ferre
2013-04-08 11:02 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 11:02 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:48 ` Johan Hovold
2013-04-08 10:48 ` Johan Hovold
2013-04-08 11:08 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 11:08 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:38 ` Johan Hovold
2013-04-08 10:38 ` Johan Hovold
2013-04-08 11:11 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 11:11 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-11 12:57 ` Johan Hovold [this message]
2013-04-11 12:57 ` Johan Hovold
2013-04-04 8:16 ` [PATCH] rtc: rtc-at91sam9.c add DT support Johan Hovold
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=20130411125726.GC21305@localhost \
--to=jhovold@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.