lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1262885241.27762.1.camel@dax.rpnet.com>
Date:	Thu, 07 Jan 2010 17:27:21 +0000
From:	Richard Purdie <rpurdie@...ys.net>
To:	Arnd Hannemann <hannemann@...s.rwth-aachen.de>
Cc:	Daniel Mack <daniel@...aq.de>,
	Arnd Hannemann <Arnd.Hannemann@...s.rwth-aachen.de>,
	LKML <linux-kernel@...r.kernel.org>,
	"linux-geode@...ts.infradead.org" <linux-geode@...ts.infradead.org>
Subject: Re: 2.6.33-rc3 regression: leds_alix2: can't allocate I/O for GPIO

On Thu, 2010-01-07 at 15:00 +0100, Arnd Hannemann wrote:
> Daniel Mack schrieb:
> > On Thu, Jan 07, 2010 at 01:11:31PM +0100, Arnd Hannemann wrote:
> >> Arnd Hannemann schrieb:
> >> Oh, maybe using cs5535_gpio AND leds_alix2 together was never supposed to work?
> > 
> > That is the problem indeed. The problem is that three of these GPIOs are
> > connected to LEDs, so if both drivers are enabled, they will both alter
> > the same GPIOs. Hmm, don't know how to handle this. Maybe the LED driver
> > should use the GPIO interface and that's it?
> 
> I'm not sure that this configuration needs to be supported at all,
> so disallowing that both drivers are configured via Kconfig could be a simple solution.

Agreed, Kconfig dependencies for this until the code is improved look
like the best option. Does someone want to send me a patch?

Cheers,

Richard

-- 
Richard Purdie
Intel Open Source Technology Centre

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ