From: Rob Herring <robh@kernel.org>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, kuba@kernel.org, matthias.bgg@gmail.com,
linux-mediatek@lists.infradead.org, nbd@nbd.name,
john@phrozen.org, sean.wang@mediatek.com,
Mark-MC.Lee@mediatek.com, lorenzo.bianconi@redhat.com,
daniel@makrotopia.org, krzysztof.kozlowski+dt@linaro.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 net-next 00/10] mtk: wed: move cpuboot, ilm and dlm in dedicated dts nodes
Date: Thu, 6 Apr 2023 10:25:11 -0500 [thread overview]
Message-ID: <20230406152511.GA3117403-robh@kernel.org> (raw)
In-Reply-To: <cover.1680268101.git.lorenzo@kernel.org>
On Fri, Mar 31, 2023 at 03:12:36PM +0200, Lorenzo Bianconi wrote:
> Since cpuboot, ilm and dlm memory region are not part of MT7986 SoC RAM,
That's not really a requirement. Is that the only "problem" here?
Certainly going from a standard binding to a custom phandle reference is
not an improvement.
> move them in dedicated mt7986a syscon dts nodes.
What makes them a syscon? Are they memory or h/w registers? Can't be
both...
Perhaps mmio-sram?
> At the same time we keep backward-compatibility with older dts version where
> cpuboot, ilm and dlm were defined as reserved-memory child nodes.
Doesn't really seem big enough issue to justify carrying this.
Rob
next prev parent reply other threads:[~2023-04-06 15:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 13:12 [PATCH v2 net-next 00/10] mtk: wed: move cpuboot, ilm and dlm in dedicated dts nodes Lorenzo Bianconi
2023-03-31 13:12 ` [PATCH v2 net-next 01/10] net: ethernet: mtk_wed: rename mtk_wed_get_memory_region in mtk_wed_get_reserved_memory_region Lorenzo Bianconi
2023-03-31 13:12 ` [PATCH v2 net-next 02/10] net: ethernet: mtk_wed: move cpuboot in a dedicated dts node Lorenzo Bianconi
2023-04-04 7:44 ` Paolo Abeni
2023-04-04 8:06 ` Lorenzo Bianconi
2023-03-31 13:12 ` [PATCH v2 net-next 03/10] dt-bindings: soc: mediatek: " Lorenzo Bianconi
2023-03-31 13:12 ` [PATCH v2 net-next 04/10] arm64: dts: mt7986: move cpuboot in a dedicated node Lorenzo Bianconi
2023-03-31 13:12 ` [PATCH v2 net-next 05/10] net: ethernet: mtk_wed: move ilm a dedicated dts node Lorenzo Bianconi
2023-03-31 13:12 ` [PATCH v2 net-next 06/10] dt-bindings: soc: mediatek: move ilm in " Lorenzo Bianconi
2023-04-06 8:50 ` Paolo Abeni
2023-03-31 13:12 ` [PATCH v2 net-next 07/10] arm64: dts: mt7986: move ilm in a dedicated node Lorenzo Bianconi
2023-03-31 13:12 ` [PATCH v2 net-next 08/10] net: ethernet: mtk_wed: move dlm a dedicated dts node Lorenzo Bianconi
2023-03-31 13:12 ` [PATCH v2 net-next 09/10] dt-bindings: soc: mediatek: move dlm in " Lorenzo Bianconi
2023-03-31 13:12 ` [PATCH v2 net-next 10/10] arm64: dts: mt7986: move dlm in a dedicated node Lorenzo Bianconi
2023-04-06 15:25 ` Rob Herring [this message]
2023-04-10 14:54 ` [PATCH v2 net-next 00/10] mtk: wed: move cpuboot, ilm and dlm in dedicated dts nodes Lorenzo Bianconi
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=20230406152511.GA3117403-robh@kernel.org \
--to=robh@kernel.org \
--cc=Mark-MC.Lee@mediatek.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=john@phrozen.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.wang@mediatek.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;
as well as URLs for NNTP newsgroup(s).