mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Akhil P Oommen <akhilpo@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Clark <robin.clark@oss.qualcomm.com>,
	Abel Vesa <abelvesa@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] soc: qcom: ubwc: disable bank swizzling for Glymur platform
Date: Fri, 6 Mar 2026 21:37:16 +0530	[thread overview]
Message-ID: <866adc34-1a42-4abf-a95f-76259d86d779@oss.qualcomm.com> (raw)
In-Reply-To: <guisclar3eonn22vpjbdnzwbztwkrbbmvous7q757lihne4zbb@jtnnmune4uit>

On 3/6/2026 8:45 PM, Dmitry Baryshkov wrote:
> On Sat, Feb 28, 2026 at 08:34:27PM +0200, Dmitry Baryshkov wrote:
>> Due to the way the DDR controller is organized on Glymur, hardware
>> engineers strongly recommended disabling UBWC bank swizzling on Glymur.
>> Follow that recommendation.
>>
>> Fixes: 9b21c3bd2480 ("soc: qcom: ubwc: Add configuration Glymur platform")
>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>> ---
>> Changes in v2:
>> - Fix the syntax error...
>> - Link to v1: https://lore.kernel.org/r/20260228-fix-glymur-ubwc-v1-1-d80e3fe0dcc7@oss.qualcomm.com
>> ---
>>  drivers/soc/qcom/ubwc_config.c | 3 +--
>>  1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/drivers/soc/qcom/ubwc_config.c b/drivers/soc/qcom/ubwc_config.c
>> index 1c25aaf55e52..8304463f238a 100644
>> --- a/drivers/soc/qcom/ubwc_config.c
>> +++ b/drivers/soc/qcom/ubwc_config.c
>> @@ -231,8 +231,7 @@ static const struct qcom_ubwc_cfg_data x1e80100_data = {
>>  static const struct qcom_ubwc_cfg_data glymur_data = {
>>  	.ubwc_enc_version = UBWC_5_0,
>>  	.ubwc_dec_version = UBWC_5_0,
>> -	.ubwc_swizzle = UBWC_SWIZZLE_ENABLE_LVL2 |
>> -			UBWC_SWIZZLE_ENABLE_LVL3,
>> +	.ubwc_swizzle = 0,
>>  	.ubwc_bank_spread = true,
>>  	/* TODO: highest_bank_bit = 15 for LP_DDR4 */
>>  	.highest_bank_bit = 16,
> 
> Carrying over from v1 discussion.
> 
> Reviewed-by: Akhil P Oommen <quic_akhilpo@quicinc.com>

Sorry, please use my oss email instead:

Reviewed-by: Akhil P Oommen <akhilpo@oss.qualcomm.com>

-Akhil.

> 
> It depends on the fix which is currently a part of msm-fixes for the
> device to function correctly. Raised the question on IRC regarding the
> immutable tag or any other proper way to merge it.
> 
>>
>> ---
>> base-commit: 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f
>> change-id: 20260228-fix-glymur-ubwc-f673d5ca0581
>>
>> Best regards,
>> -- 
>> With best wishes
>> Dmitry
>>
> 


  reply	other threads:[~2026-03-06 16:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28 18:34 Dmitry Baryshkov
2026-02-28 18:48 ` Abel Vesa
2026-03-02 10:53 ` Konrad Dybcio
2026-03-06 15:15 ` Dmitry Baryshkov
2026-03-06 16:07   ` Akhil P Oommen [this message]
2026-03-16  1:41   ` Bjorn Andersson
2026-03-16  2:51     ` Dmitry Baryshkov
2026-03-19  3:23       ` Bjorn Andersson
2026-03-19  3:50         ` Dmitry Baryshkov
2026-03-06 22:19 ` Rob Clark
2026-03-23 14:38 ` 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=866adc34-1a42-4abf-a95f-76259d86d779@oss.qualcomm.com \
    --to=akhilpo@oss.qualcomm.com \
    --cc=abelvesa@kernel.org \
    --cc=andersson@kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.clark@oss.qualcomm.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

all inboxes | Powered by JetHome®