All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Nicolas.Ferre@microchip.com>
To: <robh@kernel.org>
Cc: <alexandre.belloni@bootlin.com>,
	<Ludovic.Desroches@microchip.com>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <sre@kernel.org>,
	<linux-pm@vger.kernel.org>, <netdev@vger.kernel.org>,
	<davem@davemloft.net>, <linux-usb@vger.kernel.org>,
	<stern@rowland.harvard.edu>, <gregkh@linuxfoundation.org>,
	<devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/8] dt-bindings: arm: atmel: add new sam9x60 reset controller binding
Date: Tue, 22 Jan 2019 09:00:45 +0000	[thread overview]
Message-ID: <24a53365-1a8c-51cd-dcd4-db4a69d5256a@microchip.com> (raw)
In-Reply-To: <20190122010733.GA21139@bogus>

Hi Rob,

On 22/01/2019 at 02:07, Rob Herring wrote:
> On Wed, Jan 16, 2019 at 10:57:38AM +0100, Nicolas Ferre wrote:
>> Update the Reset Controller's binding to add new SoC compatibility string.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
>> ---
>>   Documentation/devicetree/bindings/arm/atmel-sysregs.txt | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> index 36952cc39993..badce6ef3ab3 100644
>> --- a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> +++ b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> @@ -22,6 +22,7 @@ Its subnodes can be:
>>   RSTC Reset Controller required properties:
>>   - compatible: Should be "atmel,<chip>-rstc".
>>     <chip> can be "at91sam9260", "at91sam9g45", "sama5d3" or "samx7"
>> +  it also can be "microchip,sam9x60-rstc"
> 
> How is this related to at91sam9260-rstc?

at91sam9260 and sam9x60 are completely different products (they share 
the same core though...). I know the naming could be misleading but it 
is like it is...

> The 'x' is a wildcard? We generally avoid wildcards.

Here, the 'x' is definitively not a wildcard nor a kind of "family" 
name, it's included in the (upcoming) single product's name.

I hope it clarifies.

Best regards,
   Nicolas

>>   - reg: Should contain registers location and length
>>   - clocks: phandle to input clock.
>>   
>> -- 
>> 2.17.1
>>
> 


-- 
Nicolas Ferre

WARNING: multiple messages have this Message-ID (diff)
From: <Nicolas.Ferre@microchip.com>
To: robh@kernel.org
Cc: alexandre.belloni@bootlin.com, Ludovic.Desroches@microchip.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, sre@kernel.org,
	linux-pm@vger.kernel.org, netdev@vger.kernel.org,
	davem@davemloft.net, linux-usb@vger.kernel.org,
	stern@rowland.harvard.edu, gregkh@linuxfoundation.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 2/8] dt-bindings: arm: atmel: add new sam9x60 reset controller binding
Date: Tue, 22 Jan 2019 09:00:45 +0000	[thread overview]
Message-ID: <24a53365-1a8c-51cd-dcd4-db4a69d5256a@microchip.com> (raw)
In-Reply-To: <20190122010733.GA21139@bogus>

Hi Rob,

On 22/01/2019 at 02:07, Rob Herring wrote:
> On Wed, Jan 16, 2019 at 10:57:38AM +0100, Nicolas Ferre wrote:
>> Update the Reset Controller's binding to add new SoC compatibility string.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
>> ---
>>   Documentation/devicetree/bindings/arm/atmel-sysregs.txt | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> index 36952cc39993..badce6ef3ab3 100644
>> --- a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> +++ b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> @@ -22,6 +22,7 @@ Its subnodes can be:
>>   RSTC Reset Controller required properties:
>>   - compatible: Should be "atmel,<chip>-rstc".
>>     <chip> can be "at91sam9260", "at91sam9g45", "sama5d3" or "samx7"
>> +  it also can be "microchip,sam9x60-rstc"
> 
> How is this related to at91sam9260-rstc?

at91sam9260 and sam9x60 are completely different products (they share 
the same core though...). I know the naming could be misleading but it 
is like it is...

> The 'x' is a wildcard? We generally avoid wildcards.

Here, the 'x' is definitively not a wildcard nor a kind of "family" 
name, it's included in the (upcoming) single product's name.

I hope it clarifies.

Best regards,
   Nicolas

>>   - reg: Should contain registers location and length
>>   - clocks: phandle to input clock.
>>   
>> -- 
>> 2.17.1
>>
> 


-- 
Nicolas Ferre

WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: robh@kernel.org
Cc: alexandre.belloni@bootlin.com, Ludovic.Desroches@microchip.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, sre@kernel.org,
	linux-pm@vger.kernel.org, netdev@vger.kernel.org,
	davem@davemloft.net, linux-usb@vger.kernel.org,
	stern@rowland.harvard.edu, gregkh@linuxfoundation.org,
	devicetree@vger.kernel.org
Subject: [2/8] dt-bindings: arm: atmel: add new sam9x60 reset controller binding
Date: Tue, 22 Jan 2019 09:00:45 +0000	[thread overview]
Message-ID: <24a53365-1a8c-51cd-dcd4-db4a69d5256a@microchip.com> (raw)

Hi Rob,

On 22/01/2019 at 02:07, Rob Herring wrote:
> On Wed, Jan 16, 2019 at 10:57:38AM +0100, Nicolas Ferre wrote:
>> Update the Reset Controller's binding to add new SoC compatibility string.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
>> ---
>>   Documentation/devicetree/bindings/arm/atmel-sysregs.txt | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> index 36952cc39993..badce6ef3ab3 100644
>> --- a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> +++ b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> @@ -22,6 +22,7 @@ Its subnodes can be:
>>   RSTC Reset Controller required properties:
>>   - compatible: Should be "atmel,<chip>-rstc".
>>     <chip> can be "at91sam9260", "at91sam9g45", "sama5d3" or "samx7"
>> +  it also can be "microchip,sam9x60-rstc"
> 
> How is this related to at91sam9260-rstc?

at91sam9260 and sam9x60 are completely different products (they share 
the same core though...). I know the naming could be misleading but it 
is like it is...

> The 'x' is a wildcard? We generally avoid wildcards.

Here, the 'x' is definitively not a wildcard nor a kind of "family" 
name, it's included in the (upcoming) single product's name.

I hope it clarifies.

Best regards,
   Nicolas

>>   - reg: Should contain registers location and length
>>   - clocks: phandle to input clock.
>>   
>> -- 
>> 2.17.1
>>
> 


-- 
Nicolas Ferre

WARNING: multiple messages have this Message-ID (diff)
From: <Nicolas.Ferre@microchip.com>
To: <robh@kernel.org>
Cc: devicetree@vger.kernel.org, alexandre.belloni@bootlin.com,
	linux-pm@vger.kernel.org, netdev@vger.kernel.org,
	linux-usb@vger.kernel.org, sre@kernel.org,
	linux-kernel@vger.kernel.org, Ludovic.Desroches@microchip.com,
	stern@rowland.harvard.edu, gregkh@linuxfoundation.org,
	davem@davemloft.net, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/8] dt-bindings: arm: atmel: add new sam9x60 reset controller binding
Date: Tue, 22 Jan 2019 09:00:45 +0000	[thread overview]
Message-ID: <24a53365-1a8c-51cd-dcd4-db4a69d5256a@microchip.com> (raw)
In-Reply-To: <20190122010733.GA21139@bogus>

Hi Rob,

On 22/01/2019 at 02:07, Rob Herring wrote:
> On Wed, Jan 16, 2019 at 10:57:38AM +0100, Nicolas Ferre wrote:
>> Update the Reset Controller's binding to add new SoC compatibility string.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
>> ---
>>   Documentation/devicetree/bindings/arm/atmel-sysregs.txt | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> index 36952cc39993..badce6ef3ab3 100644
>> --- a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> +++ b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> @@ -22,6 +22,7 @@ Its subnodes can be:
>>   RSTC Reset Controller required properties:
>>   - compatible: Should be "atmel,<chip>-rstc".
>>     <chip> can be "at91sam9260", "at91sam9g45", "sama5d3" or "samx7"
>> +  it also can be "microchip,sam9x60-rstc"
> 
> How is this related to at91sam9260-rstc?

at91sam9260 and sam9x60 are completely different products (they share 
the same core though...). I know the naming could be misleading but it 
is like it is...

> The 'x' is a wildcard? We generally avoid wildcards.

Here, the 'x' is definitively not a wildcard nor a kind of "family" 
name, it's included in the (upcoming) single product's name.

I hope it clarifies.

Best regards,
   Nicolas

>>   - reg: Should contain registers location and length
>>   - clocks: phandle to input clock.
>>   
>> -- 
>> 2.17.1
>>
> 


-- 
Nicolas Ferre
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-01-22  9:00 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16  9:57 [PATCH 0/8] ARM: at91/dt: update to existing drivers for the sam9x60 SoC Nicolas Ferre
2019-01-16  9:57 ` Nicolas Ferre
2019-01-16  9:57 ` Nicolas Ferre
2019-01-16  9:57 ` [PATCH 1/8] dt-bindings: arm: atmel: add missing samx7 to reset controller Nicolas Ferre
2019-01-16  9:57   ` Nicolas Ferre
2019-01-16  9:57   ` [1/8] " Nicolas Ferre
2019-01-16  9:57   ` [PATCH 1/8] " Nicolas Ferre
2019-01-22  1:05   ` Rob Herring
2019-01-22  1:05     ` Rob Herring
2019-01-22  1:05     ` [1/8] " Rob Herring
2019-01-22  1:05     ` [PATCH 1/8] " Rob Herring
2019-01-16  9:57 ` [PATCH 2/8] dt-bindings: arm: atmel: add new sam9x60 reset controller binding Nicolas Ferre
2019-01-16  9:57   ` Nicolas Ferre
2019-01-16  9:57   ` [2/8] " Nicolas Ferre
2019-01-16  9:57   ` [PATCH 2/8] " Nicolas Ferre
2019-01-22  1:07   ` Rob Herring
2019-01-22  1:07     ` Rob Herring
2019-01-22  1:07     ` [2/8] " Rob Herring
2019-01-22  9:00     ` Nicolas.Ferre [this message]
2019-01-22  9:00       ` [PATCH 2/8] " Nicolas.Ferre
2019-01-22  9:00       ` [2/8] " Nicolas Ferre
2019-01-22  9:00       ` [PATCH 2/8] " Nicolas.Ferre
2019-01-22 13:40       ` Rob Herring
2019-01-22 13:40         ` Rob Herring
2019-01-22 13:40         ` [2/8] " Rob Herring
2019-01-22 13:40         ` [PATCH 2/8] " Rob Herring
2019-01-16  9:57 ` [PATCH 3/8] dt-bindings: arm: atmel: add new sam9x60 SFR binding Nicolas Ferre
2019-01-16  9:57   ` Nicolas Ferre
2019-01-16  9:57   ` [3/8] " Nicolas Ferre
2019-01-16  9:57   ` [PATCH 3/8] " Nicolas Ferre
2019-01-16  9:57 ` [PATCH 4/8] net/macb: bindings doc/trivial: fix documentation for sama5d3 10/100 interface Nicolas Ferre
2019-01-16  9:57   ` Nicolas Ferre
2019-01-16  9:57   ` [4/8] " Nicolas Ferre
2019-01-16  9:57   ` [PATCH 4/8] " Nicolas Ferre
2019-01-22  1:10   ` Rob Herring
2019-01-22  1:10     ` Rob Herring
2019-01-22  1:10     ` [4/8] " Rob Herring
2019-01-22  9:08     ` [PATCH 4/8] " Nicolas.Ferre
2019-01-22  9:08       ` Nicolas.Ferre
2019-01-22  9:08       ` [4/8] " Nicolas Ferre
2019-01-22  9:08       ` [PATCH 4/8] " Nicolas.Ferre
2019-01-22 13:41       ` Rob Herring
2019-01-22 13:41         ` Rob Herring
2019-01-22 13:41         ` [4/8] " Rob Herring
2019-01-22 13:41         ` [PATCH 4/8] " Rob Herring
2019-01-16  9:57 ` [PATCH 5/8] net/macb: bindings doc: add sam9x60 binding Nicolas Ferre
2019-01-16  9:57   ` Nicolas Ferre
2019-01-16  9:57   ` [5/8] " Nicolas Ferre
2019-01-16  9:57   ` [PATCH 5/8] " Nicolas Ferre
2019-01-16  9:57 ` [PATCH 6/8] power: reset: at91-reset: add support for sam9x60 SoC Nicolas Ferre
2019-01-16  9:57   ` Nicolas Ferre
2019-01-16  9:57   ` [6/8] " Nicolas Ferre
2019-01-16  9:57   ` [PATCH 6/8] " Nicolas Ferre
2019-01-23 18:34   ` Sebastian Reichel
2019-01-23 18:34     ` [6/8] " Sebastian Reichel
2019-01-23 18:34     ` [PATCH 6/8] " Sebastian Reichel
2019-01-24 10:34     ` Nicolas.Ferre
2019-01-24 10:34       ` Nicolas.Ferre
2019-01-24 10:34       ` [6/8] " Nicolas Ferre
2019-01-24 10:34       ` [PATCH 6/8] " Nicolas.Ferre
2019-01-24 17:11       ` Sebastian Reichel
2019-01-24 17:11         ` Sebastian Reichel
2019-01-24 17:11         ` [6/8] " Sebastian Reichel
2019-01-16  9:57 ` [PATCH 7/8] USB: host: ohci-at91: add sam9x60-sfr definition for ohci Nicolas Ferre
2019-01-16  9:57   ` Nicolas Ferre
2019-01-16  9:57   ` [7/8] " Nicolas Ferre
2019-01-16  9:57   ` [PATCH 7/8] " Nicolas Ferre
2019-01-16  9:57 ` [PATCH 8/8] net: macb: add sam9x60-macb compatibility string Nicolas Ferre
2019-01-16  9:57   ` Nicolas Ferre
2019-01-16  9:57   ` [8/8] " Nicolas Ferre
2019-01-16  9:57   ` [PATCH 8/8] " Nicolas Ferre
2019-01-25  9:16   ` Nicolas.Ferre
2019-01-25  9:16     ` Nicolas.Ferre
2019-01-25  9:16     ` [8/8] " Nicolas Ferre
2019-01-25  9:16     ` [PATCH 8/8] " Nicolas.Ferre
2019-02-06 17:51 ` [PATCH 0/8] ARM: at91/dt: update to existing drivers for the sam9x60 SoC Nicolas.Ferre
2019-02-06 17:51   ` Nicolas.Ferre
2019-02-06 17:51   ` Nicolas.Ferre

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=24a53365-1a8c-51cd-dcd4-db4a69d5256a@microchip.com \
    --to=nicolas.ferre@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sre@kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.