linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Heiko Stübner" <heiko@sntech.de>, "Yao Zi" <ziyao@disroot.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Jiri Slaby" <jirislaby@kernel.org>,
	"Chris Morgan" <macromorgan@hotmail.com>,
	"Jonas Karlman" <jonas@kwiboo.se>,
	"Tim Lunn" <tim@feathertop.org>, "Andy Yan" <andyshrk@163.com>,
	"Muhammed Efe Cetin" <efectn@protonmail.com>,
	"Jagan Teki" <jagan@edgeble.ai>,
	"Dragan Simic" <dsimic@manjaro.org>,
	"Ondrej Jirman" <megi@xff.cz>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH 3/4] arm64: dts: rockchip: Add base DT for rk3528 SoC
Date: Sun, 4 Aug 2024 16:09:09 +0200	[thread overview]
Message-ID: <6bba3607-04c6-4d6d-942c-21859bfa9b74@kernel.org> (raw)
In-Reply-To: <10507028.U7f9L36N0a@diego>

On 04/08/2024 14:49, Heiko Stübner wrote:
> 
>>> +		compatible = "fixed-clock";
>>> +		#clock-cells = <0>;
>>> +		clock-frequency = <24000000>;
>>> +		clock-output-names = "xin24m";
>>> +	};
>>> +
>>> +	gic: interrupt-controller@fed01000 {
>>
>> Why this all is outside of SoC?
> 
> I guess you mean outside of a "soc {}" node?
> 
> Here the rk3528 simply follows all other Rockchip SoCs :-) .
> 
> Digging into the history, the first rk3066a and initial rk3288 submission
> did use a soc {} node, which later got removed as suggested by arm-soc
> maintainers at the time [0].
> 
> I guess that changed since then?

Well, referenced patch was mixing MMIO with non-MMIO, so Olof's comment
could be understood that this is not correct approach. Even though DT
spec shows examples of "soc", it is not required. But then how do you
implement any ordering? By name or by unit address?

IOW, I think this is the only platform not using "soc" nodes.

Best regards,
Krzysztof



  reply	other threads:[~2024-08-04 14:10 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-03 12:55 [PATCH 0/4] Add initial support for Rockchip RK3528 SoC Yao Zi
2024-08-03 12:55 ` [PATCH 1/4] dt-bindings: serial: snps-dw-apb-uart: Document Rockchip RK3528 Yao Zi
2024-08-04 10:01   ` Krzysztof Kozlowski
2024-08-10 21:25   ` Heiko Stübner
2024-08-03 12:55 ` [PATCH 2/4] dt-bindings: arm: rockchip: Add Radxa E20C board Yao Zi
2024-08-04 10:02   ` Krzysztof Kozlowski
2024-08-03 12:55 ` [PATCH 3/4] arm64: dts: rockchip: Add base DT for rk3528 SoC Yao Zi
2024-08-04 10:05   ` Krzysztof Kozlowski
2024-08-04 12:49     ` Heiko Stübner
2024-08-04 14:09       ` Krzysztof Kozlowski [this message]
2024-08-04 13:20     ` Yao Zi
2024-08-04 13:25       ` Dragan Simic
2024-08-04 13:44         ` Heiko Stübner
2024-08-04 13:59           ` Dragan Simic
2024-08-04 15:51             ` Heiko Stübner
2024-08-05  5:16               ` Krzysztof Kozlowski
2024-08-05  5:22               ` Dragan Simic
2024-08-04 13:58         ` Yao Zi
2024-08-04 14:05       ` Krzysztof Kozlowski
2024-08-05 10:59         ` Yao Zi
2024-08-05 11:37           ` Dragan Simic
2024-08-05 11:47             ` Heiko Stübner
2024-08-05 16:22               ` Yao Zi
2024-08-05 17:02                 ` Krzysztof Kozlowski
2024-08-05 19:13                 ` Dragan Simic
2024-08-13 16:38         ` Krzysztof Kozlowski
2024-08-14 15:21           ` Heiko Stübner
2024-08-15 16:44           ` Heiko Stübner
2024-08-16  5:57             ` Krzysztof Kozlowski
2024-08-04 11:27   ` Diederik de Haas
2024-08-04 13:22     ` Yao Zi
2024-08-03 12:55 ` [PATCH 4/4] arm64: dts: rockchip: Add Radxa e20c board Yao Zi
2024-08-03 13:52   ` Yao Zi
2024-08-04  5:40 ` [PATCH 0/4] Add initial support for Rockchip RK3528 SoC Dragan Simic
2024-08-04  6:22   ` Yao Zi
2024-08-04  9:13     ` Piotr Oniszczuk
2024-08-04 13:27       ` Yao Zi

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=6bba3607-04c6-4d6d-942c-21859bfa9b74@kernel.org \
    --to=krzk@kernel.org \
    --cc=andyshrk@163.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=efectn@protonmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=jagan@edgeble.ai \
    --cc=jirislaby@kernel.org \
    --cc=jonas@kwiboo.se \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=macromorgan@hotmail.com \
    --cc=megi@xff.cz \
    --cc=robh@kernel.org \
    --cc=tim@feathertop.org \
    --cc=ziyao@disroot.org \
    /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;
as well as URLs for NNTP newsgroup(s).