From: Peter Chen <peter.chen@freescale.com>
To: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
"Balbi, Felipe" <balbi@ti.com>,
"ABRAHAM, KISHON VIJAY" <kishon@ti.com>,
Roger Quadros <rogerq@ti.com>,
Robert Baldyga <r.baldyga@samsung.com>,
<myungjoo.ham@samsung.com>, <linux-usb@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<m.szyprowski@samsung.com>
Subject: Re: [PATCH v3 2/4] extcon: usb-gpio: add support for VBUS detection
Date: Thu, 16 Apr 2015 15:59:58 +0800 [thread overview]
Message-ID: <20150416075957.GB1709@shlinux2> (raw)
In-Reply-To: <1429168424.26621.1.camel@mm-sol.com>
On Thu, Apr 16, 2015 at 10:13:44AM +0300, Ivan T. Ivanov wrote:
> Hi,
>
> On Thu, 2015-04-16 at 16:00 +0900, Chanwoo Choi wrote:
> > Hi Peter,
> >
> > On 04/16/2015 10:59 AM, Peter Chen wrote:
> > >
>
> > > Ok, from USB point, external id/vbus value can't decide
> > > which role the controller will be, the controller driver
> > > will decide role according to many things, eg, user configurations,
> > > id/vbus value, OTG HNP, etc.
> > >
> > > So, from USB controller/phy driver, it doesn't care which cable is
> > > inserted, it cares about id/vbus value. Eg, it can get id/vbus value
> > > and it will be notified when the id/vbus value has changed.
> >
> > OK, I change the notifier name and add notifier events as following:
> >
> > - extcon_{register|unregister}_usb_notifier(struct extcon_dev *edev, struct notifier_block *nb);
> > - list of notifier events
> > #define EXTCON_USB_ID_L_VBUS_L0 /* ID low and VBUS low */
> > #define EXTCON_USB_ID_L_VBUS_H1 /* ID low and VBUS high */
> > #define EXTCON_USB_ID_H_VBUS_L2 /* ID high and VBUS low */
> > #define EXTCON_USB_ID_H_VBUS_H3 /* ID high and VBUS high */
>
> I am still confused, why we mix ID and VBUS events into one?
> Those are two lines and they are not necessarily handled by
> the same extcon_dev.
Yes, from consumer side, we only need one element per time, eg vbus
or id.
--
Best Regards,
Peter Chen
next prev parent reply other threads:[~2015-04-16 8:02 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 13:13 [PATCH v3 0/4] extcon: usb-gpio: fixes and improvements Robert Baldyga
2015-04-02 13:13 ` [PATCH v3 1/4] extcon: usb-gpio: register extcon device before IRQ registration Robert Baldyga
2015-04-03 0:09 ` Chanwoo Choi
2015-04-02 13:13 ` [PATCH v3 2/4] extcon: usb-gpio: add support for VBUS detection Robert Baldyga
2015-04-02 14:02 ` Roger Quadros
2015-04-09 2:12 ` Chanwoo Choi
2015-04-09 7:57 ` Robert Baldyga
2015-04-09 9:07 ` Chanwoo Choi
2015-04-09 9:24 ` Robert Baldyga
2015-04-09 9:59 ` Roger Quadros
2015-04-09 10:18 ` Robert Baldyga
2015-04-10 7:39 ` Chanwoo Choi
2015-04-10 7:17 ` Chanwoo Choi
2015-04-10 7:45 ` Robert Baldyga
2015-04-10 8:10 ` Chanwoo Choi
2015-04-10 8:46 ` Robert Baldyga
2015-04-10 9:18 ` Chanwoo Choi
2015-04-10 9:42 ` Robert Baldyga
2015-04-14 10:01 ` Roger Quadros
2015-04-14 10:02 ` Roger Quadros
2015-04-14 10:31 ` Chanwoo Choi
2015-04-14 10:38 ` Roger Quadros
2015-04-14 11:29 ` Chanwoo Choi
2015-04-15 3:27 ` Peter Chen
2015-04-15 7:50 ` Roger Quadros
2015-04-15 9:26 ` Chanwoo Choi
2015-04-16 1:59 ` Peter Chen
2015-04-16 7:00 ` Chanwoo Choi
2015-04-16 7:13 ` Ivan T. Ivanov
2015-04-16 7:59 ` Chanwoo Choi
2015-04-16 8:01 ` Peter Chen
2015-04-16 8:26 ` Chanwoo Choi
2015-04-30 7:32 ` Roger Quadros
2015-04-30 7:55 ` Chanwoo Choi
2015-04-30 8:04 ` Roger Quadros
2015-04-16 7:59 ` Peter Chen [this message]
2015-04-16 7:16 ` Roger Quadros
2015-04-02 13:13 ` [PATCH v3 3/4] extcon: usb-gpio: make debounce value configurable in devicetree Robert Baldyga
2015-04-02 13:13 ` [PATCH v3 4/4] Documentation: extcon: usb-gpio: update usb-gpio binding description Robert Baldyga
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=20150416075957.GB1709@shlinux2 \
--to=peter.chen@freescale.com \
--cc=balbi@ti.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=iivanov@mm-sol.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=myungjoo.ham@samsung.com \
--cc=r.baldyga@samsung.com \
--cc=rogerq@ti.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).