linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chanwoo Choi <cwchoi00@gmail.com>
To: Stephen Boyd <stephen.boyd@linaro.org>
Cc: linux-arm-msm@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH] extcon: Add support for qcom SPMI PMIC USB id detection hardware
Date: Tue, 28 Jun 2016 21:06:48 +0900	[thread overview]
Message-ID: <CAGTfZH3ZhZ2gQcOSuAByZWD59E3Bro1aayr2JsM2W+mYa2LQTQ@mail.gmail.com> (raw)
In-Reply-To: <146705470025.30684.13257433085055355379@sboyd-linaro>

2016-06-28 4:11 GMT+09:00 Stephen Boyd <stephen.boyd@linaro.org>:
> Quoting Chanwoo Choi (2016-06-26 04:20:43)
>> 2016-06-26 14:56 GMT+09:00 Stephen Boyd <stephen.boyd@linaro.org>:
>> > +PROPERTIES
>> > +
>> > +- compatible:
>> > +    Usage: required
>> > +    Value type: <string>
>> > +    Definition: Should contain "qcom,pm8941-misc";
>> > +
>> > +- reg:
>> > +    Usage: required
>> > +    Value type: <u32>
>> > +    Definition: Should contain the offset to the misc address space
>>
>> 'reg' property is used on extcon-qcom-spmi-misc.c?
>> I think that you don't need to include this property.
>
> No it isn't used in the driver right now, but there is a register offset
> for this module and there are registers that can be read/written in this
> module. I'd like to keep it as required so we can easily read the
> registers in the future if needed.

OK.
But, If you want to remain the reg property, you should add the code to get
the register offset by using OF functions. This patch don't include the OF
function to handle it.

[snip]

  parent reply	other threads:[~2016-06-28 12:07 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 [this message]
     [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
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=CAGTfZH3ZhZ2gQcOSuAByZWD59E3Bro1aayr2JsM2W+mYa2LQTQ@mail.gmail.com \
    --to=cwchoi00@gmail.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=rogerq@ti.com \
    --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).