From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755869AbdKMVTb (ORCPT ); Mon, 13 Nov 2017 16:19:31 -0500 Received: from mail-pg0-f66.google.com ([74.125.83.66]:52159 "EHLO mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755823AbdKMVT0 (ORCPT ); Mon, 13 Nov 2017 16:19:26 -0500 X-Google-Smtp-Source: AGs4zMZLFenVca7vgWneRIYTuJL68OadeUVXJkJL7IElC2Rn/1vSLOWRQkQb2QaSkxrtpOIn1tBPPg== Date: Mon, 13 Nov 2017 13:19:23 -0800 From: Brian Norris To: Jon Hunter Cc: Lee Jones , linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org, Shawn Nematbakhsh , Benson Leung , Doug Anderson Subject: Re: [PATCH 1/2] mfd: cros ec: spi: Don't send first message too soon Message-ID: <20171113211900.GA126873@google.com> References: <1510607140-30582-1-git-send-email-jonathanh@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1510607140-30582-1-git-send-email-jonathanh@nvidia.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org + others On Mon, Nov 13, 2017 at 09:05:39PM +0000, Jon Hunter wrote: > On the Tegra124 Nyan-Big chromebook the very first SPI message sent to > the EC is failing. > > The Tegra SPI driver configures the SPI chip-selects to be active-high > by default (and always has for many years). The EC SPI requires an > active-low chip-select and so the Tegra chip-select is reconfigured to > be active-low when the EC SPI driver calls spi_setup(). The problem is > that if the first SPI message to the EC is sent too soon after > reconfiguring the SPI chip-select, it fails. > > The EC SPI driver prevents back-to-back SPI messages being sent too > soon by keeping track of the time the last transfer was sent via the > variable 'last_transfer_ns'. To prevent the very first transfer being > sent too soon, initialise the 'last_transfer_ns' variable after calling > spi_setup() and before sending the first SPI message. > > Signed-off-by: Jon Hunter > --- > Looks like this issue has been around for several Linux releases now > and it just depends on timing if this issue is seen or not and so there > is no specific commit this fixes. However, would be good to include for > v4.15. I wonder if that doesn't mean we should have a stable tag still? Cc: > drivers/mfd/cros_ec_spi.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/mfd/cros_ec_spi.c b/drivers/mfd/cros_ec_spi.c > index c9714072e224..a14196e95e9b 100644 > --- a/drivers/mfd/cros_ec_spi.c > +++ b/drivers/mfd/cros_ec_spi.c > @@ -667,6 +667,7 @@ static int cros_ec_spi_probe(struct spi_device *spi) > sizeof(struct ec_response_get_protocol_info); > ec_dev->dout_size = sizeof(struct ec_host_request); > > + ec_spi->last_transfer_ns = ktime_get_ns(); Seems pretty reasonable to me: Reviewed-by: Brian Norris > > err = cros_ec_register(ec_dev); > if (err) { > -- > 2.7.4 >