mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Felipe Balbi <balbi@ti.com>
Cc: Rong Wang <wr011235813@gmail.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 09:35:48 -0700	[thread overview]
Message-ID: <20130717163548.GA14999@kroah.com> (raw)
In-Reply-To: <20130717075706.GC5291@arwen.pp.htv.fi>

On Wed, Jul 17, 2013 at 10:57:06AM +0300, Felipe Balbi wrote:
> Hi,
> 
> On Mon, Jul 15, 2013 at 11:31:17PM -0700, Greg KH wrote:
> > > 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...
> > 
> > Felipe, any ideas?
> 
> we already expose that in sysfs. IIRC udev can act on sysfs changes,
> no ?

If something is polling the sysfs file, yes.  If not, a change event
should be sent to notify people that they need to go re-read it as
something major happened (laptop docked, disk got removed, device
changed state, etc.)

thanks,

greg k-h

  parent reply	other threads:[~2013-07-17 17:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15  3:57 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
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 [this message]
2013-07-24  9:11           ` Barry Song
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=20130717163548.GA14999@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Rong.Wang@csr.com \
    --cc=arnd@arndb.de \
    --cc=balbi@ti.com \
    --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

Powered by JetHome