From: rah@settrans.net (Bob Ham)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm: sun4i: Add support for Pengpod 1000 tablet
Date: Mon, 4 Jun 2018 18:33:02 +0100 [thread overview]
Message-ID: <313a74ea-0be6-cff1-6b2f-06a4b0b7ba8d@settrans.net> (raw)
In-Reply-To: <20180604081302.hcn7j36gt6xeyquq@flea>
On 04/06/18 09:13, Maxime Ripard wrote:
> On Sat, Jun 02, 2018 at 05:03:13PM +0100, Bob Ham wrote:
>> + * This file is dual-licensed: you can use it either under the terms
>> + * of the GPL or the X11 license, at your option. Note that this dual
>> + * licensing only applies to this file, and not this project as a
>> + * whole.
>> + * The above copyright notice and this permission notice shall be
>> + * included in all copies or substantial portions of the Software.
> And this is redundant with the SPDX header.
The X11 license notice states explicitly that the notice has to be
included in the file. Wouldn't removing it be a violation of the license?
>> + brightness-levels = <0 10 20 30 40 50 60 70 80 90 100>;
>
> Each step should increase the perceived brightness by roughly 1/Nth, N
> being the number of steps. Usually PWM backlights don't work like that.
FYI, this was copied from another .dts file. All of the other
brightness-levels settings in sun{4,5,7}i .dts files follow similar
patterns:
sun4i-a10-dserve-dsrv9703c.dts: brightness-levels = <0 10
20 30 40 50 60 70 80 90 100>;
sun4i-a10-inet1.dts: brightness-levels = <0 10 20 30 40 50 60
70 80 90 100>;
sun4i-a10-pov-protab2-ips9.dts: brightness-levels = <0 10
20 30 40 50 60 70 80 90 100>;
sun5i-a13-empire-electronix-d709.dts: brightness-levels = <0 10
20 30 40 50 60 70 80 90 100>;
sun5i-a13-utoo-p66.dts: brightness-levels = <0 30 40 50 60 70 80
90 100>;
sun5i-gr8-evb.dts: brightness-levels = <0 10 20 30 40 50 60
70 80 90 100>;
sun7i-a20-wexler-tab7200.dts: brightness-levels = <0 10 20 30 40
50 60 70 80 90 100>;
I'll take the brightness-levels from sun8i-a83t-tbs-a711.dts which
follows a more appropriate pattern:
sun8i-a83t-tbs-a711.dts: brightness-levels = <0 1 2 4 8 16
32 64 128 255>;
Thanks,
Bob
--
Bob Ham <rah@settrans.net>
for (;;) { ++pancakes; }
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 2913 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180604/b46aec55/attachment.sig>
next prev parent reply other threads:[~2018-06-04 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 16:03 [PATCH v2] arm: sun4i: Add support for Pengpod 1000 tablet Bob Ham
2018-06-04 8:13 ` Maxime Ripard
2018-06-04 17:33 ` Bob Ham [this message]
2018-06-05 14:50 ` Maxime Ripard
2018-06-05 18:18 ` [linux-sunxi] " Bob Ham
2018-06-13 7:28 ` Hans de Goede
2018-06-13 9:53 ` Bob Ham
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=313a74ea-0be6-cff1-6b2f-06a4b0b7ba8d@settrans.net \
--to=rah@settrans.net \
--cc=linux-arm-kernel@lists.infradead.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