Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1241993 > unrolled thread
| Started by | wangfei <w.f@huawei.com> |
|---|---|
| First post | 2015-10-08 08:40 +0200 |
| Last post | 2015-10-12 19:00 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH 1/8] dt-bindings: pmic: Document Hi655x pmic driver wangfei <w.f@huawei.com> - 2015-10-08 08:40 +0200
Re: [PATCH 1/8] dt-bindings: pmic: Document Hi655x pmic driver Mark Brown <broonie@kernel.org> - 2015-10-12 19:00 +0200
| From | wangfei <w.f@huawei.com> |
|---|---|
| Date | 2015-10-08 08:40 +0200 |
| Subject | Re: [PATCH 1/8] dt-bindings: pmic: Document Hi655x pmic driver |
| Message-ID | <qhd1T-3Uf-5@gated-at.bofh.it> |
On 2015/10/1 1:39, Mark Brown wrote:
> On Wed, Sep 30, 2015 at 07:05:04PM +0800, Fei Wang wrote:
>
>> +Hisilicon hi655x Power Management Integrated Circuit (PMIC)
>> +
>> +hi655x consists of a large and varied group of sub-devices:
>> +
>> +Device Supply Names Description
>> +------ ------------ -----------
>> +hi655x-powerkey : : Powerkey
>> +hi655x-regulator-pmic : : Regulators
>> +hi655x-usbvbus : : USB plug detection
>> +hi655x-pmu-rtc : : RTC
>> +hi655x-coul : : Coulomb
>
> ...counter?
>
> There's no documentation of the bindings for any of the above devices or
> how things are structured, you need to provide binding documentation
> which is understandable standalone. None of the properties are
> documented, nor is the set of regulators supported or how this is
> structured.
OK,i will add them.
>
>> + coul: coul@1 {
>> + compatible = "hisilicon,hi655x-coul";
>> + interrupt-parent = <&pmic>;
>> + interrupts = <24 0>, <25 0>, <26 0>, <27 0>;
>> + interrupt-names = "cl_int_i", "cl_out_i", "cl_in_i", "vbat_int_i";
>> + battery_product_index = <0>;
>
> For example, the "battery_product_index" property here is undocumented.
now on hikey, we only enable hi655x-regulator-pmic function, and regulator is child node of pmic.do i need to document regulator dt-binding in this file or create a new regulator dt-binding file?
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[toc] | [next] | [standalone]
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Date | 2015-10-12 19:00 +0200 |
| Message-ID | <qiOC7-4Us-31@gated-at.bofh.it> |
| In reply to | #1241993 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Oct 08, 2015 at 02:33:06PM +0800, wangfei wrote:
> On 2015/10/1 1:39, Mark Brown wrote:
> > On Wed, Sep 30, 2015 at 07:05:04PM +0800, Fei Wang wrote:
Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns. Doing this makes your messages much
easier to read and reply to.
> >> + coul: coul@1 {
> >> + compatible = "hisilicon,hi655x-coul";
> >> + interrupt-parent = <&pmic>;
> >> + interrupts = <24 0>, <25 0>, <26 0>, <27 0>;
> >> + interrupt-names = "cl_int_i", "cl_out_i", "cl_in_i", "vbat_int_i";
> >> + battery_product_index = <0>;
> > For example, the "battery_product_index" property here is undocumented.
> now on hikey, we only enable hi655x-regulator-pmic function, and
> regulator is child node of pmic.do i need to document regulator
> dt-binding in this file or create a new regulator dt-binding file?
Either is possible, though it is common to split the DT documentation
into per subsystem files for ease of reference and to avoid cross tree
merge issues.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web