public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 11/14] Documentation: dt: binding: omap: am43x timer
Date: Tue, 28 May 2013 16:05:10 -0600	[thread overview]
Message-ID: <51A52A16.1040204@wwwdotorg.org> (raw)
In-Reply-To: <51A520B5.8040803@gmail.com>

On 05/28/2013 03:25 PM, Jon Hunter wrote:
> 
> On 27/05/13 15:37, Afzal Mohammed wrote:
>> AM43x timer bindings.
>>
>> Signed-off-by: Afzal Mohammed <afzal@ti•com>
>> ---
>>  Documentation/devicetree/bindings/arm/omap/timer.txt | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/omap/timer.txt b/Documentation/devicetree/bindings/arm/omap/timer.txt
>> index d02e27c..70cb398 100644
>> --- a/Documentation/devicetree/bindings/arm/omap/timer.txt
>> +++ b/Documentation/devicetree/bindings/arm/omap/timer.txt
>> @@ -14,6 +14,8 @@ Required properties:
>>  			ti,omap5430-timer (applicable to OMAP543x devices)
>>  			ti,am335x-timer	(applicable to AM335x devices)
>>  			ti,am335x-timer-1ms (applicable to AM335x devices)
>> +			"ti,am4372-timer-1ms", "ti,am335x-timer-1ms" for AM43x 1ms timer
>> +			"ti,am4372-timer", "ti,am335x-timer" for AM43x timers other than 1ms one
>>  
>>  - reg:			Contains timer register address range (base address and
>>  			length).
> 
> If you are adding more compatibility strings, then this implies that the
> AM43x timers are not 100% compatible with any other device listed (such
> as am335x or any omap device). That's fine but you should state that in
> the changelog. If the AM43x timer registers are 100% compatible with
> existing devices you should not add these.

I'm not sure that's true; .dts files should always include a compatible
value that describes the most specific model of the HW, plus any
baseline compatible value that the HW is compatible with. This allows
any required quirks/fixes/... to be applied for the specific HW model
later even if nobody knows right now they'll be needed. Hence, defining
new compatible values doesn't necessarily mean incompatible HW.

  reply	other threads:[~2013-05-28 22:05 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27 14:33 [PATCH v2 00/14] ARM: OMAP2+: AM43x initial support Afzal Mohammed
2013-05-27 14:35 ` [PATCH v2 01/14] ARM: OMAP2+: separate out OMAP4 restart Afzal Mohammed
2013-05-27 14:35 ` [PATCH v2 02/14] ARM: OMAP2+: AM43x: Kconfig Afzal Mohammed
2013-06-12 17:12   ` Tony Lindgren
2013-06-13  6:58     ` Mohammed, Afzal
2013-06-13  9:54       ` Tony Lindgren
2013-06-13 10:02         ` Mohammed, Afzal
2013-06-13 10:17           ` Tony Lindgren
2013-05-27 14:35 ` [PATCH v2 03/14] ARM: OMAP2+: AM43x: kbuild Afzal Mohammed
2013-05-27 14:35 ` [PATCH v2 04/14] ARM: OMAP2+: AM43x: soc_is support Afzal Mohammed
2013-05-27 14:36 ` [PATCH v2 05/14] ARM: OMAP2+: AM437x: SoC revision detection Afzal Mohammed
2013-05-27 14:36 ` [PATCH v2 06/14] ARM: OMAP2+: AM43x: static mapping Afzal Mohammed
2013-05-27 14:36 ` [PATCH v2 07/14] ARM: OMAP2+: AM43x: early init Afzal Mohammed
2013-06-12 17:14   ` Tony Lindgren
2013-05-27 14:36 ` [PATCH v2 08/14] ARM: OMAP2+: AM43x: GP or HS ? Afzal Mohammed
2013-05-27 14:36 ` [PATCH v2 09/14] ARM: OMAP2+: AM43x: SRAM base and size Afzal Mohammed
2013-05-27 14:36 ` [PATCH v2 10/14] ARM: OMAP2+: AM43x: basic dt support Afzal Mohammed
2013-05-27 14:37 ` [PATCH v2 11/14] Documentation: dt: binding: omap: am43x timer Afzal Mohammed
2013-05-28 21:25   ` Jon Hunter
2013-05-28 22:05     ` Stephen Warren [this message]
2013-05-29  8:06       ` Mohammed, Afzal
2013-05-29  8:39         ` Benoit Cousson
2013-05-29  9:58           ` Mohammed, Afzal
2013-05-29 13:35             ` Benoit Cousson
2013-06-03  7:49               ` Mohammed, Afzal
2013-06-03  9:53                 ` Benoit Cousson
2013-05-29 15:27           ` Stephen Warren
2013-05-30 11:44             ` Benoit Cousson
2013-05-29 20:17       ` Jon Hunter
2013-05-27 14:37 ` [PATCH v2 12/14] Documentation: dt: binding: omap: am43x counter Afzal Mohammed
2013-05-28 21:26   ` Jon Hunter
2013-05-29  8:08     ` Mohammed, Afzal
2013-05-27 14:37 ` [PATCH v2 13/14] Documentation: dt: binding: serial: omap: am43x Afzal Mohammed
2013-05-27 14:37 ` [PATCH v2 14/14] ARM: dts: AM43x: initial support Afzal Mohammed
2013-05-29  8:53   ` Benoit Cousson
2013-05-29  8:57     ` Florian Vaussard
2013-05-29  9:05       ` Benoit Cousson
2013-06-04 11:25 ` [PATCH v2 00/14] ARM: OMAP2+: AM43x " Mohammed, Afzal

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=51A52A16.1040204@wwwdotorg.org \
    --to=swarren@wwwdotorg$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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