mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Olof Johansson <olof@lixom.net>,
	Benson Leung <bleung@chromium.org>,
	linux-kernel@vger.kernel.org,
	Doug Anderson <dianders@chromium.org>,
	Brian Norris <computersforpeace@gmail.com>,
	Javier Martinez Canillas <javier@osg.samsung.com>,
	Shawn Nematbakhsh <shawnn@chromium.org>,
	Gwendal Grignou <gwendal@chromium.org>,
	Enric Balletbo <enric.balletbo@collabora.co.uk>,
	Tomeu Vizoso <tomeu.vizoso@collabora.com>
Subject: Re: [PATCH] mfd: cros_ec: Use proper protocol transfer function
Date: Wed, 23 Nov 2016 08:37:49 +0000	[thread overview]
Message-ID: <20161123083749.GN10134@dell.home> (raw)
In-Reply-To: <20161122221932.GA60416@google.com>

On Tue, 22 Nov 2016, Brian Norris wrote:

> + Benson
> 
> On Wed, Aug 10, 2016 at 01:45:12PM -0700, Brian Norris wrote:
> > From: Shawn Nematbakhsh <shawnn@chromium.org>
> > 
> > pkt_xfer should be used for protocol v3, and cmd_xfer otherwise. We had
> > one instance of these functions correct, but not the second, fall-back
> > case. We use the fall-back only when the first command returns an
> > IN_PROGRESS status, which is only used on some EC firmwares where we
> > don't want to constantly poll the bus, but instead back off and
> > sleep/retry for a little while.
> > 
> > Fixes: 2c7589af3c4d ("mfd: cros_ec: add proto v3 skeleton")

You need to Cc stable with a note saying which kernel version it
fixes.  Grep the `git log`s for stable.*#.

> > Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org>
> > Signed-off-by: Brian Norris <briannorris@chromium.org>
> > ---
> > MAINTAINERS tells me this goes through Olof, but many things have gone through
> > Lee.
> 
> I believe this was supposed to go through Olof. Olof, are you out there?

Yes, I concur.

There maybe some confusion since the $SUBJECT line is
misleading/incorrect.

> Or Benson? I see this:
> 
> http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1273587.html
> [PATCH] platform/chrome : Add myself as Maintainer
> 
> but it's not merged anywhere AFAICT.
> 
> I can resend if that helps.
> 
> Brian
> 
> >  drivers/platform/chrome/cros_ec_proto.c | 8 +++++---
> >  1 file changed, 5 insertions(+), 3 deletions(-)
> > 
> > diff --git a/drivers/platform/chrome/cros_ec_proto.c b/drivers/platform/chrome/cros_ec_proto.c
> > index 6c084b266651..591f0b0becbd 100644
> > --- a/drivers/platform/chrome/cros_ec_proto.c
> > +++ b/drivers/platform/chrome/cros_ec_proto.c
> > @@ -59,12 +59,14 @@ static int send_command(struct cros_ec_device *ec_dev,
> >  			struct cros_ec_command *msg)
> >  {
> >  	int ret;
> > +	int (*xfer_fxn)(struct cros_ec_device *ec, struct cros_ec_command *msg);
> >  
> >  	if (ec_dev->proto_version > 2)
> > -		ret = ec_dev->pkt_xfer(ec_dev, msg);
> > +		xfer_fxn = ec_dev->pkt_xfer;
> >  	else
> > -		ret = ec_dev->cmd_xfer(ec_dev, msg);
> > +		xfer_fxn = ec_dev->cmd_xfer;
> >  
> > +	ret = (*xfer_fxn)(ec_dev, msg);
> >  	if (msg->result == EC_RES_IN_PROGRESS) {
> >  		int i;
> >  		struct cros_ec_command *status_msg;
> > @@ -87,7 +89,7 @@ static int send_command(struct cros_ec_device *ec_dev,
> >  		for (i = 0; i < EC_COMMAND_RETRIES; i++) {
> >  			usleep_range(10000, 11000);
> >  
> > -			ret = ec_dev->cmd_xfer(ec_dev, status_msg);
> > +			ret = (*xfer_fxn)(ec_dev, status_msg);
> >  			if (ret < 0)
> >  				break;
> >  

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  parent reply	other threads:[~2016-11-23  8:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 20:45 Brian Norris
2016-08-30 14:38 ` Lee Jones
2016-11-22 22:19 ` Brian Norris
2016-11-22 23:01   ` Benson Leung
2016-11-23  8:37   ` Lee Jones [this message]
2016-11-28 22:13     ` Brian Norris

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=20161123083749.GN10134@dell.home \
    --to=lee.jones@linaro.org \
    --cc=bleung@chromium.org \
    --cc=briannorris@chromium.org \
    --cc=computersforpeace@gmail.com \
    --cc=dianders@chromium.org \
    --cc=enric.balletbo@collabora.co.uk \
    --cc=gwendal@chromium.org \
    --cc=javier@osg.samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=shawnn@chromium.org \
    --cc=tomeu.vizoso@collabora.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

Powered by JetHome