From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Gabor Juhos <j4g8y7@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.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 2/3] arm64: dts: qcom: ipq5018-tplink-archer-ax55-v1: add 'qcom,ipq0518' compatible
Date: Tue, 20 Oct 2026 09:40:51 +0200 [thread overview]
Message-ID: <bcdc5f69-bce4-424e-b498-893a95f3cdc6@oss.qualcomm.com> (raw)
In-Reply-To: <20261007-tplink-ax55-v1-ipq0518-v1-2-0ef058756596@gmail.com>
On 10/7/26 6:59 PM, Gabor Juhos wrote:
> The TP-Link Archer AX55 v1 board is based on the IPQ0518 SoC, so add a
> new 'qcom,ipq0518' compatible string to the board dts file.
>
> Since the SoC is a trimmed down version of IPQ5018, keep the 'qcom,ipq5018'
> compatible string as a fallback.
>
> Signed-off-by: Gabor Juhos <j4g8y7@gmail.com>
> ---
The naming is really confusing indeed
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2026-10-20 7:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 16:59 [PATCH 0/3] add 'qcom,ipq0518' compatible for the TP-Link Archer AX55 v1 Gabor Juhos
2026-10-07 16:59 ` [PATCH 1/3] dt-bindings: arm: qcom: add 'qcom,ipq0518' compatible for " Gabor Juhos
2026-10-12 7:21 ` Krzysztof Kozlowski
2026-10-07 16:59 ` [PATCH 2/3] arm64: dts: qcom: ipq5018-tplink-archer-ax55-v1: add 'qcom,ipq0518' compatible Gabor Juhos
2026-10-20 7:40 ` Konrad Dybcio [this message]
2026-10-07 16:59 ` [PATCH 3/3] arm64: dts: qcom: ipq5018-tplink-archer-ax55-v1: use 'ipq0518' prefix for dts Gabor Juhos
2026-10-09 10:15 ` Krzysztof Kozlowski
2026-10-09 13:30 ` Gabor Juhos
2026-10-20 7:41 ` Konrad Dybcio
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=bcdc5f69-bce4-424e-b498-893a95f3cdc6@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j4g8y7@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®