From: David Woodhouse <dwmw2@infradead.org>
To: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Frank Wunderlich <frank-w@public-files.de>
Cc: devicetree@vger.kernel.org, Ryder Lee <ryder.lee@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Frank Wunderlich <linux@fw-web.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] arm: dts: mt7623: move more display-related nodes to mt7623n.dtsi
Date: Mon, 10 Aug 2020 08:48:46 +0100 [thread overview]
Message-ID: <cefc273c226c93c605f4dc76afa9eb5aacceaf26.camel@infradead.org> (raw)
In-Reply-To: <CAAOTY_9o_hBWxWBdDoeeJ6zuV4rb4R_yEoN5+L0uHBGMw4Kduw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
On Sun, 2020-08-09 at 08:16 +0800, Chun-Kuang Hu wrote:
> I would like to put all device in mt7623.dtsi with some device's
> status is "disabled" and change its status in platform dtsi.
> I would like to see all device in mt7623.dtsi because of its name. If
> you move some device to platform dtsi, we would trace all platform
> dtsi to find out how many device in mt7623. One day a new platform
> enable different devices, you would reorganize all these platform
> dtsi?
No, this isn't "platform dtsi", surely? This is mt7623a and mt7623n
dtsi for the two different SoCs, and platforms then just include
mt7623a.dtsi or mt7623n.dtsi as appropriate for the SoC they are using.
If you really want *all* the nodes for both MT7623A and MT7623N chips
in a single mt7623.dtsi but disabled, could we still have mt7623a.dtsi
and mt7623n.dtsi for the chips, enabling the nodes that are only-for-A
or only-for-N, so that each platform doesn't have to do that for
itself?
Although putting those nodes that exist only in one chip or the other
directly into the mt7623[an].dtsi still seems to make more sense to
me.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2020-08-10 7:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 8:27 Frank Wunderlich
2020-08-07 8:27 ` [PATCH 1/2] arm: dts: mt7623: move more display-related nodes to mt7623n.dtsi Frank Wunderlich
2020-08-08 12:27 ` Aw: " Frank Wunderlich
2020-08-09 0:16 ` Chun-Kuang Hu
2020-08-09 7:21 ` Frank Wunderlich
2020-08-10 0:06 ` Chun-Kuang Hu
2020-08-10 5:39 ` Frank Wunderlich
2020-08-10 7:48 ` David Woodhouse [this message]
2020-08-10 23:28 ` Chun-Kuang Hu
2020-08-11 8:41 ` Frank Wunderlich
2020-08-11 9:35 ` David Woodhouse
2020-08-18 7:16 ` Aw: " Frank Wunderlich
2020-08-18 7:36 ` David Woodhouse
2020-08-18 7:45 ` Aw: " Frank Wunderlich
2020-08-07 8:27 ` [PATCH 2/2] arm: dts: mt7623: add display subsystem related device nodes Frank Wunderlich
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=cefc273c226c93c605f4dc76afa9eb5aacceaf26.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=chunkuang.hu@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@fw-web.de \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@mediatek.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).