From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Liviu Dudau <liviu@dudau.co.uk>
Cc: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Paul Burton" <paulburton@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 0/2] mips: dts: ralink: Add support for TP-Link HC220 G5 v1 board
Date: Fri, 9 Jun 2023 10:24:10 +0200 [thread overview]
Message-ID: <20230609082410.GL8160@alpha.franken.de> (raw)
In-Reply-To: <20230606211600.1601694-1-liviu@dudau.co.uk>
On Tue, Jun 06, 2023 at 10:15:58PM +0100, Liviu Dudau wrote:
> Add device tree and bindings for the TP-Link HC220 G5 v1 wireless AP,
> a consumer product from TP-Link based on MT7621.
>
> Changes since v3:
> - Turns out that adding sub-nodes to the pcie invites more warnings from
> dtbs_check so we're dropping those
> - Running dtbs_check made me realise that I need to re-order the patches
> so that the bindings are introduced first. Hence the major change in v4
> is the re-ordering of patches
> - Renamed the LEDs nodes to match the schema.
>
> Changes since v2:
> - Remove WIP nodes for NAND flash that accidentally got included in v2
> - Fix commit message with the actual 5GHz WiFi chip name
> - Remove gmac and mdio nodes from device tree as defaults are sufficient
> - Added sub-nodes under pcie for each of the WiFi chip with appropriate
> compatible string.
> - Collect Acks received for the device tree bindings patch
>
> Changes since v1:
> - Changed compatible for the board to "tplink,hc220-g5-v1"
> - Updated the DSA switch nodes to better reflect actual usage.
> - Disabled the fixed-link in gmac1
> - Added device tree bindings in Documentation/
>
> v3: https://lore.kernel.org/linux-mips/20230605150114.601102-1-liviu@dudau.co.uk/
> v2: https://lore.kernel.org/linux-mips/20230529150833.526084-1-liviu@dudau.co.uk/
> v1: https://lore.kernel.org/linux-mips/20230509200125.309026-1-liviu@dudau.co.uk/
>
> Liviu Dudau (2):
> dt-bindings: mips: Add bindings for TP-Link HC220 G5 v1 board
> mips: dts: ralink: Add support for TP-Link HC220 G5 v1 board
>
> .../devicetree/bindings/mips/ralink.yaml | 1 +
> arch/mips/boot/dts/ralink/Makefile | 3 +-
> .../dts/ralink/mt7621-tplink-hc220-g5-v1.dts | 84 +++++++++++++++++++
> 3 files changed, 87 insertions(+), 1 deletion(-)
> create mode 100644 arch/mips/boot/dts/ralink/mt7621-tplink-hc220-g5-v1.dts
>
> --
> 2.40.1
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2023-06-09 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 21:15 [PATCH v4 0/2] mips: dts: ralink: Add support for TP-Link HC220 G5 v1 board Liviu Dudau
2023-06-06 21:15 ` [PATCH v4 1/2] dt-bindings: mips: Add bindings " Liviu Dudau
2023-06-06 21:16 ` [PATCH v4 2/2] mips: dts: ralink: Add support " Liviu Dudau
2023-06-07 5:48 ` Arınç ÜNAL
2023-06-07 6:34 ` Sergio Paracuellos
2023-06-09 8:24 ` Thomas Bogendoerfer [this message]
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=20230609082410.GL8160@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=arinc.unal@arinc9.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=liviu@dudau.co.uk \
--cc=paulburton@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sergio.paracuellos@gmail.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