From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Duggan <aduggan@synaptics.com>
Subject: Re: [PATCH] Input: synaptics-rmi4 - Fix error handling in I2C transport driver
Date: Fri, 30 Sep 2016 16:02:03 -0700 [thread overview]
Message-ID: <20160930230203.GH30208@dtor-ws> (raw)
In-Reply-To: <20160930225403.GG30208@dtor-ws>
On Fri, Sep 30, 2016 at 03:54:03PM -0700, Dmitry Torokhov wrote:
> On Thu, Sep 29, 2016 at 10:55:40AM -0700, Bjorn Andersson wrote:
> > On Wed 28 Sep 17:37 PDT 2016, Guenter Roeck wrote:
> >
> > > Instantiating the rmi4 I2C transport driver without interrupts assigned
> > > (for example using manual i2c instantiation from the command line)
> > > caused the driver to fail to load, but it does not clean up its
> > > regulator or transport device registrations. Result is a crash at a later
> > > time, for example when rebooting the system.
> > >
> > > Fixes: 946c8432aab0 ("Input: synaptics-rmi4 - support regulator supplies")
> >
> > Sorry for that.
> >
> > > Fixes: fdf51604f104 ("Input: synaptics-rmi4 - add I2C transport driver")
> > > Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
> >
> > Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
>
> Applied, thank you.
I take it back. rmi_i2c_init_irq() uses devm* so this whole thing mixes
up devm* and manual unregistering and unwind order is completely
broken.
1. Why do we register interrupt from transport drivers and not make it
part of rmi_register_transport_device()?
2. If we need to use some non-devm-ised resources we should use
devm_add_action[_or_reset] to work these operations into devm stream.
Thanks,
>
> It looks like we have similar issue in rmi_spi.c. Can I get another
> patch?
>
> >
> > Regards,
> > Bjorn
> >
> > > Cc: Andrew Duggan <aduggan@synaptics.com>
> > > Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> > > ---
> > > drivers/input/rmi4/rmi_i2c.c | 13 ++++++++++---
> > > 1 file changed, 10 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/drivers/input/rmi4/rmi_i2c.c b/drivers/input/rmi4/rmi_i2c.c
> > > index 6f2e0e4f0296..d57b227ccd25 100644
> > > --- a/drivers/input/rmi4/rmi_i2c.c
> > > +++ b/drivers/input/rmi4/rmi_i2c.c
> > > @@ -285,23 +285,30 @@ static int rmi_i2c_probe(struct i2c_client *client,
> > > retval = rmi_set_page(rmi_i2c, 0);
> > > if (retval) {
> > > dev_err(&client->dev, "Failed to set page select to 0.\n");
> > > - return retval;
> > > + goto error_disable;
> > > }
> > >
> > > retval = rmi_register_transport_device(&rmi_i2c->xport);
> > > if (retval) {
> > > dev_err(&client->dev, "Failed to register transport driver at 0x%.2X.\n",
> > > client->addr);
> > > - return retval;
> > > + goto error_disable;
> > > }
> > >
> > > retval = rmi_i2c_init_irq(client);
> > > if (retval < 0)
> > > - return retval;
> > > + goto error_unregister;
> > >
> > > dev_info(&client->dev, "registered rmi i2c driver at %#04x.\n",
> > > client->addr);
> > > return 0;
> > > +
> > > +error_unregister:
> > > + rmi_unregister_transport_device(&rmi_i2c->xport);
> > > +error_disable:
> > > + regulator_bulk_disable(ARRAY_SIZE(rmi_i2c->supplies),
> > > + rmi_i2c->supplies);
> > > + return retval;
> > > }
> > >
> > > static int rmi_i2c_remove(struct i2c_client *client)
> > > --
> > > 2.5.0
> > >
>
> --
> Dmitry
--
Dmitry
next prev parent reply other threads:[~2016-09-30 23:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 0:37 [PATCH] Input: synaptics-rmi4 - Fix error handling in I2C transport driver Guenter Roeck
2016-09-29 17:55 ` Bjorn Andersson
2016-09-30 22:54 ` Dmitry Torokhov
2016-09-30 23:02 ` Dmitry Torokhov [this message]
2016-10-01 3:44 ` Guenter Roeck
2016-10-01 17:27 ` Andrew Duggan
2016-10-01 17:45 ` Guenter Roeck
2016-10-01 17:51 ` Andrew Duggan
2016-10-01 19:04 ` Dmitry Torokhov
2016-10-01 20:46 ` Guenter Roeck
2016-10-01 3:03 ` Guenter Roeck
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=20160930230203.GH30208@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=aduggan@synaptics.com \
--cc=bjorn.andersson@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).