mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eugen Hristev <ehristev@kernel.org>
To: Runyu Xiao <runyu.xiao@seu.edu.cn>,
	Hans Verkuil <hverkuil+cisco@kernel.org>
Cc: mchehab@kernel.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Jianhao Xu <jianhao.xu@seu.edu.cn>,
	Balakrishnan Sambath <balakrishnan.s@microchip.com>
Subject: Re: [PATCH] media: microchip: isc: Initialize DMA lock before requesting IRQ
Date: Wed, 23 Sep 2026 21:44:57 +0300	[thread overview]
Message-ID: <dec62b4d-15ce-4760-bf09-69dd541104ce@kernel.org> (raw)
In-Reply-To: <20260919011013.3383669-1-runyu.xiao@seu.edu.cn>

On 9/19/26 04:10, Runyu Xiao wrote:
> Hi Hans and Eugen,
> 
> Thanks for taking a look at this.
> 
> On Sun, 30 Aug 2026, I wrote:
>> The ISC interrupt can run before asynchronous subdevice completion,
>> but the DMA queue lock was initialized from isc_async_complete().
>> Initialize it in each SoC probe before requesting the auto-enabled IRQ.
> 
> On Thu, 10 Sep 2026, Hans Verkuil wrote:
>> It's dubious to just init dma_queue_lock here but not
>> INIT_LIST_HEAD(&isc->dma_queue);
>>
>> I think Eugen needs to look at this as well to see if this is actually
>> a valid issue at all.
>>
>> In any case, this patch doesn't look right to me.
> 
> You're right that moving dma_queue_lock alone is not enough. The interrupt
> handler also accesses dma_queue, comp, and awb_work, which are initialized
> later from isc_async_complete(). I also need to confirm whether an interrupt
> can actually be pending at this point, and whether the required clocks and
> hardware state are ready during probe.
> 
> I have not established that yet, so I'll drop this version for now rather
> than send a v2 that only moves another initialization. Eugen, could you
> please confirm the expected reset and interrupt state during probe? If there
> is a real probe-time path, I'll revisit this with the complete ordering.

Added Balakrishnan , he can test and review your patch.

Eugen>
> Thanks,
> Runyu


      reply	other threads:[~2026-09-23 18:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-30  2:32 Runyu Xiao
2026-09-10 11:54 ` Hans Verkuil
2026-09-19  1:10   ` Runyu Xiao
2026-09-23 18:44     ` Eugen Hristev [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=dec62b4d-15ce-4760-bf09-69dd541104ce@kernel.org \
    --to=ehristev@kernel.org \
    --cc=balakrishnan.s@microchip.com \
    --cc=hverkuil+cisco@kernel.org \
    --cc=jianhao.xu@seu.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=runyu.xiao@seu.edu.cn \
    --cc=stable@vger.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

all inboxes | Powered by JetHome®