public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@freescale.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Rong Wang <wr011235813@gmail.com>, <balbi@ti.com>,
	Arnd Bergmann <arnd@arndb.de>, <linux-usb@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <Rong.Wang@csr.com>
Subject: Re: [PATCH] usb: udc: add gadget state kobject uevent
Date: Wed, 17 Jul 2013 10:36:50 +0800	[thread overview]
Message-ID: <20130717023649.GD29679@nchen-desktop> (raw)
In-Reply-To: <20130716063117.GA30320@kroah.com>

On Mon, Jul 15, 2013 at 11:31:17PM -0700, Greg KH wrote:
> On Tue, Jul 16, 2013 at 11:49:07AM +0800, Rong Wang wrote:
> > Hi Greg,
> > 
> > The USB on our platform can change roles between HOST and GADGET, but
> > it is not capable of OTG.
> 
> That kind of sounds like the definition of OTG :)
> 
> > When the USB changes between roles the udev will run some scripts
> > automatically according to the udev rules.
> 
> What exactly does udev/userspace see when the roles change?
> 
> And what can trigger the change in roles?
> 
> > The default role is GADGET, and we bind the g_mass_storage to the USB
> > GADGET role.
> > 
> > We should secure the back end file storage between the device and the
> > host PC connecting to our device.
> > We need to know when the GADGET is really connect to a host PC, then
> > we can umount the file on the device
> > and export it to the g_mass_storage.
> 
> I thought you already get an event for this, otherwise no one would be
> able to properly deal with this.
> 
> > The question is since we default GADGET, so the g_mass_storage.ko is
> > installed early but connecting to a host PC
> > is randomly, But the udev has no idea when a host PC connects our device.
> > 
> > So we consider it's reasonable to let the udev know the GADGET device state.
> > Is there any alternative to our question?
> 
> I thought we already export events for gadget device states, have you
> looked for them?  I can't dig through the code at the moment, but this
> seems like a pretty common issue...
> 

If I understand correctly,  what Rong wants is udev can be notified the
udc state changes, like connect/disconnect event. Currently, we only
export it to /sys.

-- 

Best Regards,
Peter Chen


  reply	other threads:[~2013-07-17  2:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15  3:57 [PATCH] usb: udc: add gadget state kobject uevent Rong Wang
2013-07-15 16:52 ` Greg KH
2013-07-16  3:49   ` Rong Wang
2013-07-16  6:31     ` Greg KH
2013-07-17  2:36       ` Peter Chen [this message]
2013-07-18  8:25         ` Rong Wang
2013-07-20 10:57           ` Chen Peter-B29397
2013-07-17  5:50       ` Rong Wang
2013-07-17  7:57       ` Felipe Balbi
2013-07-17 13:04         ` Rong Wang
2013-07-17 13:27           ` Felipe Balbi
2013-07-17 15:37             ` Alan Stern
2013-07-18  8:22               ` Felipe Balbi
2013-07-18 13:50                 ` Alan Stern
2013-07-22  9:28                   ` Felipe Balbi
2013-07-18  8:33             ` Rong Wang
2013-07-18  8:40               ` Felipe Balbi
2013-07-18  9:28                 ` Rong Wang
2013-07-18 10:10                   ` Felipe Balbi
2013-07-18 10:54                     ` Rong Wang
2013-07-18 11:06                       ` Felipe Balbi
2013-07-26  5:56                     ` Barry Song
2013-07-26 15:23                       ` Greg KH
2013-07-18 10:08                 ` Felipe Balbi
2013-07-17 16:35         ` Greg KH
2013-07-24  9:11           ` Barry Song
  -- strict thread matches above, loose matches on Subject: below --
2013-07-15  4:58 Rong Wang

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=20130717023649.GD29679@nchen-desktop \
    --to=peter.chen@freescale.com \
    --cc=Rong.Wang@csr.com \
    --cc=arnd@arndb.de \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=wr011235813@gmail.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