From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: pxa: raumfeld: adapt to upcoming hardware change
Date: Thu, 26 May 2011 20:24:13 +0200 [thread overview]
Message-ID: <BANLkTiky3faK1pzaC+C9g34gTCd+CvwMmQ@mail.gmail.com> (raw)
In-Reply-To: <1306323453-6371-1-git-send-email-zonque@gmail.com>
Hi Eric,
In case there aren't any objections, can you queue up these three patches?
It doesn't matter whether they make it into the next release, I just
to make sure they're not forgotten.
Thanks,
Daniel
On Wed, May 25, 2011 at 1:37 PM, Daniel Mack <zonque@gmail.com> wrote:
> From: Sven Neumann <s.neumann@raumfeld.com>
>
> The backlight control is going to change back to PWM in the
> upcoming Raumfeld Controller hardware revision.
>
> Signed-off-by: Sven Neumann <s.neumann@raumfeld.com>
> Acked-by: Daniel Mack <zonque@gmail.com>
> ---
> ?arch/arm/mach-pxa/raumfeld.c | ? 11 ++++++-----
> ?1 files changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm/mach-pxa/raumfeld.c b/arch/arm/mach-pxa/raumfeld.c
> index 15bca98..8b2ace5 100644
> --- a/arch/arm/mach-pxa/raumfeld.c
> +++ b/arch/arm/mach-pxa/raumfeld.c
> @@ -599,14 +599,15 @@ static void __init raumfeld_lcd_init(void)
>
> ? ? ? ?pxa_set_fb_info(NULL, &raumfeld_sharp_lcd_info);
>
> - ? ? ? /* Earlier devices had the backlight regulator controlled
> - ? ? ? ?* via PWM, later versions use another controller for that */
> - ? ? ? if ((system_rev & 0xff) < 2) {
> + ? ? ? /* Hardware revision 2 has the backlight regulator controlled
> + ? ? ? ?* by an LT3593, earlier and later devices use PWM for that. */
> + ? ? ? if ((system_rev & 0xff) == 2) {
> + ? ? ? ? ? ? ? platform_device_register(&raumfeld_lt3593_device);
> + ? ? ? } else {
> ? ? ? ? ? ? ? ?mfp_cfg_t raumfeld_pwm_pin_config = GPIO17_PWM0_OUT;
> ? ? ? ? ? ? ? ?pxa3xx_mfp_config(&raumfeld_pwm_pin_config, 1);
> ? ? ? ? ? ? ? ?platform_device_register(&raumfeld_pwm_backlight_device);
> - ? ? ? } else
> - ? ? ? ? ? ? ? platform_device_register(&raumfeld_lt3593_device);
> + ? ? ? }
>
> ? ? ? ?ret = gpio_request(GPIO_TFT_VA_EN, "display VA enable");
> ? ? ? ?if (ret < 0)
> --
> 1.7.5.1
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
prev parent reply other threads:[~2011-05-26 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 12:13 [PATCH 1/2] ARM: pxa: raumfeld: follow upcoming hardware change Daniel Mack
2011-05-24 12:13 ` [PATCH 2/2] ARM: pxa: raumfeld: fix device name for codec ak4104 Daniel Mack
2011-05-24 17:50 ` [PATCH 1/2] ARM: pxa: raumfeld: follow upcoming hardware change Russell King - ARM Linux
2011-05-25 11:11 ` Daniel Mack
2011-05-25 11:37 ` [PATCH 1/3] ARM: pxa: raumfeld: adapt to " Daniel Mack
2011-05-25 11:37 ` [PATCH 2/3] ARM: pxa: raumfeld: display initialisation fixes Daniel Mack
2011-05-25 11:37 ` [PATCH 3/3] ARM: pxa: raumfeld: fix device name for codec ak4104 Daniel Mack
2011-05-26 18:24 ` Daniel Mack [this message]
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=BANLkTiky3faK1pzaC+C9g34gTCd+CvwMmQ@mail.gmail.com \
--to=zonque@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).