linux-kernel - Re: [lm-sensors] [PATCH] hwmon: (max6650) Add support for gpiodef

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 16 Dec 2013 18:28:05 +0000
From:	Laszlo Papp <lpapp@....org>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Marcus Folkesson <marcus.folkesson@...il.com>, hjk@...sjkoch.de,
	LKML <linux-kernel@...r.kernel.org>, lm-sensors@...sensors.org
Subject: Re: [lm-sensors] [PATCH] hwmon: (max6650) Add support for gpiodef

On Mon, Dec 16, 2013 at 5:27 PM, Guenter Roeck <linux@...ck-us.net> wrote:
> On Mon, Dec 16, 2013 at 03:56:33PM +0000, Laszlo Papp wrote:
>> So, Mr. Roeck, how do you suggest to handle input or output port
>> configuration? Should it be coming from platform data, or should it be
>> more dynamic? I would say, it is usually static, but I do not know if
>> it is common to be dynamic. I am not a hardware designer.
>>
>
> Platform and/or devicetree.

Works for me. Should I apply the gpio and mfd drivers separately or in
one single patch?
--
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/