From: Kishon Vijay Abraham I <kishon@ti.com>
To: Nishanth Menon <nm@ti.com>, <linux-kernel@vger.kernel.org>,
<tony@atomide.com>, <gregkh@linuxfoundation.org>
Cc: <nsekhar@ti.com>, <praneeth@ti.com>
Subject: Re: [PATCH 1/2] ARM: dts: am4372: Add "ti,am437x-ocp2scp" as compatible string for OCP2SCP
Date: Fri, 13 Mar 2015 21:01:17 +0530 [thread overview]
Message-ID: <550302C5.9050809@ti.com> (raw)
In-Reply-To: <5502FF0E.7090502@ti.com>
Hi,
On Friday 13 March 2015 08:45 PM, Nishanth Menon wrote:
> On 03/13/2015 10:12 AM, Kishon Vijay Abraham I wrote:
>> Added a new compatible string "ti,am437x-ocp2scp" for OCP2SCP module.
>> This is needed since except for the OCP2SCP used in AM437x, SYNC2 value
>> in OCP2SCP TIMING should be changed whereas the default value is sufficient
>> in AM437x.
>>
>> Cc: Tony Lindgren <tony@atomide.com>
>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>> ---
>> .../devicetree/bindings/bus/omap-ocp2scp.txt | 3 ++-
>> arch/arm/boot/dts/am4372.dtsi | 4 ++--
>> 2 files changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/bus/omap-ocp2scp.txt b/Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
>> index 63dd805..18729f6 100644
>> --- a/Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
>> +++ b/Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
>> @@ -1,7 +1,8 @@
>> * OMAP OCP2SCP - ocp interface to scp interface
>>
>> properties:
>> -- compatible : Should be "ti,omap-ocp2scp"
>> +- compatible : Should be "ti,am437x-ocp2scp" for AM437x processor
>> + Should be "ti,omap-ocp2scp" for all others
>> - reg : Address and length of the register set for the device
>> - #address-cells, #size-cells : Must be present if the device has sub-nodes
>> - ranges : the child address space are mapped 1:1 onto the parent address space
>> diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi
>> index 1943fc3..286e317 100644
>> --- a/arch/arm/boot/dts/am4372.dtsi
>> +++ b/arch/arm/boot/dts/am4372.dtsi
>> @@ -787,7 +787,7 @@
>> };
>>
>> ocp2scp0: ocp2scp@483a8000 {
>> - compatible = "ti,omap-ocp2scp";
>> + compatible = "ti,am437x-ocp2scp", "ti,omap-ocp2scp";
>> #address-cells = <1>;
>> #size-cells = <1>;
>> ranges;
>> @@ -806,7 +806,7 @@
>> };
>>
>> ocp2scp1: ocp2scp@483e8000 {
>> - compatible = "ti,omap-ocp2scp";
>> + compatible = "ti,am437x-ocp2scp", "ti,omap-ocp2scp";
>> #address-cells = <1>;
>> #size-cells = <1>;
>> ranges;
>>
>
>
> is there a reason you chose not to --cc
> 'linux-arm-kernel@lists.infradead.org' --cc
> 'linux-kernel@vger.kernel.org' --cc 'linux-doc@vger.kernel.org' --cc
> 'devicetree@vger.kernel.org' --cc linux-omap@vger.kernel.org ?
no, my bad.
>
>
> please repost with a proper cover-letter to all appropriate lists.
sure will resend. I don't think cover-letter is necessary here since it will
just have the same info of the commit log.
Thanks
Kishon
prev parent reply other threads:[~2015-03-13 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 15:12 Kishon Vijay Abraham I
2015-03-13 15:13 ` [PATCH 2/2] bus: ocp2scp: SYNC2 value should be changed to 0x6 Kishon Vijay Abraham I
2015-03-13 15:15 ` [PATCH 1/2] ARM: dts: am4372: Add "ti,am437x-ocp2scp" as compatible string for OCP2SCP Nishanth Menon
2015-03-13 15:31 ` Kishon Vijay Abraham I [this message]
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=550302C5.9050809@ti.com \
--to=kishon@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=praneeth@ti.com \
--cc=tony@atomide.com \
/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
Powered by JetHome