From: Md Sadre Alam <md.alam@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Varadarajan Narayanan <varadarajan.narayanan@oss.qualcomm.com>,
Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
Abhishek Sahu <absahu@codeaurora.org>,
mani@kernel.org, linux-arm-msm@vger.kernel.org,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
lakshmi.d@oss.qualcomm.com
Subject: Re: [PATCH v5] dma: qcom: bam_dma: Fix command element mask field for BAM v1.6.0+
Date: Tue, 9 Jun 2026 16:04:52 +0530 [thread overview]
Message-ID: <89a95a6f-1dce-4141-9b7c-12d7ab6bc0af@oss.qualcomm.com> (raw)
In-Reply-To: <6qkgzmrr3oxzj47so4jqw6gk6stzjkxbnaflajk5zw5fgf65cn@yj3d55p5b7do>
Hi,
On 6/8/2026 11:33 AM, Dmitry Baryshkov wrote:
> On Mon, Jun 08, 2026 at 11:20:01AM +0530, Md Sadre Alam wrote:
>> Hi,
>>
>> On 6/4/2026 4:15 PM, Varadarajan Narayanan wrote:
>>> On Tue, May 19, 2026 at 11:01:51PM +0530, Vinod Koul wrote:
>>>> On 14-05-26, 12:09, Varadarajan Narayanan wrote:
>>>>> From: Md Sadre Alam <md.alam@oss.qualcomm.com>
>>>>>
>>>>> BAM version 1.6.0 and later changed the behavior of the mask field in
>>>>> command elements for read operations. In newer BAM versions, the mask
>>>>> field for read commands contains the upper 4 bits of the destination
>>>>> address to support 36-bit addressing, while for write commands it
>>>>> continues to function as a traditional write mask.
>>>>
>>>> But this changes behaviour for all versions. What happens to folks on older
>>>> versions, wont this break for them, if not what am I missing
>>
>> It will not have any impact on older version of BAM controller. Konrad also
>> had a similar concern. Please refer to [1]
>>
>> [1] https://lore.kernel.org/linux-arm-msm/2394e63f-1df7-764e-5489-3567065707a1@quicinc.com/
>
> So, you got this question once, have resent the patches, but didn't
> guess that there will be the similar question from other reviewers?
>
> Usually a question means that the commit needs to be improved. Adding a
> simple "Previously this field was ignored for read commands" would have
> saved you from futher questions.
Will update the commit message and post the new version.
Thanks,
Alam.
prev parent reply other threads:[~2026-06-09 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 6:39 [PATCH v5] dma: qcom: bam_dma: Fix command element mask field for BAM v1.6.0+ Varadarajan Narayanan
2026-05-19 17:31 ` Vinod Koul
2026-06-04 10:45 ` Varadarajan Narayanan
2026-06-08 5:50 ` Md Sadre Alam
2026-06-08 6:03 ` Dmitry Baryshkov
2026-06-09 10:34 ` Md Sadre Alam [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=89a95a6f-1dce-4141-9b7c-12d7ab6bc0af@oss.qualcomm.com \
--to=md.alam@oss.qualcomm.com \
--cc=Frank.Li@kernel.org \
--cc=absahu@codeaurora.org \
--cc=dmaengine@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=lakshmi.d@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=varadarajan.narayanan@oss.qualcomm.com \
--cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.