All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	Jean Delvare <jdelvare@suse.com>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	gregkh@linuxfoundation.org, Johan Hovold <johan@kernel.org>,
	Alex Elder <elder@linaro.org>
Subject: Re: [PATCH 0/2] i2c-dev: Don't let userspace block adapter
Date: Wed, 6 Jul 2016 08:34:49 -0700	[thread overview]
Message-ID: <20160706153449.GL2671@ubuntu> (raw)
In-Reply-To: <577D1895.3060202@metafoo.de>

On 06-07-16, 16:41, Lars-Peter Clausen wrote:
> On 07/06/2016 04:57 AM, Viresh Kumar wrote:
> > Hi Wolfram/Jean,
> > 
> > I am part of the kernel team for Google's projectara [1], where we are
> > building a module smart phone.
> > 
> > This series tries to fix one of the problems we hit on our system as we
> > are required to hotplug pretty much every thing on the phone and so this
> > fixes hotplug issues with i2c-dev.
> > 
> > As described in the second patch, the current implementation of i2c-dev
> > file operations doesn't let the modules (hardware attached to the phone)
> > eject from the phone as the cleanup path for the module hasn't finished
> > yet (i2c adapter not removed).
> > 
> > We can't let the userspace block the kernel devices forever in such
> > cases.
> > 
> > I was able to test them on the ARA phone with kernel 3.10 only and not
> > mainline.
> 
> This sounds like you want hot-unplug. This is currently not support by the
> I2C framework for adapters. A better approach compared to this series might
> be to implement full hot-unplug support for I2C adapters. This will probably
> also be useful for additional usecases.

Yeah, we need hot-unplug.

Hmm, doing that would require more knowledge of the framework and I am
afraid I don't have it right now, not that it can't be done :)

-- 
viresh

      reply	other threads:[~2016-07-06 15:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06  2:57 [PATCH 0/2] i2c-dev: Don't let userspace block adapter Viresh Kumar
2016-07-06  2:57 ` [PATCH 1/2] i2c-dev: don't get i2c adapter via i2c_dev Viresh Kumar
2016-07-06 17:04   ` Jean Delvare
2016-07-06 17:07     ` Viresh Kumar
2016-07-07 13:16   ` Jean Delvare
2016-07-07 15:35     ` Viresh Kumar
2016-07-08  1:31   ` Wolfram Sang
2016-07-06  2:57 ` [PATCH 2/2] i2c-dev: Don't block the adapter from unregistering Viresh Kumar
2016-07-06  4:32   ` kbuild test robot
2016-07-06  4:32     ` kbuild test robot
2016-07-06  6:55   ` Wolfram Sang
2016-07-06 13:50     ` Viresh Kumar
2016-07-06 17:12     ` Jean Delvare
2016-07-06 20:55       ` Viresh Kumar
2016-07-11 12:22         ` Jean Delvare
2016-07-11 21:50           ` Greg KH
2016-07-18 20:20             ` Viresh Kumar
2016-07-25  9:39             ` Jean Delvare
2016-07-25 22:31               ` Viresh Kumar
2016-07-26  7:41                 ` Jean Delvare
2016-07-26 15:18                   ` Dmitry Torokhov
2016-07-06  8:22   ` Peter Rosin
2016-07-06  8:22     ` Peter Rosin
2016-07-06 14:33     ` Viresh Kumar
2016-07-06 14:43       ` Lars-Peter Clausen
2016-07-06 15:04         ` Peter Rosin
2016-07-06 15:04           ` Peter Rosin
2016-07-06 15:37           ` Viresh Kumar
2016-07-06 15:35         ` Viresh Kumar
2016-07-06 14:41 ` [PATCH 0/2] i2c-dev: Don't let userspace block adapter Lars-Peter Clausen
2016-07-06 15:34   ` Viresh Kumar [this message]

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=20160706153449.GL2671@ubuntu \
    --to=viresh.kumar@linaro.org \
    --cc=elder@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jdelvare@suse.com \
    --cc=johan@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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.