From: Frank Wunderlich <frank-w@public-files.de>
To: linux-mediatek@lists.infradead.org,
Chun-Kuang Hu <chunkuang.hu@kernel.org>,
David Woodhouse <dwmw2@infradead.org>
Cc: Ryder Lee <ryder.lee@mediatek.com>,
devicetree@vger.kernel.org, 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: Tue, 11 Aug 2020 10:41:10 +0200 [thread overview]
Message-ID: <363F05E9-8D03-4CFD-83C3-1E874DA34309@public-files.de> (raw)
In-Reply-To: <CAAOTY__4Qs93EMjrpK_jW4NsxyZf7w3RHa7vDSRecea_JwAxKw@mail.gmail.com>
Hi
Am 11. August 2020 01:28:25 MESZ schrieb Chun-Kuang Hu <chunkuang.hu@kernel.org>:
>Sorry I does not notice that mt7623a and mt7623n are different SoC.
>Because they are different SoC, I think the first step is to upstream
>mt7623a.dtsi and mt7623n.dtsi independently. That means in each dtsi,
>it include all devices of its SoC. After both dtsi is upsteamed, we
>could find out what is the common part, then we create a common dtsi
>these two SoC, for example mt7623a_mt7623n_common.dtsi. (Maybe there
>is a SoC's name is exactly 'mt7623', so I prefer mt7623.dtsi is
>reserved for that SoC, and mt7623_common.dtsi is not preferred because
>I don't know there are how many mt7623 family SoC and
>mt7623_common.dtsi should be use for all mt7623 family)
Afair there is only mt7623a and mt7623n. Mt7623a uses mt7623.dtsi as common part. These 2 soc are released 5 years ago...and only these 2 from that family).
https://www.mediatek.com/news-events/press-releases/mediatek-launches-the-mt7623-and-mt7683-multi-standard-iot-gateways-with-high-speed-wlan-to-lan-to-drive-the-secure-smart-home
So from my current pov the best way (to no more delay my hdmi series) is to move display related stuff in new mt7623n.dtsi and keep mt7623.dtsi as common. So we can avoid touching mt7623a.dtsi for now (can be done later if really needed).
regards Frank
next prev parent reply other threads:[~2020-08-11 8:41 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
2020-08-10 23:28 ` Chun-Kuang Hu
2020-08-11 8:41 ` Frank Wunderlich [this message]
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=363F05E9-8D03-4CFD-83C3-1E874DA34309@public-files.de \
--to=frank-w@public-files.de \
--cc=chunkuang.hu@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--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).