From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Weifeng Liu <weifeng.liu.z@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-serial@vger.kernel.org,
Maximilian Luz <luzmaximilian@gmail.com>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [RFC PATCH 2/2] platform/surface: aggregator: Log critical errors during SAM probing
Date: Thu, 2 May 2024 18:15:48 +0300 [thread overview]
Message-ID: <ZjOuJC9NcYHvgWcY@smile.fi.intel.com> (raw)
In-Reply-To: <20240502040255.655957-4-weifeng.liu.z@gmail.com>
On Thu, May 02, 2024 at 12:02:47PM +0800, Weifeng Liu wrote:
> Emits messages upon errors during probing of SAM. Hopefully this could
> provide useful context to user for the purpose of diagnosis when
> something miserable happen.
...
> - if (gpiod_count(&serdev->dev, NULL) < 0)
> + if (gpiod_count(&serdev->dev, NULL) < 0) {
> + dev_err(&serdev->dev, "no GPIO found\n");
> return -ENODEV;
Why not
return dev_err_probe(...);
?
Also while at it, unshadow the error code
status = gpiod_count(&serdev->dev, NULL);
if (status < 0)
return dev_err_probe(..., status, ...);
> + }
...
> astatus = ssam_serdev_setup_via_acpi(ssh->handle, serdev);
> if (ACPI_FAILURE(astatus)) {
> status = -ENXIO;
> + dev_err(&serdev->dev, "failed to setup serdev\n");
In the similar way
status = dev_err(&serdev->dev, -ENXIO, "failed to setup serdev\n");
> goto err_devinit;
> }
...
> status = ssam_log_firmware_version(ctrl);
> - if (status)
> + if (status) {
> + dev_err(&serdev->dev, "failed to get firmware version\n");
> goto err_initrq;
Use dev_err_probe() everywhere for the sake of uniform output format.
> + }
...
> status = ssam_ctrl_notif_d0_entry(ctrl);
> - if (status)
> + if (status) {
> + dev_err(&serdev->dev, "failed to notify EC of entry of D0\n");
> goto err_initrq;
Ditto.
> + }
>
> status = ssam_ctrl_notif_display_on(ctrl);
> - if (status)
> + if (status) {
> + dev_err(&serdev->dev, "failed to notify EC of display on\n");
> goto err_initrq;
Ditto.
> + }
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-05-02 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 4:02 [RFC PATCH 0/2] Defer probing of SAM if serdev device is not ready Weifeng Liu
2024-05-02 4:02 ` [RFC PATCH 1/2] platform/surface: aggregator: Defer probing when serdev " Weifeng Liu
2024-05-02 15:19 ` Andy Shevchenko
2024-05-02 4:02 ` [RFC PATCH 2/2] platform/surface: aggregator: Log critical errors during SAM probing Weifeng Liu
2024-05-02 15:15 ` Andy Shevchenko [this message]
2024-05-02 8:38 ` [RFC PATCH 0/2] Defer probing of SAM if serdev device is not ready Hans de Goede
2024-05-02 20:03 ` Maximilian Luz
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=ZjOuJC9NcYHvgWcY@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-serial@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=weifeng.liu.z@gmail.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