From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
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>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: qcom: sdm630: move DSI opp-table out of soc node
Date: Sun, 26 Mar 2023 11:22:20 +0200 [thread overview]
Message-ID: <c6429b89-bdf1-a601-7cc2-a6cbb566fecd@linaro.org> (raw)
In-Reply-To: <CAA8EJpqR-QisyWEHE83oFbXt8wUcn2Ofd4W6UwFmkYzGD18N9Q@mail.gmail.com>
On 26/03/2023 11:21, Dmitry Baryshkov wrote:
> On Sun, 26 Mar 2023 at 12:16, Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> wrote:
>>
>> The soc node is supposed to have only device nodes with MMIO addresses,
>> so move the DSI OPP out of it (it is used also by second DSI1 on
>> SDM660):
>
> This raises a question: would it make sense to add /opps to handle all
> opp tables?
We didn't add it to any other cases like this (and we already fixed all
other boards), so why now? We can but it is a bit late for it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-26 9:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 9:16 [PATCH v2] arm64: dts: qcom: sdm630: move DSI opp-table out of soc node Krzysztof Kozlowski
2023-03-26 9:21 ` Dmitry Baryshkov
2023-03-26 9:22 ` Krzysztof Kozlowski [this message]
2023-03-26 10:03 ` Dmitry Baryshkov
2023-03-26 10:13 ` Krzysztof Kozlowski
2023-03-26 22:02 ` Dmitry Baryshkov
2023-03-27 17:48 ` Konrad Dybcio
2023-03-27 19:39 ` Bjorn Andersson
2023-03-27 19:39 ` Krzysztof Kozlowski
2023-04-07 16:34 ` Bjorn Andersson
2023-04-07 19:18 ` Krzysztof Kozlowski
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=c6429b89-bdf1-a601-7cc2-a6cbb566fecd@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.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=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