From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: <broonie@kernel.org>, <tiwai@suse.com>, <perex@perex.cz>,
<amade@asmblr.net>, <linux-sound@vger.kernel.org>
Subject: Re: [PATCH 1/6] ASoC: Intel: catpt: Fix offset checks
Date: Mon, 24 Nov 2025 19:20:48 +0100 [thread overview]
Message-ID: <e99d1131-0c7b-4cf8-8830-34f766bdfe6f@intel.com> (raw)
In-Reply-To: <aSRsX9qlUVC7HHvA@smile.fi.intel.com>
On 2025-11-24 3:31 PM, Andy Shevchenko wrote:
> On Fri, Nov 21, 2025 at 12:43:26PM +0100, Cezary Rojewski wrote:
>> Verify if the entire block is found within DRAM, not just the start of
>> it.
>
> I would rewrap this to have less distant lengths.
>
> E.g.,
>
> Verify if the entire block is found within DRAM, not just
> the start of it.
>
Sure, will do. Typically I just do 72-chars per line and whatever
happens, happens.
>> Signed-off-by: Cezary Rojewski <cezary.rojewski@intel.com>
>
> ...
>
>> static int catpt_restore_memdumps(struct catpt_dev *cdev, struct dma_chan *chan)
>
>> off = catpt_to_host_offset(info->offset);
>> - if (off < cdev->dram.start || off > cdev->dram.end)
>> + if (off < cdev->dram.start || off + info->size >= cdev->dram.end)
>> continue;
>
> Hmm... I would rather do something like
>
> struct resource r;
> ...
> resource_set_range(catpt_to_host_offset(info->offset), info->size);
> if (!resource_contains())
> continue;
>
>> dev_dbg(cdev->dev, "restoring memdump: off 0x%08x size %d\n",
>
> OTOH it seems more invasive change for kinda a fix.
Looks elegant though. My idea was to avoid additional operations (which
resource_contains() does), perhaps unnecessarily as readability suffered
because of that. Ack.
>
> ...
>
>> static int catpt_restore_fwimage(struct catpt_dev *cdev,
>
>> off = catpt_to_host_offset(info->offset);
>> - if (off < cdev->dram.start || off > cdev->dram.end)
>> - continue;
>> -
>> r2.start = off;
>> r2.end = r2.start + info->size - 1;
>>
>> + if (r2.start < cdev->dram.start || r2.end > cdev->dram.end)
>> + continue;
>
> See above, but here we already good for use the respective resource_*() API.
>
>> if (!resource_intersection(&r2, &r1, &common))
>> continue;
>
next prev parent reply other threads:[~2025-11-24 18:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 11:43 [PATCH 0/6] ASoC: Intel: catpt: Round of fixes and PM changes Cezary Rojewski
2025-11-21 11:43 ` [PATCH 1/6] ASoC: Intel: catpt: Fix offset checks Cezary Rojewski
2025-11-24 14:31 ` Andy Shevchenko
2025-11-24 18:20 ` Cezary Rojewski [this message]
2025-11-24 19:05 ` Andy Shevchenko
2025-11-24 19:06 ` Andy Shevchenko
2025-11-25 11:31 ` Cezary Rojewski
2025-11-25 18:24 ` Andy Shevchenko
2025-11-25 18:26 ` Andy Shevchenko
2025-11-21 11:43 ` [PATCH 2/6] ASoC: Intel: catpt: Fix error path in hw_params() Cezary Rojewski
2025-11-21 11:43 ` [PATCH 3/6] ASoC: Intel: catpt: Fix probing order of driver components Cezary Rojewski
2025-11-21 11:43 ` [PATCH 4/6] ASoC: Intel: catpt: Do not ignore errors on runtime resume Cezary Rojewski
2025-11-21 11:43 ` [PATCH 5/6] ASoC: Intel: catpt: Do not block the system from suspending Cezary Rojewski
2025-11-24 14:42 ` Andy Shevchenko
2025-11-24 18:05 ` Cezary Rojewski
2025-11-24 19:07 ` Andy Shevchenko
2025-11-21 11:43 ` [PATCH 6/6] ASoC: Intel: catpt: Drop catpt_runtime_resume() Cezary Rojewski
2025-11-24 14:37 ` Andy Shevchenko
2025-11-24 18:06 ` Cezary Rojewski
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=e99d1131-0c7b-4cf8-8830-34f766bdfe6f@intel.com \
--to=cezary.rojewski@intel.com \
--cc=amade@asmblr.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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