All of
 help / color / mirror / Atom feed
From: Stephen Boyd <>
To: Benson Leung <>,
	Enric Balletbo i Serra <>
Cc:, Simon Glass <>,
	Gwendal Grignou <>,
	Douglas Anderson <>,
	Alexandru M Stan <>
Subject: [PATCH 1/2] platform/chrome: cros_ec_spi: Don't overwrite spi::mode
Date: Wed,  2 Dec 2020 17:16:48 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

There isn't any need to overwrite the mode here in the driver with what
has been detected by the firmware, such as DT or ACPI. In fact, if we
use the SPI CS gpio descriptor feature we will overwrite the mode with
SPI_MODE_0 where it already contains SPI_MODE_0 and more importantly
SPI_CS_HIGH. Clearing the SPI_CS_HIGH bit causes the CS line to toggle
when the device is probed when it shouldn't change, confusing the driver
and making it fail to probe. Drop the assignment and let the spi core
take care of it.

Fixes: a17d94f0b6e1 ("mfd: Add ChromeOS EC SPI driver")
Cc: Simon Glass <>
Cc: Gwendal Grignou <>
Cc: Douglas Anderson <>
Cc: Alexandru M Stan <>
Signed-off-by: Stephen Boyd <>
 drivers/platform/chrome/cros_ec_spi.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/platform/chrome/cros_ec_spi.c b/drivers/platform/chrome/cros_ec_spi.c
index dfa1f816a45f..f9df218fc2bb 100644
--- a/drivers/platform/chrome/cros_ec_spi.c
+++ b/drivers/platform/chrome/cros_ec_spi.c
@@ -742,7 +742,6 @@ static int cros_ec_spi_probe(struct spi_device *spi)
 	int err;
 	spi->bits_per_word = 8;
-	spi->mode = SPI_MODE_0;
 	spi->rt = true;
 	err = spi_setup(spi);
 	if (err < 0)

  reply	other threads:[~2020-12-03  1:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03  1:16 [PATCH 0/2] cros_ec_spi: Work better with CS GPIO descriptors Stephen Boyd
2020-12-03  1:16 ` Stephen Boyd [this message]
2020-12-03  1:17   ` [PATCH 1/2] platform/chrome: cros_ec_spi: Don't overwrite spi::mode Doug Anderson
2020-12-04  9:15   ` Enric Balletbo i Serra
2020-12-03  1:16 ` [PATCH 2/2] platform/chrome: cros_ec_spi: Drop bits_per_word assignment Stephen Boyd
2020-12-03  1:18   ` Doug Anderson
2020-12-04  9:15   ` Enric Balletbo i Serra

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* 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.