linux-kernel - Re: awful kconfig help texts.

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: <5018F908.9090607@metafoo.de>
Date:	Wed, 01 Aug 2012 11:38:16 +0200
From:	Lars-Peter Clausen <lars@...afoo.de>
To:	Borislav Petkov <bp@...en8.de>,
	Thierry Reding <thierry.reding@...onic-design.de>,
	Steven Rostedt <rostedt@...dmis.org>,
	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: awful kconfig help texts.

On 08/01/2012 11:26 AM, Borislav Petkov wrote:
> On Wed, Aug 01, 2012 at 11:21:59AM +0200, Lars-Peter Clausen wrote:
>> One major reason for the new PWM framework is to be able to support
>> arch independent PWM drivers, like those for companion chips with PWM
>> capabilities. Restricting the config option to certain architectures
>> wouldn't work.
> 
> Right,
> 
> but when I enable the CONFIG_PWM option on x86, I don't see any drivers
> there. So the logical thing to do would be to hide that option on arches
> which don't have such chips.

You don't see any drivers, because the subsystem is still young and no such
arch independent drivers have been added yet, but they will get added in the
future. The arch independent companion or PWM expander chips usually
interface via I2S or SPI and I would consider it quite likely that you'll
also find them on some embedded X86 boards. If we add a arch restriction to
the config item now we'd quite likely have to remove it again in the next
release.

--
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/