From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pushpendra Singh <quic_pussin@quicinc.com>,
cros-qcom-dts-watchers@chromium.org, andersson@kernel.org,
konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kernel@quicinc.com
Subject: Re: [PATCH] arm64: dts: qcom: sc7280: Add support for two additional DDR frequencies
Date: Tue, 1 Jul 2025 09:56:54 +0200 [thread overview]
Message-ID: <ea5058cd-29da-4939-990d-697396197ed9@kernel.org> (raw)
In-Reply-To: <20250701074334.1782967-1-quic_pussin@quicinc.com>
On 01/07/2025 09:43, Pushpendra Singh wrote:
> Cc: kernel@quicinc.com, kernel@oss.qualcomm.com
>
> The SC7280 SoC now supports two additional frequencies. This patch
> add those frequencies to the BWMON OPP table and updates the frequency
> mapping table accordingly.
>
> These changes do not impact existing platforms, as the updated mapping
> only affects the highest OPP. On any given platform, this will continue
> to vote for the maximum available OPP.
>
> Change-Id: Id3a91e065c49848d9af18e5c3edee0836cb693e5
> Signed-off-by: Pushpendra Singh <quic_pussin@quicinc.com>
Doesn't your internal guideline tell you to run checkpatch before sending?
Also it mentions many other things, so read entire guideline prior to
posting.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-01 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 7:43 [PATCH] arm64: dts: qcom: sc7280: Add support for two additional DDR frequencies Pushpendra Singh
2025-07-01 7:56 ` Krzysztof Kozlowski [this message]
2025-07-03 9:45 ` Pushpendra Singh
2025-07-01 18:13 ` Trilok Soni
2025-07-02 9:57 ` Pushpendra Singh
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=ea5058cd-29da-4939-990d-697396197ed9@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_pussin@quicinc.com \
--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