From: Roger Quadros <rogerq@ti.com>
To: Stephen Boyd <stephen.boyd@linaro.org>,
Chanwoo Choi <cw00.choi@samsung.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] extcon: Add support for qcom SPMI PMIC USB id detection hardware
Date: Wed, 29 Jun 2016 09:10:57 +0300 [thread overview]
Message-ID: <57736671.6090800@ti.com> (raw)
In-Reply-To: <146715129359.31418.3271966598208551482@sboyd-linaro>
On 29/06/16 01:01, Stephen Boyd wrote:
> Quoting Roger Quadros (2016-06-28 02:13:57)
>> On 28/06/16 11:47, Stephen Boyd wrote:
>>>
>>> Sorry I must have confused you. There are two modules in the PMIC that
>>> are doing detection here. The charger module is detecting the VBUS event
>>> and this misc module is detecting the ID pin. I'm not sure why they're
>>> two different blocks, but it is what it is in the hardware.
>>>
>> OK. Can the MISC block do anything else other than USB ID?
>
> Yes.
>
>> Does the USB ID interrupt come on a different line than the charger interrupt?
>
> Yes.
>
OK. Is it better to have this driver somewhere in drivers/mfd or drivers/misc if the
other function doesn't need/use extcon?
>>
>> It would be more like MISC block interrupt than USB ID interrupt right?
>
> There are two interrupts going to two different hw blocks inside the
> PMIC.
>
cheers,
-roger
next prev parent reply other threads:[~2016-06-29 6:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 5:56 [PATCH] extcon: Add support for qcom SPMI PMIC USB id detection hardware Stephen Boyd
2016-06-26 11:20 ` Chanwoo Choi
2016-06-26 11:22 ` Chanwoo Choi
[not found] ` <146705470025.30684.13257433085055355379@sboyd-linaro>
2016-06-28 12:06 ` Chanwoo Choi
[not found] ` <CGME20160628215923epcas1p3f7942aca724bf2746c20319750184584@epcas1p3.samsung.com>
[not found] ` <146715115921.31418.2315766296233007937@sboyd-linaro>
2016-06-29 6:25 ` Chanwoo Choi
2016-06-29 18:48 ` Stephen Boyd
2016-06-30 0:35 ` Chanwoo Choi
2016-06-30 1:04 ` Stephen Boyd
2016-06-27 7:39 ` Roger Quadros
2016-06-27 19:30 ` Stephen Boyd
2016-06-28 6:36 ` Roger Quadros
2016-06-28 8:47 ` Stephen Boyd
2016-06-28 9:13 ` Roger Quadros
2016-06-28 22:01 ` Stephen Boyd
2016-06-29 6:10 ` Roger Quadros [this message]
2016-06-29 18:51 ` Stephen Boyd
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=57736671.6090800@ti.com \
--to=rogerq@ti.com \
--cc=cw00.choi@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stephen.boyd@linaro.org \
/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).