From: Matthias Brugger <matthias.bgg@gmail.com>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Frank Wunderlich <frank-w@public-files.de>,
erkin.bozoglu@xeront.com, Sean Wang <sean.wang@mediatek.com>,
DENG Qingfang <dqfext@gmail.com>
Subject: Re: [PATCH 0/5] arm: dts: mt7623: relocate gmacs, mt7530 switch, and mux phy
Date: Wed, 25 Jan 2023 16:03:04 +0100 [thread overview]
Message-ID: <e6e91635-b8ce-787a-96e6-dd8b066f8c0a@gmail.com> (raw)
In-Reply-To: <20230120205318.519493-1-arinc.unal@arinc9.com>
On 20/01/2023 21:53, Arınç ÜNAL wrote:
> Yeia sou!
>
γεια σας!
Whole series applied, thanks!
> I initially just wanted to submit the phy muxing patch for BPI-R2 but after
> looking around the bindings, I decided to do a bit of a cleanup.
>
> The main takeaway of the cleanup is that the MT7530 switch is actually a
> part of the multi-chip module on the MT7623AI SoC. I'm moving the bindings
> for this switch to mt7623a.dtsi so they don't need to be defined on every
> device with this SoC. This should ease it up for supporting more devices
> with MT7623AI SoC on mainline.
>
> I don't know if there's a pin wired for interrupt. The switch is going to
> work with polling for the time being. Folks from MediaTek, feel free to
> fill me in on this.
>
> I've tested phy muxing on my BPI-R2. DTs compile fine.
>
> Arınç ÜNAL (5):
> arm: dts: mt7623: add gmacs to mt7623.dtsi
> arm: dts: mt7623: add mt7530 switch to mt7623a.dtsi
> arm: dts: mt7623: change mt7530 switch address
> arm: dts: mt7623: mux phy0 on Bananapi BPI-R2
> arm: dts: mt7623: enable flow control on port@6
>
> arch/arm/boot/dts/mt7623.dtsi | 14 ++++
> arch/arm/boot/dts/mt7623a-rfb-emmc.dts | 86 ++++++----------------
> arch/arm/boot/dts/mt7623a-rfb-nand.dts | 86 ++++++----------------
> arch/arm/boot/dts/mt7623a.dtsi | 74 +++++++++++++++++++
> arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts | 22 +++---
> arch/arm/boot/dts/mt7623n-rfb-emmc.dts | 13 ++--
> 6 files changed, 147 insertions(+), 148 deletions(-)
>
>
next parent reply other threads:[~2023-01-25 15:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230120205318.519493-1-arinc.unal@arinc9.com>
2023-01-25 15:03 ` Matthias Brugger [this message]
[not found] ` <20230120205318.519493-5-arinc.unal@arinc9.com>
2023-01-25 16:41 ` [PATCH 4/5] arm: dts: mt7623: mux phy0 on Bananapi BPI-R2 Frank Wunderlich
2023-01-25 16:54 ` Arınç ÜNAL
2023-01-31 11:55 ` Matthias Brugger
2023-01-31 16:39 ` Aw: " Frank Wunderlich
2023-02-01 17:49 ` Arınç ÜNAL
[not found] ` <20230120205318.519493-2-arinc.unal@arinc9.com>
2023-01-25 16:45 ` [PATCH 1/5] arm: dts: mt7623: add gmacs to mt7623.dtsi Frank Wunderlich
2023-01-25 16:52 ` Arınç ÜNAL
2023-01-31 11:53 ` Matthias Brugger
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=e6e91635-b8ce-787a-96e6-dd8b066f8c0a@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=dqfext@gmail.com \
--cc=erkin.bozoglu@xeront.com \
--cc=frank-w@public-files.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=robh+dt@kernel.org \
--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).