From: Dan Murphy <dmurphy@ti.com>
To: Daniel Thompson <daniel.thompson@linaro.org>,
Brian Dodge <bdodge09@gmail.com>
Cc: devicetree@vger.kernel.org, jingoohan1@gmail.com,
dri-devel@lists.freedesktop.org, robh+dt@kernel.org,
jacek.anaszewski@gmail.com, pavel@ucw.cz, pbacon@psemi.com,
lee.jones@linaro.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: backlight: fix vendor prefix for ArcticSand arcxcnn driver bindings
Date: Wed, 26 Jun 2019 06:44:10 -0500 [thread overview]
Message-ID: <905cf517-0fae-cc52-d0ef-5b1dbe1c5864@ti.com> (raw)
In-Reply-To: <20190625085534.xf2ullyju3ewbgik@holly.lan>
Hello
On 6/25/19 3:55 AM, Daniel Thompson wrote:
> On Tue, Jun 25, 2019 at 12:05:28AM -0400, Brian Dodge wrote:
>> The vendor-prefixes.txt file properly refers to ArcticSand
>> as arctic but the driver bindings improperly abbreviated the
>> prefix to arc. This was a mistake in the original patch
>>
>> Signed-off-by: Brian Dodge <bdodge09@gmail.com>
>> ---
>> .../bindings/leds/backlight/arcxcnn_bl.txt | 24 +++++++++++++---------
>> 1 file changed, 14 insertions(+), 10 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/leds/backlight/arcxcnn_bl.txt b/Documentation/devicetree/bindings/leds/backlight/arcxcnn_bl.txt
>> index 230abde..9cf4c44 100644
>> --- a/Documentation/devicetree/bindings/leds/backlight/arcxcnn_bl.txt
>> +++ b/Documentation/devicetree/bindings/leds/backlight/arcxcnn_bl.txt
>> @@ -1,8 +1,12 @@
>> -Binding for ArcticSand arc2c0608 LED driver
>> +Binding for ArcticSand arc family LED drivers
>>
>> Required properties:
>> -- compatible: should be "arc,arc2c0608"
>> -- reg: slave address
>> +- compatible: one of
>> + "arctic,arc1c0608"
>> + "arctic,arc2c0608"
>> + "arctic,arc3c0845"
> This is more a question for the DT folks than for Brian but...
>
> AFAICT this patch is fixing the binding for the ArcticSand devices to
> use the correct value from vendor-prefixes.yaml and has been previously
> discussed here:
> https://lkml.org/lkml/2018/9/25/726
>
> Currently this patch series just updates the DT bindings but the
> implementation also honours the old values (since there is a Chromebook
> in the wild that uses the current bindings).
>
> Hence I'm not clear whether the bindings should document the deprecated
> options too (e.g. make it easier to find the bindings doc with git grep
> and friends).
>
>
> Daniel.
>
>
>> +
>> +- reg: slave address
>>
>> Optional properties:
>> - default-brightness: brightness value on boot, value from: 0-4095
>> @@ -11,19 +15,19 @@ Optional properties:
>> - led-sources: List of enabled channels from 0 to 5.
>> See Documentation/devicetree/bindings/leds/common.txt
>>
>> -- arc,led-config-0: setting for register ILED_CONFIG_0
>> -- arc,led-config-1: setting for register ILED_CONFIG_1
>> -- arc,dim-freq: PWM mode frequence setting (bits [3:0] used)
>> -- arc,comp-config: setting for register CONFIG_COMP
>> -- arc,filter-config: setting for register FILTER_CONFIG
>> -- arc,trim-config: setting for register IMAXTUNE
IMO I would prefer to keep these and mark them as deprecated since the
driver will still
honor these properties.
Maybe in a Optional Deprecated Properties section in the DT binding.
Dan
>> +- arctic,led-config-0: setting for register ILED_CONFIG_0
>> +- arctic,led-config-1: setting for register ILED_CONFIG_1
>> +- arctic,dim-freq: PWM mode frequence setting (bits [3:0] used)
>> +- arctic,comp-config: setting for register CONFIG_COMP
>> +- arctic,filter-config: setting for register FILTER_CONFIG
>> +- arctic,trim-config: setting for register IMAXTUNE
>>
>> Note: Optional properties not specified will default to values in IC EPROM
>>
>> Example:
>>
>> arc2c0608@30 {
>> - compatible = "arc,arc2c0608";
>> + compatible = "arctic,arc2c0608";
>> reg = <0x30>;
>> default-brightness = <500>;
>> label = "lcd-backlight";
>> --
>> 2.7.4
>>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-06-26 11:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 4:05 [PATCH 0/2] fix vendor prefix for arcxcnn driver and bindings Brian Dodge
2019-06-25 4:05 ` [PATCH 1/2] dt-bindings: backlight: fix vendor prefix for ArcticSand arcxcnn driver bindings Brian Dodge
2019-06-25 8:55 ` Daniel Thompson
2019-06-25 11:44 ` Brian Dodge
2019-06-26 10:56 ` Daniel Thompson
2019-06-26 13:22 ` Lee Jones
2019-06-26 14:43 ` Rob Herring
2019-06-26 14:56 ` Pavel Machek
2019-06-26 14:59 ` Brian Dodge
2019-06-26 15:09 ` Dan Murphy
2019-06-26 11:44 ` Dan Murphy [this message]
2019-06-25 4:05 ` [PATCH 2/2] backlight: arcxcnn: add "arctic" vendor prefix Brian Dodge
2019-06-26 10:53 ` Daniel Thompson
2019-06-26 11:42 ` Dan Murphy
2019-06-26 11:45 ` Dan Murphy
2019-07-01 0:28 [PATCH v2 0/2] fix vendor prefix for arcxcnn driver and bindings Brian Dodge
2019-07-01 0:28 ` [PATCH 1/2] dt-bindings: backlight: fix vendor prefix for ArcticSand arcxcnn driver bindings Brian Dodge
2019-07-02 9:26 ` Daniel Thompson
2019-07-02 11:21 ` Brian Dodge
2019-07-02 13:11 ` Daniel Thompson
2019-07-08 18:02 ` Dan Murphy
2019-07-08 18:02 ` Dan Murphy
2019-07-09 17:48 ` Brian Dodge
2019-07-09 18:01 ` Dan Murphy
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=905cf517-0fae-cc52-d0ef-5b1dbe1c5864@ti.com \
--to=dmurphy@ti.com \
--cc=bdodge09@gmail.com \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.anaszewski@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=pbacon@psemi.com \
--cc=robh+dt@kernel.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).