Re: [PATCH v3] mfd: cros ec: Lock the SPI bus while holding chipselect

On Wed, 25 Nov 2015, Nicolas Boichat wrote: > cros_ec_cmd_xfer_spi and cros_ec_pkt_xfer_spi generally work like > this: > - Pull CS down (active), wait a bit, then send a command > - Wait for response (multiple requests) > - Wait a while, pull CS up (inactive) > > These operations, individuall

Re: [PATCH v3] mfd: cros ec: Lock the SPI bus while holding chipselect

Reviewed-by: Gwendal Grignou On Wed, Nov 25, 2015 at 12:12 AM, Lee Jones wrote: > On Wed, 25 Nov 2015, Nicolas Boichat wrote: > >> cros_ec_cmd_xfer_spi and cros_ec_pkt_xfer_spi generally work like >> this: >> - Pull CS down (active), wait a bit, then send a command >> - Wait for response (mult

Re: [PATCH v3] mfd: cros ec: Lock the SPI bus while holding chipselect

On Wed, 25 Nov 2015, Nicolas Boichat wrote: > cros_ec_cmd_xfer_spi and cros_ec_pkt_xfer_spi generally work like > this: > - Pull CS down (active), wait a bit, then send a command > - Wait for response (multiple requests) > - Wait a while, pull CS up (inactive) > > These operations, individuall

[PATCH v3] mfd: cros ec: Lock the SPI bus while holding chipselect

cros_ec_cmd_xfer_spi and cros_ec_pkt_xfer_spi generally work like this: - Pull CS down (active), wait a bit, then send a command - Wait for response (multiple requests) - Wait a while, pull CS up (inactive) These operations, individually, lock the SPI bus, but there is nothing preventing the SP