public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Nishanth Menon <nm@ti.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Bao Cheng Su <baocheng.su@siemens.com>,
	Diogo Ivo <diogo.ivo@siemens.com>
Subject: Re: [PATCH v4 2/3] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain
Date: Mon, 26 Aug 2024 22:13:20 +0200	[thread overview]
Message-ID: <8de13103-cd57-407c-839c-843dcedbac29@siemens.com> (raw)
In-Reply-To: <20240826195930.c7bylbgu6qma2v3c@siren>

On 26.08.24 21:59, Nishanth Menon wrote:
> On 14:01-20240826, Jan Kiszka wrote:
>> On 26.08.24 13:42, Nishanth Menon wrote:
>>> On 13:31-20240826, Jan Kiszka wrote:
>>>> On 24.08.24 19:58, Nishanth Menon wrote:
>>>>> On 18:37-20240814, Jan Kiszka wrote:
>>>>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>>>>
>>>>>> Expand bindings to cover both the MCU and the main usage of the AM654
>>>>>> system controller.
>>>>>>
>>>>>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>>>>>> ---
>>>>>>  .../soc/ti/ti,am654-system-controller.yaml    | 19 +++++++++++++++++++
>>>>>>  1 file changed, 19 insertions(+)
>>>>>>
>>>>>> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
>>>>>> index e79803e586ca..cb9da3ec39a8 100644
>>>>>> --- a/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
>>>>>> +++ b/Documentation/devicetree/bindings/soc/ti/ti,am654-system-controller.yaml
>>>>>
>>>>> As per linux-next, this file does not exist? looks like you might need
>>>>> to rebase on latest next?
>>>>>
>>>>
>>>> "This goes on top of
>>>> https://patchwork.kernel.org/project/linux-arm-kernel/cover/20240518-dt-bindings-ti-soc-mfd-v1-0-b3952f104c9a@linaro.org/"
>>>>
>>>> Is that series obsolete by now?
>>>
>>> This dependency information would have been useful when provided under the
>>> diffstat section of the representative patch. :(
>>>
>>
>> Yeah, who reads cover letters? ;) Will try to do that next time.
> 
> Looking at what we included in v6.11, looks like the above series from
> krystoff will need to be re-thought through.
> [1] makes the patches un-necessary to an extent by modelling the node as
> a simple-bus - Looks like k3-am62-wakeup.dtsi was missed, but it should
> be trivial enough fixup. Did you try applying the series on latest next?
> it should not apply anymore (Doesn't apply on master either).
> 
> [1] https://lore.kernel.org/all/20240628151518.40100-1-afd@ti.com/
> 

Krystoff's and my patches still apply on top of master and next.

I don't mind via which patches we finally get to zero dtbs_check
warnings, just that we get there.

Jan

-- 
Siemens AG, Technology
Linux Expert Center



  reply	other threads:[~2024-08-26 20:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 16:37 [PATCH v4 0/3] arm64: dts: k3: Resolve remaining dtbs_check warnings Jan Kiszka
2024-08-14 16:37 ` [PATCH v4 1/3] arm64: dts: ti: k3-am642-evm: Silence schema warning Jan Kiszka
2024-08-14 16:37 ` [PATCH v4 2/3] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain Jan Kiszka
2024-08-15 15:24   ` Conor Dooley
2024-08-24 17:58   ` Nishanth Menon
2024-08-26 11:31     ` Jan Kiszka
2024-08-26 11:42       ` Nishanth Menon
2024-08-26 12:01         ` Jan Kiszka
2024-08-26 19:59           ` Nishanth Menon
2024-08-26 20:13             ` Jan Kiszka [this message]
2024-08-27 11:38               ` Nishanth Menon
2024-08-14 16:37 ` [PATCH v4 3/3] arm64: dts: ti: k3-am65-main: add system controller compatible Jan Kiszka
2024-08-24 19:54 ` (subset) [PATCH v4 0/3] arm64: dts: k3: Resolve remaining dtbs_check warnings Nishanth Menon

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=8de13103-cd57-407c-839c-843dcedbac29@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=baocheng.su@siemens.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=diogo.ivo@siemens.com \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@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