From: Bjorn Andersson <andersson@kernel.org>
To: cros-qcom-dts-watchers@chromium.org,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
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 00/20] arm64: dts: qcom: minor display-related fixups
Date: Wed, 16 Apr 2025 13:10:41 -0500 [thread overview]
Message-ID: <174482704418.446874.3479876614080391885.b4-ty@kernel.org> (raw)
In-Reply-To: <20250415-drm-msm-dts-fixes-v1-0-90cd91bdd138@oss.qualcomm.com>
On Tue, 15 Apr 2025 13:25:58 +0300, Dmitry Baryshkov wrote:
> Based on the patch review by Konrad:
> - Change VBIF size to 0x3000 as defined by memory map
> - Use new DSI clock defines on SC7280
> - Use TAG_ALWAYS for MDP->EBI memory interface on SA8775P
>
>
Applied, thanks!
[01/20] arm64: dts: qcom: sc7280: Use the header with DSI phy clock IDs
commit: 33e020b942cb4bcf2f3870b573470973e6464bd5
[02/20] arm64: dts: qcom: sa8775p: mark MDP interconnects as ALWAYS on
commit: 8725fb400542a6c88c1cc918d96064eedc8c94c4
[03/20] arm64: dts: qcom: msm8998: use correct size for VBIF regions
commit: 31e18ebef09a596ea87277c24411e1a86eb56470
[04/20] arm64: dts: qcom: qcm2290: use correct size for VBIF regions
commit: bacf203baa1ef896ac2bb4f9bf43b19f15a6ae26
[05/20] arm64: dts: qcom: sa8775p: use correct size for VBIF regions
commit: 180f990ed061cefdac620d02f34b03387210a2b7
[06/20] arm64: dts: qcom: sc7180: use correct size for VBIF regions
commit: 74e18dc4aef0e8e2989815856e48c737820ebca8
[07/20] arm64: dts: qcom: sc7280: use correct size for VBIF regions
commit: 545b26b926ae20640a7d464e1b830ce4ce021fd5
[08/20] arm64: dts: qcom: sc8180x: use correct size for VBIF regions
commit: a24e1cb954a6915983280e757c36d04fd5e6ce34
[09/20] arm64: dts: qcom: sc8280xp: use correct size for VBIF regions
commit: 7b5160ce90a3c6c8e6202f727c3e6cd2c0911cbd
[10/20] arm64: dts: qcom: sdm670: use correct size for VBIF regions
commit: acc206fed3698554a16cf70e5a2fc0e4f1e1a5fc
[11/20] arm64: dts: qcom: sdm845: use correct size for VBIF regions
commit: e50450aae01ea23e17e10f59cdbdc7aa59108250
[12/20] arm64: dts: qcom: sm6115: use correct size for VBIF regions
commit: c7f4216765891939e6d2dfa8809883bae978582f
[13/20] arm64: dts: qcom: sm6125: use correct size for VBIF regions
commit: e24c7cb72b9b1286deee43fecf87d0248fa430cc
[14/20] arm64: dts: qcom: sm6350: use correct size for VBIF regions
commit: 7cfcd1a3c519d0aff10af2db06aa6d2291393bd8
[15/20] arm64: dts: qcom: sm8150: use correct size for VBIF regions
commit: 130e9aacc40176b5fa2954e7861d9b5f28f373ae
[16/20] arm64: dts: qcom: sm8250: use correct size for VBIF regions
commit: 4e851ff6a3a12ce616e3cc902af0ae2efb2e8137
[17/20] arm64: dts: qcom: sm8350: use correct size for VBIF regions
commit: d55fe5da78836835f9a88c29dd2fb3086b4a3720
[18/20] arm64: dts: qcom: sm8450: use correct size for VBIF regions
commit: 62acfd77a5783948ba3593fb169720ab7495c380
[19/20] arm64: dts: qcom: sm8550: use correct size for VBIF regions
commit: 9e9d8349e76252d5b7e060cc0ca4823a3f062052
[20/20] arm64: dts: qcom: sm8650: use correct size for VBIF regions
commit: d8203fff4e6849cc5799fcf51105f7622e13c46d
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2025-04-16 18:10 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
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 ` Bjorn Andersson [this message]
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=174482704418.446874.3479876614080391885.b4-ty@kernel.org \
--to=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=konrad.dybcio@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