From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Douglas Anderson <dianders@chromium.org>,
Bjorn Andersson <andersson@kernel.org>
Cc: Sheng-Liang Pan <sheng-liang.pan@quanta.corp-partner.google.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andy Gross <agross@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
cros-qcom-dts-watchers@chromium.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sc7180: Reorganize trogdor rt5682 audio codec dts
Date: Sat, 26 Aug 2023 11:36:17 +0200 [thread overview]
Message-ID: <610a1b08-ced2-4e07-8b69-b2dd2749293e@linaro.org> (raw)
In-Reply-To: <20230816112143.2.I29a5a330b6994afca81871f74bbacaf55b155937@changeid>
On 16.08.2023 20:21, Douglas Anderson wrote:
> It was asserted that the "/delete-property/ VBAT-supply;" that we
> needed to do in the rt5682s dts fragment was ugly. Let's change up all
> the trogdor device trees to make it explicit which version of "rt5682"
> we have and avoid the need for the "delete-property".
>
> As a side effect, this nicely gets rid of the need for a delete-node
> in coachz, which doesn't use "rt5682" at all.
>
> A few notes:
> - This doesn't get rid of every "/delete-node/" in trogdor, just the
> one that was used for rt5682s.
> - Though we no longer have any "/delete-node/", we do still override
> the "model" in the "sound" node in one case (in pompom) since that
> uses the "2mic" sound setup.
>
> This is validated to produce the same result (other than a few
> properties being reordered) when taking the dtbs generated by the
> kernel build and then doing:
>
> for dtb in *trogdor*.dtb; do
> dtc -I dtb -O dts $dtb -o out/$dtb.dts;
> done
>
> Suggested-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
[...]
> +&mdss_dsi0_phy {
> + qcom,phy-rescode-offset-top = /bits/ 8 <31 31 31 31 (-32)>;
> + qcom,phy-rescode-offset-bot = /bits/ 8 <31 31 31 31 (-32)>;
> + qcom,phy-drive-ldo-level = <450>;
> +};
> +
> +&panel {
> + compatible = "boe,tv110c9m-ll3";
> +};
This is odd
Konrad
next prev parent reply other threads:[~2023-08-26 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 18:21 [PATCH 1/2] arm64: dts: qcom: sc7180: Move trogdor rt5682s bits to a fragment Douglas Anderson
2023-08-16 18:21 ` [PATCH 2/2] arm64: dts: qcom: sc7180: Reorganize trogdor rt5682 audio codec dts Douglas Anderson
2023-08-17 8:57 ` Sheng-Liang Pan
2023-08-26 9:36 ` Konrad Dybcio [this message]
2023-08-28 15:04 ` Doug Anderson
2023-08-28 15:07 ` Konrad Dybcio
2023-08-17 8:24 ` [PATCH 1/2] arm64: dts: qcom: sc7180: Move trogdor rt5682s bits to a fragment Sheng-Liang Pan
2023-08-26 9:34 ` Konrad Dybcio
2023-09-14 23:37 ` Doug Anderson
2023-09-20 2:13 ` (subset) " Bjorn Andersson
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=610a1b08-ced2-4e07-8b69-b2dd2749293e@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sheng-liang.pan@quanta.corp-partner.google.com \
/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).