All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, stable@vger.kernel.org
Subject: [1/2] usb: typec: tps6598x: handle block reads separately with plain-I2C adapters
Date: Mon, 23 Apr 2018 11:03:09 +0300	[thread overview]
Message-ID: <20180423080309.GG25303@kuha.fi.intel.com> (raw)

On Fri, Apr 20, 2018 at 10:26:08AM -0700, Guenter Roeck wrote:
> On Wed, Apr 18, 2018 at 03:34:09PM +0300, Heikki Krogerus wrote:
> > If the I2C adapter that the PD controller is attached to
> > does not support SMBus protocol, the driver needs to handle
> > block reads separately. The first byte returned in block
> > read protocol will show the total number of bytes. It needs
> > to be stripped away.
> > 
> > This is handled separately in the driver only because right
> > now we have no way of requesting the used protocol with
> > regmap-i2c. This is in practice a workaround for what is
> > really a problem in regmap-i2c. The other option would have
> > been to register custom regmap, or not use regmap at all,
> > however, since the solution is very simple, I choose to use
> > it in this case for convenience. It is easy to remove once
> > we figure out how to handle this kind of cases in
> > regmap-i2c.
> > 
> > Fixes: 0a4c005bd171 ("usb: typec: driver for TI TPS6598x USB Power Delivery controllers")
> > Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > ---
> >  drivers/usb/typec/tps6598x.c | 42 ++++++++++++++++++++++++++++++------
> >  1 file changed, 35 insertions(+), 7 deletions(-)
> > 
> > diff --git a/drivers/usb/typec/tps6598x.c b/drivers/usb/typec/tps6598x.c
> > index 8b8406867c02..82f09cd9792d 100644
> > --- a/drivers/usb/typec/tps6598x.c
> > +++ b/drivers/usb/typec/tps6598x.c
> > @@ -73,6 +73,7 @@ struct tps6598x {
> >  	struct device *dev;
> >  	struct regmap *regmap;
> >  	struct mutex lock; /* device lock */
> > +	u8 i2c_protocol:1;
> >  
> >  	struct typec_port *port;
> >  	struct typec_partner *partner;
> > @@ -80,6 +81,23 @@ struct tps6598x {
> >  	struct typec_capability typec_cap;
> >  };
> >  
> > +static int
> > +tps6598x_block_read(struct tps6598x *tps, u8 reg, void *val, ssize_t len)
> > +{
> > +	u8 data[len + 1];
> > +	int ret;
> > +
> > +	if (!tps->i2c_protocol)
> > +		return regmap_raw_read(tps->regmap, reg, val, len);
> > +
> > +	ret = regmap_raw_read(tps->regmap, reg, data, sizeof(data));
> > +	if (ret)
> > +		return ret;
> > +
> 
> Sanity check ?
> 	if (data[0] != len)
> 		return -Esomething;

No. Then we would not even need the len parameter. The idea is to
allow reading a number of bytes specified by caller, regardless of the
maximum size of the block.


Thanks,

             reply	other threads:[~2018-04-23  8:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23  8:03 Heikki Krogerus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-24 13:45 [1/2] usb: typec: tps6598x: handle block reads separately with plain-I2C adapters Heikki Krogerus
2018-04-24 13:02 Guenter Roeck
2018-04-24 11:46 Heikki Krogerus
2018-04-23 16:43 Guenter Roeck
2018-04-22 12:54 Greg Kroah-Hartman
2018-04-20 17:26 Guenter Roeck
2018-04-18 12:34 Heikki Krogerus

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=20180423080309.GG25303@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=stable@vger.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.