From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Bingbu Cao <bingbu.cao@linux.intel.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, Bingbu Cao <bingbu.cao@intel.com>
Subject: Re: [PATCH v2] media: intel/ipu6: remove buttress ish structure
Date: Mon, 4 Nov 2024 10:19:02 +0100 [thread overview]
Message-ID: <ZyiRhk/LejVGSUKL@linux.intel.com> (raw)
In-Reply-To: <7ad30743-58c5-7004-9eed-4f1d8589c7f7@linux.intel.com>
On Fri, Nov 01, 2024 at 05:07:25PM +0800, Bingbu Cao wrote:
>
> On 11/1/24 4:19 PM, Sakari Ailus wrote:
> > Hi Bingbu,
> >
> > On Fri, Nov 01, 2024 at 03:47:54PM +0800, Bingbu Cao wrote:
> >> Sakari and Stanislaw,
> >>
> >> On 11/1/24 3:46 PM, Sakari Ailus wrote:
> >>>>>> @@ -386,10 +382,8 @@ irqreturn_t ipu6_buttress_isr(int irq, void *isp_ptr)
> >>>>>> }
> >>>>>>
> >>>>>> if (irq_status & BUTTRESS_ISR_IPC_FROM_ISH_IS_WAITING) {
> >>>>>> - dev_dbg(&isp->pdev->dev,
> >>>>>> - "BUTTRESS_ISR_IPC_FROM_ISH_IS_WAITING\n");
> >>>>>> - ipu6_buttress_ipc_recv(isp, &b->ish, &b->ish.recv_data);
> >>>>>> - complete(&b->ish.recv_complete);
> >>>>>> + dev_warn(&isp->pdev->dev,
> >>>>>> + "BUTTRESS_ISR_IPC_FROM_ISH_IS_WAITING\n");
> >>>>>
> >>>>> I think this is a unrelated change, right?
> >>>>
> >>>> I mean the change from dev_dbg() to dev_warn().
> >>>
> >>> We're not handling these interrupts anymore in any way.
> >>>
> >>> I wonder if the ipu6_buttress_ipc_recv() call should still remain in place,
> >>> even if we really do nothing with these. It looks like some kind of an
> >>> acknowledgement mechanism.
> >>
> >> I just confirm that IPC_FROM_ISH_IS_WAITING and IPC_EXEC_DONE_BY_ISH are
> >> not valid anymore from IPU6, I think the handling here and below could be
> >> removed.
> >
> > Do you know which IPU version still needed it?
> >
> > There are folks who'd like to add IPU4 support to the driver but they can
> > add it back if it's needed.
> >
>
> I know that ISH IPC was added from IPU4, but I am not sure IPU4 really
> need that now.
Ok, I think on v3, I'll remove handling of BUTTRESS_ISR_IPC_FROM_ISH_IS_WAITING
and BUTTRESS_ISR_IPC_EXEC_DONE_BY_ISH from isr, but will keep the BIT's
definitions just in case.
Regards
Stanislaw
next prev parent reply other threads:[~2024-11-04 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 13:06 [PATCH v2] media: intel/ipu6: remove buttress ish structure Stanislaw Gruszka
2024-11-01 4:22 ` Bingbu Cao
2024-11-01 4:26 ` Bingbu Cao
2024-11-01 7:46 ` Sakari Ailus
2024-11-01 7:47 ` Bingbu Cao
2024-11-01 8:19 ` Sakari Ailus
2024-11-01 9:07 ` Bingbu Cao
2024-11-04 9:19 ` Stanislaw Gruszka [this message]
2024-11-05 2:47 ` Bingbu Cao
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=ZyiRhk/LejVGSUKL@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=bingbu.cao@linux.intel.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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 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.