public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: linux-geode@lists.infradead.org, rpurdie@rpsys.net
Subject: 2.6.33-rc3 regression: leds_alix2: can't allocate I/O for GPIO
Date: Thu, 07 Jan 2010 11:26:37 +0100	[thread overview]
Message-ID: <4B45B6DD.4060903@nets.rwth-aachen.de> (raw)

Hi,

with 2.6.33-rc3 the LEDs are not working anymore on my Geode embedded board:
If I remember correctly this was working fine with 2.6.32, but certainly with 2.6.31

relevant dmesg output of 2.6.33-rc3:

[    0.709643] cs5535_gpio: base=0x6100 mask=0xb003c66 major=253

[    2.207947] leds_alix2: system is recognized as "PC Engines ALIX.2 v0.99h"
[    2.228678] leds_alix2: can't allocate I/O for GPIO


For reference dmesg of 2.6.31.3:

[    0.611953] cs5535_gpio: base=0x6100 mask=0xb003c66 major=253

[    2.379114] leds_alix2: system is recognized as "PC Engines ALIX.2"
[    2.399097] Registered led device: alix:1
[    2.411404] Registered led device: alix:2
[    2.423720] Registered led device: alix:3

Best regards,
Arnd

             reply	other threads:[~2010-01-07 10:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 10:26 Arnd Hannemann [this message]
2010-01-07 10:51 ` 2.6.33-rc3 regression: leds_alix2: can't allocate I/O for GPIO Richard Purdie
2010-01-07 11:58   ` Arnd Hannemann
2010-01-07 12:11     ` Arnd Hannemann
2010-01-07 12:46       ` Daniel Mack
2010-01-07 14:00         ` Arnd Hannemann
2010-01-07 14:20           ` Daniel Mack
2010-01-07 17:27           ` Richard Purdie
2010-01-08  3:08             ` Daniel Mack
2010-01-08  8:32               ` Arnd Hannemann
2010-01-10 12:27                 ` Daniel Mack
2010-01-16 18:52                   ` Daniel Mack
2010-01-18 13:59                   ` Richard Purdie

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=4B45B6DD.4060903@nets.rwth-aachen.de \
    --to=hannemann@nets.rwth-aachen.de \
    --cc=linux-geode@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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