From: Lee Jones <lee.jones@linaro.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Olof Johansson <olof@lixom.net>,
bleung@chromium.org, martinez.javier@gmail.com,
Guenter Roeck <groeck@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
rtc-linux@googlegroups.com, Vic Yang <victoryang@google.com>
Subject: Re: [PATCH 1/7] mfd: cros-ec: Fix host command buffer size
Date: Mon, 3 Apr 2017 15:30:20 +0100 [thread overview]
Message-ID: <20170403143020.mti5vdig6vvlcb2d@dell> (raw)
In-Reply-To: <20170403142357.2usczfylqbg6cgcx@dell>
On Mon, 03 Apr 2017, Lee Jones wrote:
> On Fri, 24 Mar 2017, Enric Balletbo i Serra wrote:
>
> > From: Vic Yang <victoryang@google.com>
> >
> > For SPI, we can get up to 32 additional bytes for response preamble.
> > The current overhead (2 bytes) may cause problems when we try to receive
> > a big response. Update it to 32 bytes.
> >
> > Without this fix we could see a kernel BUG when we receive a big response
> > from the Chrome EC when is connected via SPI.
> >
> > Signed-off-by: Vic Yang <victoryang@google.com>
> > Tested-by: Enric Balletbo i Serra <enric.balletbo.collabora.com>
> > ---
> >
> > This patch is a FIX, and I think that would be interesting see it merged
> > in this release cycle. This should go through the MFD tree and can be picked
> > independently of the other patches. Lee Jones I think this is for you.
> >
> > include/linux/mfd/cros_ec.h | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
>
> Applied, thanks.
Scrap that, I'll keep it with the set.
> > diff --git a/include/linux/mfd/cros_ec.h b/include/linux/mfd/cros_ec.h
> > index b3e812f..3b16c90 100644
> > --- a/include/linux/mfd/cros_ec.h
> > +++ b/include/linux/mfd/cros_ec.h
> > @@ -35,10 +35,11 @@
> > * Max bus-specific overhead incurred by request/responses.
> > * I2C requires 1 additional byte for requests.
> > * I2C requires 2 additional bytes for responses.
> > + * SPI requires up to 32 additional bytes for responses.
> > * */
> > #define EC_PROTO_VERSION_UNKNOWN 0
> > #define EC_MAX_REQUEST_OVERHEAD 1
> > -#define EC_MAX_RESPONSE_OVERHEAD 2
> > +#define EC_MAX_RESPONSE_OVERHEAD 32
> >
> > /*
> > * Command interface between EC and AP, for LPC, I2C and SPI interfaces.
>
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2017-04-03 14:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 17:44 [PATCH 0/7] mfd: cros-ec: Some fixes and improvements Enric Balletbo i Serra
2017-03-24 17:44 ` [PATCH 1/7] mfd: cros-ec: Fix host command buffer size Enric Balletbo i Serra
2017-04-03 14:23 ` Lee Jones
2017-04-03 14:30 ` Lee Jones [this message]
2017-04-03 15:12 ` Enric Balletbo i Serra
2017-04-04 8:37 ` Lee Jones
2017-04-04 8:36 ` Lee Jones
2017-03-24 17:44 ` [PATCH 2/7] iio: cros_ec_sensors: Fix return value to get raw and calibbias data Enric Balletbo i Serra
2017-03-25 15:07 ` Jonathan Cameron
2017-03-24 17:44 ` [PATCH 3/7] iio: cros_ec_sensors: Use devm to setup the triggered buffer Enric Balletbo i Serra
2017-03-25 15:09 ` Jonathan Cameron
2017-03-24 17:44 ` [PATCH 4/7] mfd: cros_ec: Get rid of cros_ec_check_features from cros_ec_dev Enric Balletbo i Serra
2017-03-25 15:22 ` Jonathan Cameron
2017-03-25 15:24 ` Jonathan Cameron
2017-03-27 12:42 ` Lee Jones
2017-04-02 10:41 ` Jonathan Cameron
2017-03-24 17:44 ` [PATCH 5/7] mfd: cros_ec: Introduce RTC commands and events definitions Enric Balletbo i Serra
2017-03-24 17:44 ` [PATCH 6/7] rtc: cros-ec: add cros-ec-rtc driver Enric Balletbo i Serra
2017-03-24 17:44 ` [PATCH 7/7] mfd: cros_ec: add RTC as mfd subdevice Enric Balletbo i Serra
2017-04-03 14:25 ` Lee Jones
2017-04-03 15:06 ` Enric Balletbo i Serra
2017-04-04 8:38 ` Lee Jones
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=20170403143020.mti5vdig6vvlcb2d@dell \
--to=lee.jones@linaro.org \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martinez.javier@gmail.com \
--cc=olof@lixom.net \
--cc=rtc-linux@googlegroups.com \
--cc=victoryang@google.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: 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