public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: lost.distance@yahoo.com (Paul Parsons)
To: linux-arm-kernel@lists.infradead.org
Subject: PXA PWM possible regression after 3.5: backlight remains off after resume
Date: Wed, 26 Sep 2012 03:02:58 +0100	[thread overview]
Message-ID: <50626252.3050405@yahoo.com> (raw)
In-Reply-To: <87ehlpzy50.fsf@free.fr>

On 25/09/12 20:43, Robert Jarzmik wrote:
> Paul Parsons <lost.distance@yahoo.com> writes:
>
>> The same failure is also present in 3.6-rc1.
>>
>> Just to be clear, are you saying that drivers/pwm/pwm-pxa.c should
>> include suspend/resume handlers like in drivers/pwm/pwm-samsung.c ?
>>
>> Agreed that it is possible that recent changes exposed a latent bug
>> somewhere, and that turning the backlight on after resume should never
>> have worked.
>
> Hi Paul,
>
> I checked on the mioa701 board (see [1]).
> On my board, the backlight if fully driven by PXA PWM0, and the suspend/resume
> is working perfectly.
>
> So I don't thing anything is needed for suspend/resume wrt PWM (empirically).

You're right. I belatedly reached the same conclusion after I noticed
that only the pwm-samsung driver included any suspend/resume handlers:
the other drivers can't all be broken!

Fortunately I have just identified the problem: the PXA27X PWM device
numbering scheme has changed, breaking the hx4700 platform and probably
other PXA27X platforms which use PWM1 or PWM2.

Regards,
Paul

      reply	other threads:[~2012-09-26  2:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-23 15:20 PXA PWM possible regression after 3.5: backlight remains off after resume Paul Parsons
2012-09-23 17:22 ` Thierry Reding
2012-09-23 18:13   ` Paul Parsons
2012-09-25 19:43     ` Robert Jarzmik
2012-09-26  2:02       ` Paul Parsons [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=50626252.3050405@yahoo.com \
    --to=lost.distance@yahoo.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