On 01/11/24 18:45, Mark Brown wrote:
On Fri, Nov 01, 2024 at 02:32:43PM +0530, Suraj Sonawane wrote:
I reviewed the context around val_1 and val_2 in dma_addr_next. These values
are expected to come from the registers when offlevel is non-zero,
representing the next DMA address and length information. If offlevel is
zero, it means there’s no offset data to process, and dma_addr_next might
not need updating in that case.
A more precise solution would be to conditionally update prtd->dma_addr_next
only when offlevel is non-zero, as this would reflect the intended logic
without relying on an arbitrary initialization.
Would it be better to revise the patch to conditionally update
prtd->dma_addr_next only when offlevel is non-zero?
Let me know if this approach aligns better with the expected behavior.
That seems like a reasonable approach, just skip the update when we
didn't read the values.
Thanks for the feedback.
I've updated the patch based on your suggestion to conditionally update
prtd->dma_addr_next only when offlevel is non-zero, effectively skipping
the update if values were not read. This approach aligns with the
expected logic, as it ensures dma_addr_next is only updated when valid
data is available, preventing any unintended updates.
I’ve just sent the revised patch. Please let me know if any additional
adjustments are needed.
Best regards,
Suraj Sonawane
[Index of Archives]
[Pulseaudio]
[Linux Audio Users]
[ALSA Devel]
[Fedora Desktop]
[Fedora SELinux]
[Big List of Linux Books]
[Yosemite News]
[KDE Users]