[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b15816d2df435378c113766796a878a949286feb.camel@infradead.org>
Date: Tue, 11 Aug 2020 10:35:00 +0100
From: David Woodhouse <dwmw2@...radead.org>
To: frank-w@...lic-files.de, linux-mediatek@...ts.infradead.org,
Chun-Kuang Hu <chunkuang.hu@...nel.org>
Cc: devicetree@...r.kernel.org, Ryder Lee <ryder.lee@...iatek.com>,
Sean Wang <sean.wang@...iatek.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Frank Wunderlich <linux@...web.de>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 1/2] arm: dts: mt7623: move more display-related nodes
to mt7623n.dtsi
On Tue, 2020-08-11 at 10:41 +0200, Frank Wunderlich wrote:
> 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).
Agreed.
I see all three (now I added U7623) MT7623A platforms add the built-in
Ethernet switch for themselves, so I'll probably move that to
mt7623a.dtsi on top of the series that we're already using. But that
can come later.
Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (5174 bytes)
Powered by blists - more mailing lists