From: k.kozlowski@samsung•com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/6] ARM: s3cxxxx: Use PWM lookup table
Date: Tue, 06 Oct 2015 09:28:50 +0900 [thread overview]
Message-ID: <561315C2.9040506@samsung.com> (raw)
In-Reply-To: <1444049237-29878-1-git-send-email-thierry.reding@gmail.com>
On 05.10.2015 21:47, Thierry Reding wrote:
> Back when the PWM framework was introduced the concept of PWM lookup
> tables was added to allow board code to register a table of PWM devices
> and their association with consumers. The goal is to allow drivers to
> use a unified method to request PWM devices. At the same time, since no
> boards were exposing these tables, fallback code was kept in drivers to
> allow old code to remain functional. In order to get rid of the legacy
> fallback code, legacy users need to be updated to register PWM lookup
> tables.
>
> This series converts all s3c24xx and s3c64xx boards that hook up a pwm-
> backlight device to use the new PWM lookup tables. All patches have been
> compile-tested, but I don't have access to any of these boards, so I
> couldn't verify that they really work.
Unfortunately I can't verify them neither. I don't have these boards. In
that case I would prefer approach "if it ain't broken, don't touch
it"... unless someone tests the patches of course.
Anyone can provide tested-by tag?
Best regards,
Krzysztof
>
> Thierry
>
> Thierry Reding (6):
> ARM: s3c24xx: h1940: Use PWM lookup table
> ARM: s3c24xx: rx1950: Use PWM lookup table
> ARM: s3c64xx: smdk6410: Use PWM lookup table
> ARM: s3c64xx: crag6410: Use PWM lookup table
> ARM: s3c64xx: hmt: Use PWM lookup table
> ARM: s3c64xx: smartq: Use PWM lookup table
>
> arch/arm/mach-s3c24xx/mach-h1940.c | 10 +++++++---
> arch/arm/mach-s3c24xx/mach-rx1950.c | 8 ++++++--
> arch/arm/mach-s3c64xx/dev-backlight.c | 4 ----
> arch/arm/mach-s3c64xx/mach-crag6410.c | 9 +++++++--
> arch/arm/mach-s3c64xx/mach-hmt.c | 9 +++++++--
> arch/arm/mach-s3c64xx/mach-smartq.c | 9 +++++++--
> arch/arm/mach-s3c64xx/mach-smdk6410.c | 8 +++++++-
> 7 files changed, 41 insertions(+), 16 deletions(-)
>
next prev parent reply other threads:[~2015-10-06 0:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 12:47 [PATCH 0/6] ARM: s3cxxxx: Use PWM lookup table Thierry Reding
2015-10-05 12:47 ` [PATCH 1/6] ARM: s3c24xx: h1940: " Thierry Reding
2015-10-07 1:32 ` Krzysztof Kozlowski
2015-10-05 12:47 ` [PATCH 2/6] ARM: s3c24xx: rx1950: " Thierry Reding
2015-10-07 1:35 ` Krzysztof Kozlowski
2015-10-07 15:31 ` Thierry Reding
2015-10-08 1:00 ` Krzysztof Kozlowski
2015-10-05 12:47 ` [PATCH 3/6] ARM: s3c64xx: smdk6410: " Thierry Reding
2015-10-08 1:00 ` Krzysztof Kozlowski
2015-10-05 12:47 ` [PATCH 4/6] ARM: s3c64xx: crag6410: " Thierry Reding
2015-10-07 1:36 ` Krzysztof Kozlowski
2015-10-05 12:47 ` [PATCH 5/6] ARM: s3c64xx: hmt: " Thierry Reding
2015-10-07 1:37 ` Krzysztof Kozlowski
2015-10-07 15:37 ` Thierry Reding
2015-10-08 1:01 ` Krzysztof Kozlowski
2015-10-05 12:47 ` [PATCH 6/6] ARM: s3c64xx: smartq: " Thierry Reding
2015-10-08 1:02 ` Krzysztof Kozlowski
2015-10-06 0:28 ` Krzysztof Kozlowski [this message]
2015-10-06 8:43 ` [PATCH 0/6] ARM: s3cxxxx: " Thierry Reding
2015-10-06 12:27 ` Krzysztof Kozlowski
2015-10-12 19:17 ` Kukjin Kim
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=561315C2.9040506@samsung.com \
--to=k.kozlowski@samsung$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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