linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Dodge <bdodge09@gmail.com>
To: Daniel Thompson <daniel.thompson@linaro.org>
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: Tue, 2 Jul 2019 07:21:29 -0400	[thread overview]
Message-ID: <9ffed46f-c878-e415-cad0-cbe64efb9885@gmail.com> (raw)
In-Reply-To: <20190702092617.c4wn3dmg5orrquyj@holly.lan>


On 7/2/19 5:26 AM, Daniel Thompson wrote:
>> [PATCH 1/2] dt-bindings: backlight: fix vendor prefix for
>> ArcticSand arcxcnn driver bindings
> The "v2" is normally applied to the whole patchset (if you
> prepare the patchset using git format-patch then you can use
> the --subject-prefix argument for that).
Sorry and noted
>
> On Sun, Jun 30, 2019 at 08:28:14PM -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. This
>> patch adds "arctic" and retains "arc" (deprecated) bindings
>>
>> Signed-off-by: Brian Dodge <bdodge09@gmail.com>
>> ---
>>   .../bindings/leds/backlight/arcxcnn_bl.txt         | 31 +++++++++++++++-------
>>   1 file changed, 21 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..4d98394 100644
>> --- a/Documentation/devicetree/bindings/leds/backlight/arcxcnn_bl.txt
>> +++ b/Documentation/devicetree/bindings/leds/backlight/arcxcnn_bl.txt
>> @@ -1,8 +1,13 @@
>> -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"
>> +	"arc,arc2c0608" (deprecated)
> Nothing wrong with adding compatible strings for arc1 and arc3 but I
> would expect it to be mentioned in the description to reassure reviewers
> that the right depth of thought has been applied Something like "Also added
> compatible strings for other family members, all the existing optional
> properties work the same way for the new devices." (if you agree that it
> is true) is good to show you were paying proper attention!
>
> However this does perhaps verge a little towards nitpicking so maybe
> wait to see what the DT folks say. From my point of view:
> Acked-by: Daniel Thompson <daniel.thompson@linaro.org>
>
>
> Daniel.

Good point. I did actually think about this a bit. The *only* chip 
available at the time of the original driver was the arc2c0608 and that 
is the chip that is currently in use in the Samsung Chromebook Plus, and 
the only use I know of using the "arc" prefix. There will be no reason 
to ever support "arc,arc1.." or "arc,arc3..." in the bindings for past 
or future use.

The new two chips are just basically supported by this driver. There is 
more functionality to them which will be enabled in my next patch. I 
wanted to separate the move to "arctic" from the move to fully support 
the other chips for clarity (you guys are all rightly picky!) I did put 
the new chip bindings in the driver/bindings in this patch though so I 
could test this patch against the actual h/w instances: I have three 
boards, one with each chip type and each has a dtb with the "arctic,.." 
type binding onboard.

>> +
>> +- reg:		slave address
>>   
>>   Optional properties:
>>   - default-brightness:	brightness value on boot, value from: 0-4095
>> @@ -11,19 +16,25 @@ 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
>> +- 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
>> +- arc,led-config-0:	setting for register ILED_CONFIG_0 (deprecated)
>> +- arc,led-config-1:	setting for register ILED_CONFIG_1 (deprecated)
>> +- arc,dim-freq:		PWM mode frequence setting (bits [3:0] used) (deprecated)
>> +- arc,comp-config:	setting for register CONFIG_COMP (deprecated)
>> +- arc,filter-config:	setting for register FILTER_CONFIG (deprecated)
>> +- arc,trim-config:	setting for register IMAXTUNE (deprecated)
>>   
>>   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

  reply	other threads:[~2019-07-02 11:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2019-07-01  0:28 ` [PATCH 2/2] backlight: arcxcnn: add "arctic" vendor prefix Brian Dodge
2019-07-05  9:37   ` Pavel Machek
2019-07-05  9:37     ` Pavel Machek
2019-07-08 18:05   ` Dan Murphy
2019-07-08 18:05     ` Dan Murphy
2019-07-08 19:05     ` Brian Dodge
  -- strict thread matches above, loose matches on Subject: below --
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

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=9ffed46f-c878-e415-cad0-cbe64efb9885@gmail.com \
    --to=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).