From: Florian Fainelli <f.fainelli@gmail.com>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>,
broonie@kernel.org, f.fainelli@gmail.com,
bcm-kernel-feedback-list@broadcom.com, p.zabel@pengutronix.de,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/4] spi: bcm63xx-spi: add reset support
Date: Tue, 16 Jun 2020 10:05:06 -0700 [thread overview]
Message-ID: <d79c9e3d-fcf3-84ab-4a13-8ff00b4b2605@gmail.com> (raw)
In-Reply-To: <20200616070223.3401282-2-noltari@gmail.com>
On 6/16/2020 12:02 AM, Álvaro Fernández Rojas wrote:
> bcm63xx arch resets the SPI controller at early boot. However, bmips arch
> needs to perform a reset when probing the driver.
>
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
> ---
> v3: use devm_reset_control_get_optional_exclusive
> v2: use devm_reset_control_get_exclusive
>
> drivers/spi/spi-bcm63xx.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/drivers/spi/spi-bcm63xx.c b/drivers/spi/spi-bcm63xx.c
> index 0f1b10a4ef0c..92e88901189c 100644
> --- a/drivers/spi/spi-bcm63xx.c
> +++ b/drivers/spi/spi-bcm63xx.c
> @@ -18,6 +18,7 @@
> #include <linux/err.h>
> #include <linux/pm_runtime.h>
> #include <linux/of.h>
> +#include <linux/reset.h>
>
> /* BCM 6338/6348 SPI core */
> #define SPI_6348_RSET_SIZE 64
> @@ -493,6 +494,7 @@ static int bcm63xx_spi_probe(struct platform_device *pdev)
> struct bcm63xx_spi *bs;
> int ret;
> u32 num_cs = BCM63XX_SPI_MAX_CS;
> + struct reset_control *reset;
>
> if (dev->of_node) {
> const struct of_device_id *match;
> @@ -529,6 +531,15 @@ static int bcm63xx_spi_probe(struct platform_device *pdev)
> return PTR_ERR(clk);
> }
>
> + reset = devm_reset_control_get_optional_exclusive(dev, NULL);
> + if (IS_ERR(reset)) {
> + ret = PTR_ERR(reset);
> + if (ret != -EPROBE_DEFER)
> + dev_err(dev,
> + "failed to get reset controller: %d\n", ret);
> + return ret;
> + }
When the controller is optional, you don't need to do that manual error
checking, as it does that for you already. You can only do:
if (IS_ERR(reset))
return PTR_ERR(reset);
and that's it. With that fixed in v4, you can add:
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2020-06-16 17:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 7:02 [PATCH v3 0/4] spi: bcm63xx: add BMIPS support Álvaro Fernández Rojas
2020-06-16 7:02 ` [PATCH v3 1/4] spi: bcm63xx-spi: add reset support Álvaro Fernández Rojas
2020-06-16 17:05 ` Florian Fainelli [this message]
2020-06-16 7:02 ` [PATCH v3 2/4] spi: bcm63xx-spi: allow building for BMIPS Álvaro Fernández Rojas
2020-06-16 17:07 ` Mark Brown
2020-06-16 17:15 ` Florian Fainelli
2020-06-16 17:25 ` Mark Brown
2020-06-16 17:31 ` Florian Fainelli
2020-06-16 18:30 ` Mark Brown
2020-06-16 7:02 ` [PATCH v3 3/4] spi: bcm63xx-hsspi: add reset support Álvaro Fernández Rojas
2020-06-16 17:07 ` Florian Fainelli
2020-06-16 7:02 ` [PATCH v3 4/4] spi: bcm63xx-hsspi: allow building for BMIPS Álvaro Fernández Rojas
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=d79c9e3d-fcf3-84ab-4a13-8ff00b4b2605@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=p.zabel@pengutronix.de \
/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
all inboxes | Powered by JetHome®