From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Gabor Juhos <j4g8y7@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: add TP-Link Archer AX55 v1
Date: Tue, 12 Mar 2024 21:37:49 +0100 [thread overview]
Message-ID: <6cbc2741-db0f-4acb-a9e1-45b3df1292d5@linaro.org> (raw)
In-Reply-To: <20240226-archer-ax55-v1-v2-2-3776eb61f432@gmail.com>
On 2/26/24 18:12, Gabor Juhos wrote:
> Add device tree source for the TP-Link Archer AX55 v1 [1]
> which is a dual-band WiFi router based on the IPQ5018 SoC.
>
> At the moment, only the UART, the GPIO LEDs and buttons
> are usable, but it makes it possible to boot an initramfs
> image on the device.
>
> The device tree can be extended in the future, once support
> for other periherals will be available for the platform.
>
> 1. https://www.tp-link.com/en/home-networking/wifi-router/archer-ax55/v1/
>
> Signed-off-by: Gabor Juhos <j4g8y7@gmail.com>
> ---
[...]
> +
> +&uart1_pins {
> + /*
> + * Remove "gpio31" from the default pins in order to be able
> + * to use that for the WPS button.
> + */
> + pins = "gpio32", "gpio33", "gpio34";
I believe you can even shorten it down to gpio32/33, 4pin uart
screams flow control, and I'm not sure if it's there only one-way
Konrad
next prev parent reply other threads:[~2024-03-12 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 17:12 [PATCH v2 0/2] arm64: add minimal boot support for TP-Link Archer AX55 v1 Gabor Juhos
2024-02-26 17:12 ` [PATCH v2 1/2] dt-bindings: arm: qcom: add " Gabor Juhos
2024-02-26 17:12 ` [PATCH v2 2/2] arm64: dts: " Gabor Juhos
2024-03-12 20:37 ` Konrad Dybcio [this message]
2024-03-13 15:44 ` Gabor Juhos
2024-02-27 13:45 ` [PATCH v2 0/2] arm64: add minimal boot support for " Rob Herring
2024-02-27 14:51 ` Gabor Juhos
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=6cbc2741-db0f-4acb-a9e1-45b3df1292d5@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j4g8y7@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).