From: Srinivas Neeli <srinivas.neeli@xilinx.com> To: wg@grandegger.com, mkl@pengutronix.de, davem@davemloft.net, michal.simek@xilinx.com, appanad@xilinx.com Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, git@xilinx.com, nagasure@xilinx.com, Venkatesh Yadav Abbarapu <venkatesh.abbarapu@xilinx.com>, Srinivas Neeli <srinivas.neeli@xilinx.com> Subject: [PATCH 1/2] can: xilinx_can: skip error message on deferred probe Date: Wed, 20 Nov 2019 17:41:04 +0530 [thread overview] Message-ID: <1574251865-19592-2-git-send-email-srinivas.neeli@xilinx.com> (raw) In-Reply-To: <1574251865-19592-1-git-send-email-srinivas.neeli@xilinx.com> From: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@xilinx.com> When can clock is provided from the clock wizard, clock wizard driver may not be available when can driver probes resulting to the error message "bus clock not found error". As this error message is not very useful to the end user, skip printing in the case of deferred probe. Signed-off-by: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@xilinx.com> Signed-off-by: Srinivas Neeli <srinivas.neeli@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> --- drivers/net/can/xilinx_can.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/net/can/xilinx_can.c b/drivers/net/can/xilinx_can.c index 4a96e2dd7d77..c5f05b994435 100644 --- a/drivers/net/can/xilinx_can.c +++ b/drivers/net/can/xilinx_can.c @@ -1772,7 +1772,8 @@ static int xcan_probe(struct platform_device *pdev) priv->bus_clk = devm_clk_get(&pdev->dev, devtype->bus_clk_name); if (IS_ERR(priv->bus_clk)) { - dev_err(&pdev->dev, "bus clock not found\n"); + if (PTR_ERR(priv->bus_clk) != -EPROBE_DEFER) + dev_err(&pdev->dev, "bus clock not found\n"); ret = PTR_ERR(priv->bus_clk); goto err_free; } -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Srinivas Neeli <srinivas.neeli@xilinx.com> To: wg@grandegger.com, mkl@pengutronix.de, davem@davemloft.net, michal.simek@xilinx.com, appanad@xilinx.com Cc: Srinivas Neeli <srinivas.neeli@xilinx.com>, netdev@vger.kernel.org, Venkatesh Yadav Abbarapu <venkatesh.abbarapu@xilinx.com>, linux-kernel@vger.kernel.org, linux-can@vger.kernel.org, nagasure@xilinx.com, git@xilinx.com, linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/2] can: xilinx_can: skip error message on deferred probe Date: Wed, 20 Nov 2019 17:41:04 +0530 [thread overview] Message-ID: <1574251865-19592-2-git-send-email-srinivas.neeli@xilinx.com> (raw) In-Reply-To: <1574251865-19592-1-git-send-email-srinivas.neeli@xilinx.com> From: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@xilinx.com> When can clock is provided from the clock wizard, clock wizard driver may not be available when can driver probes resulting to the error message "bus clock not found error". As this error message is not very useful to the end user, skip printing in the case of deferred probe. Signed-off-by: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@xilinx.com> Signed-off-by: Srinivas Neeli <srinivas.neeli@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> --- drivers/net/can/xilinx_can.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/net/can/xilinx_can.c b/drivers/net/can/xilinx_can.c index 4a96e2dd7d77..c5f05b994435 100644 --- a/drivers/net/can/xilinx_can.c +++ b/drivers/net/can/xilinx_can.c @@ -1772,7 +1772,8 @@ static int xcan_probe(struct platform_device *pdev) priv->bus_clk = devm_clk_get(&pdev->dev, devtype->bus_clk_name); if (IS_ERR(priv->bus_clk)) { - dev_err(&pdev->dev, "bus clock not found\n"); + if (PTR_ERR(priv->bus_clk) != -EPROBE_DEFER) + dev_err(&pdev->dev, "bus clock not found\n"); ret = PTR_ERR(priv->bus_clk); goto err_free; } -- 2.7.4 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-20 12:11 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-20 12:11 [PATCH 0/2] can: xilinx_can: Bug fixes on can driver Srinivas Neeli 2019-11-20 12:11 ` Srinivas Neeli 2019-11-20 12:11 ` Srinivas Neeli [this message] 2019-11-20 12:11 ` [PATCH 1/2] can: xilinx_can: skip error message on deferred probe Srinivas Neeli 2019-11-22 14:28 ` Marc Kleine-Budde 2019-11-22 14:28 ` Marc Kleine-Budde 2019-11-25 3:58 ` Appana Durga Kedareswara Rao 2019-11-25 3:58 ` Appana Durga Kedareswara Rao 2019-11-25 3:58 ` Appana Durga Kedareswara Rao 2019-11-20 12:11 ` [PATCH 2/2] can: xilinx_can: Fix usage of skb memory Srinivas Neeli 2019-11-20 12:11 ` Srinivas Neeli 2019-11-20 12:37 ` Marc Kleine-Budde 2019-11-20 12:37 ` Marc Kleine-Budde 2019-11-20 12:42 ` [PATCH 0/2] can: xilinx_can: Bug fixes on can driver Marc Kleine-Budde 2019-11-20 12:42 ` Marc Kleine-Budde 2019-11-20 15:54 ` Appana Durga Kedareswara Rao 2019-11-20 15:54 ` Appana Durga Kedareswara Rao 2019-11-20 15:54 ` Appana Durga Kedareswara Rao
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=1574251865-19592-2-git-send-email-srinivas.neeli@xilinx.com \ --to=srinivas.neeli@xilinx.com \ --cc=appanad@xilinx.com \ --cc=davem@davemloft.net \ --cc=git@xilinx.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-can@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=michal.simek@xilinx.com \ --cc=mkl@pengutronix.de \ --cc=nagasure@xilinx.com \ --cc=netdev@vger.kernel.org \ --cc=venkatesh.abbarapu@xilinx.com \ --cc=wg@grandegger.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: linkBe 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.