From: Martin Botka <martin.botka@somainline.org>
To: Lux Aliaga <they@mint.lgbt>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
~postmarketos/upstreaming@lists.sr.ht,
marijn.suijten@somainline.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 5/6] dt-bindings: arm: qcom: Document xiaomi,laurel-sprout board
Date: Sat, 31 Dec 2022 23:50:33 +0100 [thread overview]
Message-ID: <942SNR.IMR405HRPE6J@somainline.org> (raw)
In-Reply-To: <20221231222420.75233-6-they@mint.lgbt>
On Sat, Dec 31 2022 at 07:24:19 PM -03:00:00, Lux Aliaga
<they@mint.lgbt> wrote:
> Document the Xiaomi Mi A3 (xiaomi-laurel-sprout) smartphone which is
> based on the Snapdragon 665 SoC.
>
> Signed-off-by: Lux Aliaga <they@mint.lgbt>
> ---
> Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml
> b/Documentation/devicetree/bindings/arm/qcom.yaml
> index 27063a045bd0..4923dafb5d7a 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -793,6 +793,7 @@ properties:
> - items:
> - enum:
> - sony,pdx201
> + - xiaomi,laurel-sprout
From what i can see laurel_sprout is the correct and official codename
for the device.
Not sure here at all but should we maybe use that as it is the official
codename ?
-Martin
> - const: qcom,sm6125
>
> - items:
> --
> 2.38.1
>
next prev parent reply other threads:[~2022-12-31 22:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221231222420.75233-1-they@mint.lgbt>
2022-12-31 22:24 ` [PATCH v5 1/6] dt-bindings: ufs: qcom: Add SM6125 compatible string Lux Aliaga
2022-12-31 22:29 ` Lux Aliaga
2022-12-31 22:32 ` [PATCH v5 0/6] arm64: dts: qcom: sm6125: UFS and xiaomi-laurel-sprout support Lux Aliaga
2022-12-31 22:53 ` [PATCH v5 1/6] dt-bindings: ufs: qcom: Add SM6125 compatible string Martin Botka
2023-01-01 15:40 ` Krzysztof Kozlowski
2022-12-31 22:24 ` [PATCH v5 2/6] dt-bindings: phy: Add QMP UFS PHY compatible for SM6125 Lux Aliaga
2022-12-31 22:53 ` Martin Botka
2023-01-03 11:20 ` Dhruva Gole
2023-01-08 20:15 ` Rob Herring
2023-01-08 22:20 ` Lux Aliaga
2022-12-31 22:24 ` [PATCH v5 4/6] arm64: dts: qcom: sm6125: Add UFS nodes Lux Aliaga
2023-01-01 15:41 ` Krzysztof Kozlowski
2022-12-31 22:24 ` [PATCH v5 5/6] dt-bindings: arm: qcom: Document xiaomi,laurel-sprout board Lux Aliaga
2022-12-31 22:50 ` Martin Botka [this message]
2023-01-01 18:54 ` Lux Aliaga
2023-01-01 15:40 ` Krzysztof Kozlowski
2023-01-01 18:55 ` Lux Aliaga
2022-12-31 22:24 ` [PATCH v5 6/6] arm64: dts: qcom: sm6125: Initial support for xiaomi-laurel-sprout Lux Aliaga
2023-01-01 15:44 ` Krzysztof Kozlowski
2023-01-01 23:39 ` Marijn Suijten
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=942SNR.IMR405HRPE6J@somainline.org \
--to=martin.botka@somainline.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robh+dt@kernel.org \
--cc=they@mint.lgbt \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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