linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Hung-yu Wu <hywu@google.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	hywu@chromium.org, ejcaruso@chromium.org, drinkcat@chromium.org,
	kyan@chromium.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CHROMIUM: ec: register shutdown function to clear delayed works
Date: Wed, 2 Nov 2016 15:59:40 +0800	[thread overview]
Message-ID: <20161102075939.GA5463@google.com> (raw)
In-Reply-To: <20161026142214.GK13127@dell>

On Wed, Oct 26, 2016 at 03:22:14PM +0100, Lee Jones wrote:
> On Wed, 26 Oct 2016, Lee Jones wrote:
> 
> > On Mon, 24 Oct 2016, Daniel Hung-yu Wu wrote:
> > 
> > > This patch applies on top of "mfd: cros_ec: Add EC console read structures
> > > definitions" (https://patchwork.kernel.org/patch/9294887/).
> > > 
> > > This patch is currently against a linux 3.18 kernel.
> > > 
> > > Reboot or shutdown during delayed works could corrupt communication with EC,
> > > and certain I2C controller may not be able to recover from the error state.
> > > A shutdown function is registered to clear delayed works or wait for them to
> > > finish.
> > > 
> > > Signed-off-by: Daniel Hung-yu Wu <hywu@chromium.org>
> > > ---
> > >  drivers/mfd/cros_ec_dev.c | 9 +++++++++
> > >  1 file changed, 9 insertions(+)
> > 
> > Applied, thanks.
> 
> Ah, I thought you'd at least ported it to Mainline!
> 
> You need to do that before posting patches.
> 
> > > diff --git a/drivers/mfd/cros_ec_dev.c b/drivers/mfd/cros_ec_dev.c
> > > index 8618a7c..3e548f1 100644
> > > --- a/drivers/mfd/cros_ec_dev.c
> > > +++ b/drivers/mfd/cros_ec_dev.c
> > > @@ -613,6 +613,14 @@ static int ec_device_remove(struct platform_device *pdev)
> > >  	return 0;
> > >  }
> > >  
> > > +static void ec_device_shutdown(struct platform_device *pdev)
> > > +{
> > > +	struct cros_ec_dev *ec = dev_get_drvdata(&pdev->dev);
> > > +
> > > +	/* Be sure to clear up debugfs delayed works */
> > > +	cros_ec_debugfs_remove(ec);
> > > +}
> > > +
> > >  static int ec_device_suspend(struct device *dev)
> > >  {
> > >  	struct cros_ec_dev *ec = dev_get_drvdata(dev);
> > > @@ -656,6 +664,7 @@ static struct platform_driver cros_ec_dev_driver = {
> > >  	},
> > >  	.probe = ec_device_probe,
> > >  	.remove = ec_device_remove,
> > > +	.shutdown = ec_device_shutdown,
> > >  };
> > >  
> > >  static int __init cros_ec_dev_init(void)
> > 
> 
> -- 
> Lee Jones
> Linaro STMicroelectronics Landing Team Lead
> Linaro.org │ Open source software for ARM SoCs
> Follow Linaro: Facebook | Twitter | Blog

The patch for Mainline is submitted. Thanks.

  reply	other threads:[~2016-11-02  7:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24  7:53 [PATCH] CHROMIUM: ec: register shutdown function to clear delayed works Daniel Hung-yu Wu
2016-10-26 14:04 ` Lee Jones
2016-10-26 14:22   ` Lee Jones
2016-11-02  7:59     ` Daniel Hung-yu Wu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-02  7:36 Daniel Hung-yu Wu

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=20161102075939.GA5463@google.com \
    --to=hywu@google.com \
    --cc=drinkcat@chromium.org \
    --cc=ejcaruso@chromium.org \
    --cc=hywu@chromium.org \
    --cc=kyan@chromium.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).