devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	cros-qcom-dts-watchers@chromium.org,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH 09/20] arm64: dts: qcom: sc8280xp: use correct size for VBIF regions
Date: Tue, 15 Apr 2025 12:43:17 +0200	[thread overview]
Message-ID: <ae06a328-f830-4583-a314-b50331c7f56c@oss.qualcomm.com> (raw)
In-Reply-To: <20250415-drm-msm-dts-fixes-v1-9-90cd91bdd138@oss.qualcomm.com>

On 4/15/25 12:26 PM, Dmitry Baryshkov wrote:
> Use allocated region size for VBIF regions as defined by the docs
> (0x3000) instead of just using the last register address.
> 
> Suggested-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Konrad

  reply	other threads:[~2025-04-15 10:43 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 10:25 [PATCH 00/20] arm64: dts: qcom: minor display-related fixups Dmitry Baryshkov
2025-04-15 10:25 ` [PATCH 01/20] arm64: dts: qcom: sc7280: Use the header with DSI phy clock IDs Dmitry Baryshkov
2025-04-15 10:36   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 02/20] arm64: dts: qcom: sa8775p: mark MDP interconnects as ALWAYS on Dmitry Baryshkov
2025-04-15 10:37   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 03/20] arm64: dts: qcom: msm8998: use correct size for VBIF regions Dmitry Baryshkov
2025-04-15 10:37   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 04/20] arm64: dts: qcom: qcm2290: " Dmitry Baryshkov
2025-04-15 10:38   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 05/20] arm64: dts: qcom: sa8775p: " Dmitry Baryshkov
2025-04-15 10:41   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 06/20] arm64: dts: qcom: sc7180: " Dmitry Baryshkov
2025-04-15 10:42   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 07/20] arm64: dts: qcom: sc7280: " Dmitry Baryshkov
2025-04-15 10:42   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 08/20] arm64: dts: qcom: sc8180x: " Dmitry Baryshkov
2025-04-15 10:42   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 09/20] arm64: dts: qcom: sc8280xp: " Dmitry Baryshkov
2025-04-15 10:43   ` Konrad Dybcio [this message]
2025-04-15 10:26 ` [PATCH 10/20] arm64: dts: qcom: sdm670: " Dmitry Baryshkov
2025-04-15 10:47   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 11/20] arm64: dts: qcom: sdm845: " Dmitry Baryshkov
2025-04-15 10:44   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 12/20] arm64: dts: qcom: sm6115: " Dmitry Baryshkov
2025-04-15 10:45   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 13/20] arm64: dts: qcom: sm6125: " Dmitry Baryshkov
2025-04-15 10:47   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 14/20] arm64: dts: qcom: sm6350: " Dmitry Baryshkov
2025-04-15 10:45   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 15/20] arm64: dts: qcom: sm8150: " Dmitry Baryshkov
2025-04-15 10:46   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 16/20] arm64: dts: qcom: sm8250: " Dmitry Baryshkov
2025-04-15 10:46   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 17/20] arm64: dts: qcom: sm8350: " Dmitry Baryshkov
2025-04-15 10:46   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 18/20] arm64: dts: qcom: sm8450: " Dmitry Baryshkov
2025-04-15 10:46   ` Konrad Dybcio
2025-04-15 10:26 ` [PATCH 19/20] arm64: dts: qcom: sm8550: " Dmitry Baryshkov
2025-04-15 10:47   ` Konrad Dybcio
2025-04-15 11:52   ` neil.armstrong
2025-04-15 10:26 ` [PATCH 20/20] arm64: dts: qcom: sm8650: " Dmitry Baryshkov
2025-04-15 10:47   ` Konrad Dybcio
2025-04-15 11:52   ` neil.armstrong
2025-04-16 18:10 ` [PATCH 00/20] arm64: dts: qcom: minor display-related fixups 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=ae06a328-f830-4583-a314-b50331c7f56c@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=cros-qcom-dts-watchers@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).