mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Wang Ming <machel@vivo.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Michal Simek <michal.simek@amd.com>,
	linux-media@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, opensource.kernel@vivo.com
Subject: Re: [PATCH v2] media: platform: Use dev_err_probe instead of dev_err
Date: Wed, 26 Jul 2023 17:49:23 +0300	[thread overview]
Message-ID: <20230726144923.GA28136@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20230726142835.GA5148@pendragon.ideasonboard.com>

On Wed, Jul 26, 2023 at 05:28:37PM +0300, Laurent Pinchart wrote:
> Hi Wang,
> 
> Thank you for the patch.
> 
> On Wed, Jul 26, 2023 at 07:51:58PM +0800, Wang Ming wrote:
> > It is possible that dma_request_chan will return EPROBE_DEFER,
> > which means that dma->xdev->dev is not ready yet. In this case,
> > dev_err(dma->xdev->dev), there will be no output. This patch
> > fixes the bug.
> 
> It's not a bug. The existing code works as expected. dev_err_probe() is
> nicer though, as it records the reason for the probe deferral. Here's a
> proposal for a better commit message:
> 
>   It is possible that dma_request_chan() returns EPROBE_DEFER, in which
>   case the driver defers probing without printing any message. Use
>   dev_err_probe() to record the probe deferral cause and ease debugging.
> 
> If you're fine with this, there's no need to resubmit, I'll update the
> commit message locally and merge the patch.
> 
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> 
> > Signed-off-by: Wang Ming <machel@vivo.com>
> > ---
> >  drivers/media/platform/xilinx/xilinx-dma.c | 5 ++---
> >  1 file changed, 2 insertions(+), 3 deletions(-)
> > 
> > diff --git a/drivers/media/platform/xilinx/xilinx-dma.c b/drivers/media/platform/xilinx/xilinx-dma.c
> > index 80d6f5b072ea..16ad39bef6c6 100644
> > --- a/drivers/media/platform/xilinx/xilinx-dma.c
> > +++ b/drivers/media/platform/xilinx/xilinx-dma.c
> > @@ -708,9 +708,8 @@ int xvip_dma_init(struct xvip_composite_device *xdev, struct xvip_dma *dma,
> >  	snprintf(name, sizeof(name), "port%u", port);
> >  	dma->dma = dma_request_chan(dma->xdev->dev, name);
> >  	if (IS_ERR(dma->dma)) {
> > -		ret = PTR_ERR(dma->dma);
> > -		if (ret != -EPROBE_DEFER)
> > -			dev_err(dma->xdev->dev, "no VDMA channel found\n");
> > +		ret = dev_err_probe(dma->xdev->dev, PTR_ERR(dma->dma),
> > +			"no VDMA channel found\n");

I forgot to mention that the message should be aligned:

		ret = dev_err_probe(dma->xdev->dev, PTR_ERR(dma->dma),
				    "no VDMA channel found\n");

I can fix this locally too.

> >  		goto error;
> >  	}
> >  

-- 
Regards,

Laurent Pinchart

      reply	other threads:[~2023-07-26 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 11:51 Wang Ming
2023-07-26 14:28 ` Laurent Pinchart
2023-07-26 14:49   ` Laurent Pinchart [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=20230726144923.GA28136@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=machel@vivo.com \
    --cc=mchehab@kernel.org \
    --cc=michal.simek@amd.com \
    --cc=opensource.kernel@vivo.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

all inboxes | Powered by JetHome®