From: Vincent Cheng <vscheng@gmail.com>
To: Sarath Babu Naidu Gaddam <sarath.babu.naidu.gaddam@amd.com>,
richardcochran@gmail.com, netdev@vger.kernel.org
Cc: simon.horman@corigine.com, andrew@lunn.ch,
linux-kernel@vger.kernel.org, harini.katakam@amd.com,
git@amd.com
Subject: Re: [PATCH V2] ptp: clockmatrix: Add Defer probe if firmware load fails
Date: Sat, 17 Jun 2023 20:54:28 -0400 [thread overview]
Message-ID: <ZI5VxN8o+VvwrZ+5@vcheng-VirtualBox> (raw)
On Sun, Jun 18, 2023 at 12:51:08AM +0000, Vincent Cheng wrote:
>
>
> -----Original Message-----
> From: Sarath Babu Naidu Gaddam <sarath.babu.naidu.gaddam@amd.com>
> Sent: Wednesday, June 14, 2023 1:12 AM
> To: richardcochran@gmail.com; netdev@vger.kernel.org
> Cc: simon.horman@corigine.com; andrew@lunn.ch; linux-kernel@vger.kernel.org; Vincent Cheng <vincent.cheng.xh@renesas.com>; harini.katakam@amd.com; git@amd.com; sarath.babu.naidu.gaddam@amd.com
> Subject: [PATCH V2] ptp: clockmatrix: Add Defer probe if firmware load fails
>
> Clock matrix driver can be probed before the rootfs containing firmware/initialization .bin is available. The current driver throws a warning and proceeds to execute probe even when firmware is not ready. Instead, defer probe and wait for the .bin file to be available.
>
> Signed-off-by: Sarath Babu Naidu Gaddam <sarath.babu.naidu.gaddam@amd.com>
Reviewed-by: Vincent Cheng <vincent.cheng.xh@renesas.com>
> ---
> Changes in V2:
> 1) Added mutex_unlock(idtcm->lock); before returning EPROBE_DEFER.
> 2) Moved failure log after defer probe.
> ---
> drivers/ptp/ptp_clockmatrix.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/ptp/ptp_clockmatrix.c b/drivers/ptp/ptp_clockmatrix.c index c9d451bf89e2..b3cb136257e3 100644
> --- a/drivers/ptp/ptp_clockmatrix.c
> +++ b/drivers/ptp/ptp_clockmatrix.c
> @@ -2424,8 +2424,13 @@ static int idtcm_probe(struct platform_device *pdev)
>
> err = idtcm_load_firmware(idtcm, &pdev->dev);
>
> - if (err)
> + if (err) {
> + if (err == -ENOENT) {
> + mutex_unlock(idtcm->lock);
> + return -EPROBE_DEFER;
> + }
> dev_warn(idtcm->dev, "loading firmware failed with %d", err);
> + }
>
> wait_for_chip_ready(idtcm);
>
> --
> 2.25.1
>
next reply other threads:[~2023-06-18 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 0:54 Vincent Cheng [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-14 5:12 [PATCH V2] ptp: clockmatrix: Add Defer probe if firmware load fails Sarath Babu Naidu Gaddam
2023-06-15 20:05 ` Jakub Kicinski
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=ZI5VxN8o+VvwrZ+5@vcheng-VirtualBox \
--to=vscheng@gmail.com \
--cc=andrew@lunn.ch \
--cc=git@amd.com \
--cc=harini.katakam@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=sarath.babu.naidu.gaddam@amd.com \
--cc=simon.horman@corigine.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;
as well as URLs for NNTP newsgroup(s).