Linux Media Controller development
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Bingbu Cao <bingbu.cao@linux.intel.com>
Cc: linux-media@vger.kernel.org, Bingbu Cao <bingbu.cao@intel.com>,
	Tianshu Qiu <tian.shu.qiu@intel.com>
Subject: Re: [PATCH 1/1] media: staging: ipu3-imgu: Update firmware path
Date: Thu, 11 Apr 2024 07:45:28 +0000	[thread overview]
Message-ID: <ZheVGP4b4Sdsh-K3@kekkonen.localdomain> (raw)
In-Reply-To: <79079812-fdd2-c712-6442-73bd5a40ba4c@linux.intel.com>

Hi Bingbu,

On Thu, Apr 11, 2024 at 03:35:25PM +0800, Bingbu Cao wrote:
> Sakari,
> 
> On 4/11/24 2:56 PM, Sakari Ailus wrote:
> > Use the current firmware path in linux-firmware repository. Check the
> > older paths still in order to avoid causing issues to the users.
> 
> We also meet similiar issues for IPU6(github driver), I am wondering
> as the WHENCE file create link and do we still need such patch for IPU6?

Good question. This was still never found in the upstream Linux kernel.

I don't have a strong opinion about it though. Something like that was done
to the ipu3-cio2 driver, too. So perhaps we could just take Hao Yao's patch
and get it to linux-firmware (with a bit more elaborate commit message)?

> 
> > 
> > Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> > ---
> >  drivers/staging/media/ipu3/ipu3-css-fw.c | 4 +++-
> >  drivers/staging/media/ipu3/ipu3-css-fw.h | 2 ++
> >  2 files changed, 5 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/staging/media/ipu3/ipu3-css-fw.c b/drivers/staging/media/ipu3/ipu3-css-fw.c
> > index 2b659b0ccca1..37482b626c3c 100644
> > --- a/drivers/staging/media/ipu3/ipu3-css-fw.c
> > +++ b/drivers/staging/media/ipu3/ipu3-css-fw.c
> > @@ -117,7 +117,9 @@ int imgu_css_fw_init(struct imgu_css *css)
> >  	unsigned int i, j, binary_nr;
> >  	int r;
> >  
> > -	r = request_firmware(&css->fw, IMGU_FW_NAME_20161208, css->dev);
> > +	r = request_firmware(&css->fw, IMGU_FW_NAME_IPU_20161208, css->dev);
> > +	if (r == -ENOENT)
> > +		r = request_firmware(&css->fw, IMGU_FW_NAME_20161208, css->dev);
> >  	if (r == -ENOENT)
> >  		r = request_firmware(&css->fw, IMGU_FW_NAME, css->dev);
> >  	if (r)
> > diff --git a/drivers/staging/media/ipu3/ipu3-css-fw.h b/drivers/staging/media/ipu3/ipu3-css-fw.h
> > index f9403da75785..c956aa21df25 100644
> > --- a/drivers/staging/media/ipu3/ipu3-css-fw.h
> > +++ b/drivers/staging/media/ipu3/ipu3-css-fw.h
> > @@ -9,6 +9,8 @@
> >  #define IMGU_FW_NAME		"intel/ipu3-fw.bin"
> >  #define IMGU_FW_NAME_20161208	\
> >  	"intel/irci_irci_ecr-master_20161208_0213_20170112_1500.bin"
> > +#define IMGU_FW_NAME_IPU_20161208	\
> > +	"intel/ipu/irci_irci_ecr-master_20161208_0213_20170112_1500.bin"
> >  
> >  typedef u32 imgu_fw_ptr;
> >  
> > 
> 

-- 
Regards,

Sakari Ailus

      reply	other threads:[~2024-04-11  7:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  6:56 [PATCH 1/1] media: staging: ipu3-imgu: Update firmware path Sakari Ailus
2024-04-11  7:35 ` Bingbu Cao
2024-04-11  7:45   ` Sakari Ailus [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=ZheVGP4b4Sdsh-K3@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=bingbu.cao@intel.com \
    --cc=bingbu.cao@linux.intel.com \
    --cc=linux-media@vger.kernel.org \
    --cc=tian.shu.qiu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox