From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: Liviu Dudau <liviu@dudau.co.uk>
Cc: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Paul Burton" <paulburton@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"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 2/2] mips: dts: ralink: Add support for TP-Link HC220 G5 v1 board
Date: Wed, 7 Jun 2023 08:34:46 +0200 [thread overview]
Message-ID: <CAMhs-H-b-RmxSKsXpFjRby4XLTx3S0_M-dV-fffHueRSmebLRw@mail.gmail.com> (raw)
In-Reply-To: <20230606211600.1601694-3-liviu@dudau.co.uk>
On Tue, Jun 6, 2023 at 11:16 PM Liviu Dudau <liviu@dudau.co.uk> wrote:
>
> This WiFi AP is based on a MT7621 SoC with 128MiB RAM, 128MiB NAND,
> a MT7603 2.4GHz WiFi and a MT7613 5GHz WiFi chips integrated on the board,
> connected to the main SoC over PCIe.
>
> The device uses NMBM over NAND, which is not currently supported in the
> mainline, so NAND node is skipped in this revision.
>
> Signed-off-by: Liviu Dudau <liviu@dudau.co.uk>
> ---
> arch/mips/boot/dts/ralink/Makefile | 3 +-
> .../dts/ralink/mt7621-tplink-hc220-g5-v1.dts | 84 +++++++++++++++++++
> 2 files changed, 86 insertions(+), 1 deletion(-)
Acked-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Thanks,
Sergio Paracuellos
next prev parent reply other threads:[~2023-06-07 6:36 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 [this message]
2023-06-09 8:24 ` [PATCH v4 0/2] " Thomas Bogendoerfer
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=CAMhs-H-b-RmxSKsXpFjRby4XLTx3S0_M-dV-fffHueRSmebLRw@mail.gmail.com \
--to=sergio.paracuellos@gmail.com \
--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=tsbogend@alpha.franken.de \
/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).