From: Nikita Travkin <nikita@trvn.ru>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Anton Bambura <jenneron@postmarketos.org>,
Stephan Gerhold <stephan@gerhold.net>
Subject: Re: [PATCH v2 2/3] arm64: dts: qcom: msm8916-wingtech-wt865x8: Add Lenovo A6000/A6010
Date: Tue, 23 Jul 2024 20:25:50 +0500 [thread overview]
Message-ID: <bb270fce3c78314ffc5ac8590cc3685c@trvn.ru> (raw)
In-Reply-To: <0d982452-f41c-400e-b350-3c022927036c@linaro.org>
Konrad Dybcio писал(а) 23.07.2024 16:24:
> On 22.07.2024 2:47 PM, Nikita Travkin wrote:
>> From: Anton Bambura <jenneron@postmarketos.org>
>>
>> Add initial device-tree for Lenovo A6000 (wt86518) and Lenovo A6010
>> (wt86528), which are MSM8916-based devices. These devices are quite
>> similar, so some configuration is shared in msm8916-wingtech-wt865x8.dtsi.
>
> [...]
>
>
>> +/ {
>> + model = "Lenovo A6000 (Wingtech WT86518)";
>> + compatible = "wingtech,wt86518", "qcom,msm8916";
>> + chassis-type = "handset";
>> +
>> + speaker_amp: audio-amplifier {
>> + compatible = "awinic,aw8738";
>> +
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&spk_ext_pa_default>;
>
> flip
Oops, missed this one, will fix.
>
> [...]
>
>> +&sound {
>> + model = "wt88047";
>> + widgets =
>> + "Speaker", "Speaker",
>> + "Headphone", "Headphones";
>
> Please don't start a new line for this (same below)
>
Ack, will re-align.
>> + pin-switches = "Speaker", "Headphones";
>> + audio-routing =
>> + "Speaker", "Speaker Amp OUT",
>> + "Speaker Amp IN", "HPH_R",
>
> [...]
>
>> + /* left AW8736 */
>> + speaker_amp_left: audio-amplifier-left {
>> + compatible = "awinic,aw8738";
>
> Should this get a new compatible (with a fallback if sw-compatible)?
>
Per my understanding those two are supposed to be effectively same
chip, not sure if there is any point in adding a new compatible/fallback
in this case...
Thanks for looking at this!
Nikita
>> +
>> + pinctrl-0 = <&spk_ext_pa_left_default>;
>> + pinctrl-names = "default";
>> +
>> + mode-gpios = <&tlmm 119 GPIO_ACTIVE_HIGH>;
>> + sound-name-prefix = "Speaker Amp L";
>> + awinic,mode = <3>;
>> + };
>> +
>> + /* right AW8736 */
>> + speaker_amp_right: audio-amplifier-right {
>> + compatible = "awinic,aw8738";
>
> ditto
>
> Konrad
next prev parent reply other threads:[~2024-07-23 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 12:47 [PATCH v2 0/3] Introduce msm8916/39 based Lenovo devices Nikita Travkin
2024-07-22 12:47 ` [PATCH v2 1/3] dt-bindings: arm: qcom: Add " Nikita Travkin
2024-07-24 6:23 ` Krzysztof Kozlowski
2024-07-24 6:37 ` Nikita Travkin
2024-07-22 12:47 ` [PATCH v2 2/3] arm64: dts: qcom: msm8916-wingtech-wt865x8: Add Lenovo A6000/A6010 Nikita Travkin
2024-07-23 11:24 ` Konrad Dybcio
2024-07-23 15:25 ` Nikita Travkin [this message]
2024-07-22 12:47 ` [PATCH v2 3/3] arm64: dts: qcom: msm8939-wingtech-wt82918: Add Lenovo Vibe K5 devices Nikita Travkin
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=bb270fce3c78314ffc5ac8590cc3685c@trvn.ru \
--to=nikita@trvn.ru \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=jenneron@postmarketos.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stephan@gerhold.net \
--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