From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: lee.jones@linaro.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
Sebastian Reichel <sre@kernel.org>
Subject: Re: [PATCH] mfd: motorola-cpcap: Do not hardcode SPI mode flags
Date: Thu, 19 Dec 2019 09:04:09 -0800 [thread overview]
Message-ID: <20191219170409.GH35479@atomide.com> (raw)
In-Reply-To: <20191204231931.21378-1-linus.walleij@linaro.org>
Hi Linus,
* Linus Walleij <linus.walleij@linaro.org> [700101 00:00]:
> The current use of mode flags to us SPI_MODE_0 and
> SPI_CS_HIGH is fragile: it overwrites anything already
> assigned by the SPI core. Change it thusly:
>
> - Just |= the SPI_MODE_0 so we keep other flags
> - Assign ^= SPI_CS_HIGH since we might be active high
> already, and that is usually the case with GPIOs used
> for chip select, even if they are in practice active low.
>
> Add a comment clarifying why ^= SPI_CS_HIGH is the right
> choice here.
Looks like this breaks booting for droid4 with a cpcap
PMIC, probably as regulators won't work. There's no GPIO
controller involved in this case for the chip select, the
pins are directly controlled by the spi-omap2-mcspi.c
driver.
From the pin muxing setup we see there's a pull-down on
mcspi1_cs0 pin meaning it's active high:
/* 0x4a100138 mcspi1_cs0.mcspi1_cs0 ae23 */
OMAP4_IOPAD(0x138, PIN_INPUT_PULLDOWN | MUX_MODE0)
My guess a similar issue is with similar patches for
all non-gpio spi controllers?
Let me know if you want me to test some other changes,
or if this patch depends on some other changes.
Regards,
Tony
> Reported-by: Mark Brown <broonie@kernel.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> drivers/mfd/motorola-cpcap.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mfd/motorola-cpcap.c b/drivers/mfd/motorola-cpcap.c
> index 52f38e57cdc1..a3bc61b8008c 100644
> --- a/drivers/mfd/motorola-cpcap.c
> +++ b/drivers/mfd/motorola-cpcap.c
> @@ -279,7 +279,13 @@ static int cpcap_probe(struct spi_device *spi)
> spi_set_drvdata(spi, cpcap);
>
> spi->bits_per_word = 16;
> - spi->mode = SPI_MODE_0 | SPI_CS_HIGH;
> + spi->mode |= SPI_MODE_0;
> + /*
> + * Active high should be defined as "inverse polarity" as GPIO-based
> + * chip selects can be logically active high but inverted by the GPIO
> + * library.
> + */
> + spi->mode ^= SPI_CS_HIGH;
>
> ret = spi_setup(spi);
> if (ret)
> --
> 2.23.0
>
next prev parent reply other threads:[~2019-12-19 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 23:19 [PATCH] mfd: motorola-cpcap: Do not hardcode SPI mode flags Linus Walleij
2019-12-19 17:04 ` Tony Lindgren [this message]
2020-01-07 9:57 ` Linus Walleij
2020-01-07 18:24 ` Tony Lindgren
2020-01-07 18:37 ` Tony Lindgren
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=20191219170409.GH35479@atomide.com \
--to=tony@atomide.com \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sre@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.