From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] media: fdp1: Reduce FCP not found message level to debug
Date: Tue, 9 Jul 2019 11:07:30 +0100 [thread overview]
Message-ID: <17f28f31-73e1-5170-a0d5-31ad9826defa@ideasonboard.com> (raw)
In-Reply-To: <20190709095952.5666-1-geert+renesas@glider.be>
Hi Geert,
On 09/07/2019 10:59, Geert Uytterhoeven wrote:
> When support for the IPMMU is not enabled, the FDP driver may be
> probe-deferred multiple times, causing several messages to be printed
> like:
>
> rcar_fdp1 fe940000.fdp1: FCP not found (-517)
> rcar_fdp1 fe944000.fdp1: FCP not found (-517)
>
> Fix this by reducing the message level to debug level, as is done in the
> VSP1 driver.
Does the lack of IPMMU prevent the FDP1 being loaded entirely?
If so is that a problem for us? (I thought we were able to run without
the IPMMU)
> Fixes: 4710b752e029f3f8 ("[media] v4l: Add Renesas R-Car FDP1 Driver")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> The alternative would be to add an explicit check for -EPROBE_DEFER.
> ---
> drivers/media/platform/rcar_fdp1.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/rcar_fdp1.c b/drivers/media/platform/rcar_fdp1.c
> index 43aae9b6bb20e3e8..c23ec127c2776f51 100644
> --- a/drivers/media/platform/rcar_fdp1.c
> +++ b/drivers/media/platform/rcar_fdp1.c
> @@ -2306,7 +2306,7 @@ static int fdp1_probe(struct platform_device *pdev)
> fdp1->fcp = rcar_fcp_get(fcp_node);
> of_node_put(fcp_node);
> if (IS_ERR(fdp1->fcp)) {
> - dev_err(&pdev->dev, "FCP not found (%ld)\n",
> + dev_dbg(&pdev->dev, "FCP not found (%ld)\n",
> PTR_ERR(fdp1->fcp));
Should we be doing something differently here in the event of no IPMMU then?
Otherwise, if the IPMMU has become a hard dependency, should we add it
to the Kconfig dependencies?
> return PTR_ERR(fdp1->fcp);
> }
>
--
Regards
Kieran
next prev parent reply other threads:[~2019-07-09 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 9:59 [PATCH] media: fdp1: Reduce FCP not found message level to debug Geert Uytterhoeven
2019-07-09 10:07 ` Kieran Bingham [this message]
2019-07-09 10:13 ` Geert Uytterhoeven
2019-07-09 10:18 ` Kieran Bingham
2019-07-09 10:28 ` Geert Uytterhoeven
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=17f28f31-73e1-5170-a0d5-31ad9826defa@ideasonboard.com \
--to=kieran.bingham+renesas@ideasonboard.com \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).