public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>, <t-kristo@ti.com>, <nm@ti.com>
Cc: <mark.rutland@arm.com>, <devicetree@vger.kernel.org>,
	<robh+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/9] arm64: dts: ti: k3-am65-main: Correct main NAVSS representation
Date: Thu, 23 Jan 2020 11:46:18 +0200	[thread overview]
Message-ID: <52078b70-b5dd-103a-45ea-55fd36cba480@ti.com> (raw)
In-Reply-To: <469a35b0-9b60-7faf-2b1b-a77f9f502a50@ti.com>



On 23/01/2020 10.32, Lokesh Vutla wrote:
> 
> 
> On 22/01/20 5:09 PM, Peter Ujfalusi wrote:
>>
>>
>> On 22/01/2020 13.03, Lokesh Vutla wrote:
>>>
>>>
>>> On 22/01/20 1:56 PM, Peter Ujfalusi wrote:
>>>> NAVSS is a subsystem containing different IPs, it is not really a bus.
>>>> Change the compatible from "simple-bus" to "simple-mfd" to reflect that.
>>>>
>>>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>>>> ---
>>>>  arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 4 ++--
>>>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
>>>> index efb24579922c..e40f7acbec42 100644
>>>> --- a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
>>>> +++ b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
>>>> @@ -385,8 +385,8 @@ intr_main_gpio: interrupt-controller0 {
>>>>  		ti,sci-rm-range-girq = <0x1>;
>>>>  	};
>>>>  
>>>> -	cbass_main_navss: interconnect0 {
>>>> -		compatible = "simple-bus";
>>>> +	cbass_main_navss: navss@30800000 {
>>>
>>> This introduces below dtc warning when built with W=1
>>>
>>> arch/arm64/boot/dts/ti/k3-am65-main.dtsi:388.35-530.4: Warning
>>> (unit_address_vs_reg): /interconnect@100000/navss@30800000: node has a unit
>>> name, but no reg property
>>
>> Interesting, the example in
>> Documentation/devicetree/bindings/dma/ti/k3-udma.yaml
>>
>> is basically the same and dt_binding_check is happy about it:
>> DTC     Documentation/devicetree/bindings/dma/ti/k3-udma.example.dt.yaml
>> CHECK   Documentation/devicetree/bindings/dma/ti/k3-udma.example.dt.yaml
>>
>> but it screamed when I had the simple-bus in there (copied from the
>> existing dtsi file).
>>
>> The node name for simple-bus _must_ be
>> '^(bus|soc|axi|ahb|apb)(@[0-9a-f]+)?$'
>>
>> I would not use any of these to NAVSS node...
>>
>>> this is representing cbass inside main_navss, just like cbass_main. You can drop
>>> this patch and the similar mcu version.
>>
>> According to Documentation/devicetree/bindings/mfd/mfd.txt:
>> - compatible : "simple-mfd" - this signifies that the operating system
>>   should consider all subnodes of the MFD device as separate devices
>>   akin to how "simple-bus" indicates when to see subnodes as children
>>   for a simple memory-mapped bus.
>>
>> NAVSS is falling into simple-mfd as the devices under it are independent
>> devices.
> 
> okay, may be rename cbass_main_navss to main_navss.

Actually we don't even need label for any of the NAVSS nodes.

> 
> Thanks and regards,
> Lokesh
> 
>>
>>>
>>> Thanks and regards,
>>> Lokesh
>>>
>>>> +		compatible = "simple-mfd";
>>>>  		#address-cells = <2>;
>>>>  		#size-cells = <2>;
>>>>  		ranges;
>>>>
>>
>> - Péter
>>
>> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
>> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
>>

- Péter

Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

  reply	other threads:[~2020-01-23  9:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22  8:26 [PATCH v2 0/9] arm64: dts: ti: UDMAP and McASP support Peter Ujfalusi
2020-01-22  8:26 ` [PATCH v2 1/9] arm64: dts: ti: k3-am65-main: Correct main NAVSS representation Peter Ujfalusi
2020-01-22 11:03   ` Lokesh Vutla
2020-01-22 11:39     ` Peter Ujfalusi
2020-01-23  8:32       ` Lokesh Vutla
2020-01-23  9:46         ` Peter Ujfalusi [this message]
2020-01-22  8:26 ` [PATCH v2 2/9] arm64: dts: ti: k3-am65-main: Move secure proxy under cbass_main_navss Peter Ujfalusi
2020-01-22  8:26 ` [PATCH v2 3/9] arm64: dts: ti: k3-am65: DMA support Peter Ujfalusi
2020-01-22  8:26 ` [PATCH v2 4/9] arm64: dts: ti: k3-j721e: Correct the address for MAIN NAVSS Peter Ujfalusi
2020-01-22  8:26 ` [PATCH v2 5/9] arm64: dts: ti: k3-j721e-main: Correct main NAVSS representation Peter Ujfalusi
2020-01-22  8:26 ` [PATCH v2 6/9] arm64: dts: ti: k3-j721e-main: Move secure proxy and smmu under main_navss Peter Ujfalusi
2020-01-22  8:26 ` [PATCH v2 7/9] arm64: dts: ti: k3-j721e: DMA support Peter Ujfalusi
2020-01-22  8:26 ` [PATCH v2 8/9] arm64: dts: ti: k3-am654-main: Add McASP nodes Peter Ujfalusi
2020-01-22  8:26 ` [PATCH v2 9/9] arm64: dts: ti: k3-j721e-main: " Peter Ujfalusi

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=52078b70-b5dd-103a-45ea-55fd36cba480@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=mark.rutland@arm.com \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=t-kristo@ti.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