From: Jani Nikula <jani.nikula@linux.intel.com>
To: James Hilliard <james.hilliard1@gmail.com>,
dri-devel@lists.freedesktop.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
James Hilliard <james.hilliard1@gmail.com>,
linux-kernel@vger.kernel.org,
"Rafael J . Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH] component: Silence bind error on -EPROBE_DEFER
Date: Tue, 14 Apr 2020 14:07:01 +0300 [thread overview]
Message-ID: <87lfmymilm.fsf@intel.com> (raw)
In-Reply-To: <20200411054106.25366-1-james.hilliard1@gmail.com>
On Fri, 10 Apr 2020, James Hilliard <james.hilliard1@gmail.com> wrote:
> If a component fails to bind due to -EPROBE_DEFER we should not log an
> error as this is not a real failure.
>
> Fixes:
> vc4-drm soc:gpu: failed to bind 3f902000.hdmi (ops vc4_hdmi_ops): -517
> vc4-drm soc:gpu: master bind failed: -517
I'd think the probe defer is useful information anyway. Maybe just tone
down the severity and/or the message?
BR,
Jani.
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> drivers/base/component.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/base/component.c b/drivers/base/component.c
> index e97704104784..157c6c790578 100644
> --- a/drivers/base/component.c
> +++ b/drivers/base/component.c
> @@ -256,7 +256,8 @@ static int try_to_bring_up_master(struct master *master,
> ret = master->ops->bind(master->dev);
> if (ret < 0) {
> devres_release_group(master->dev, NULL);
> - dev_info(master->dev, "master bind failed: %d\n", ret);
> + if (ret != -EPROBE_DEFER)
> + dev_info(master->dev, "master bind failed: %d\n", ret);
> return ret;
> }
>
> @@ -611,8 +612,10 @@ static int component_bind(struct component *component, struct master *master,
> devres_release_group(component->dev, NULL);
> devres_release_group(master->dev, NULL);
>
> - dev_err(master->dev, "failed to bind %s (ops %ps): %d\n",
> - dev_name(component->dev), component->ops, ret);
> + if (ret != -EPROBE_DEFER) {
> + dev_err(master->dev, "failed to bind %s (ops %ps): %d\n",
> + dev_name(component->dev), component->ops, ret);
> + }
> }
>
> return ret;
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: James Hilliard <james.hilliard1@gmail.com>,
dri-devel@lists.freedesktop.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
James Hilliard <james.hilliard1@gmail.com>,
linux-kernel@vger.kernel.org,
"Rafael J . Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH] component: Silence bind error on -EPROBE_DEFER
Date: Tue, 14 Apr 2020 14:07:01 +0300 [thread overview]
Message-ID: <87lfmymilm.fsf@intel.com> (raw)
In-Reply-To: <20200411054106.25366-1-james.hilliard1@gmail.com>
On Fri, 10 Apr 2020, James Hilliard <james.hilliard1@gmail.com> wrote:
> If a component fails to bind due to -EPROBE_DEFER we should not log an
> error as this is not a real failure.
>
> Fixes:
> vc4-drm soc:gpu: failed to bind 3f902000.hdmi (ops vc4_hdmi_ops): -517
> vc4-drm soc:gpu: master bind failed: -517
I'd think the probe defer is useful information anyway. Maybe just tone
down the severity and/or the message?
BR,
Jani.
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> drivers/base/component.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/base/component.c b/drivers/base/component.c
> index e97704104784..157c6c790578 100644
> --- a/drivers/base/component.c
> +++ b/drivers/base/component.c
> @@ -256,7 +256,8 @@ static int try_to_bring_up_master(struct master *master,
> ret = master->ops->bind(master->dev);
> if (ret < 0) {
> devres_release_group(master->dev, NULL);
> - dev_info(master->dev, "master bind failed: %d\n", ret);
> + if (ret != -EPROBE_DEFER)
> + dev_info(master->dev, "master bind failed: %d\n", ret);
> return ret;
> }
>
> @@ -611,8 +612,10 @@ static int component_bind(struct component *component, struct master *master,
> devres_release_group(component->dev, NULL);
> devres_release_group(master->dev, NULL);
>
> - dev_err(master->dev, "failed to bind %s (ops %ps): %d\n",
> - dev_name(component->dev), component->ops, ret);
> + if (ret != -EPROBE_DEFER) {
> + dev_err(master->dev, "failed to bind %s (ops %ps): %d\n",
> + dev_name(component->dev), component->ops, ret);
> + }
> }
>
> return ret;
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2020-04-14 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 5:41 [PATCH] component: Silence bind error on -EPROBE_DEFER James Hilliard
2020-04-11 5:41 ` James Hilliard
2020-04-14 11:07 ` Jani Nikula [this message]
2020-04-14 11:07 ` Jani Nikula
2020-04-14 23:56 ` James Hilliard
2020-04-14 23:56 ` James Hilliard
2020-04-15 7:37 ` Jani Nikula
2020-04-15 7:37 ` Jani Nikula
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=87lfmymilm.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=james.hilliard1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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 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.