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]
Date:	Sun, 18 Mar 2012 17:54:06 -0700
From:	Guenter Roeck <guenter.roeck@...csson.com>
To:	Linus Walleij <linus.walleij@...aro.org>
CC:	Diego Elio Pettenò <flameeyes@...meeyes.eu>,
	Grant Likely <grant.likely@...retlab.ca>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Linus Walleij <linus.walleij@...ricsson.com>,
	Denis Turischev <denis@...pulab.co.il>
Subject: Re: [PATCH] gpio: add support for ITE IT87xx Super I/O GPIO.

On Sun, Mar 18, 2012 at 07:14:45PM -0400, Linus Walleij wrote:
> On Sat, Mar 17, 2012 at 7:53 PM, Diego Elio Pettenò
> <flameeyes@...meeyes.eu> wrote:
> 
> > Another reason to have a MFD driver would be to allow tweaking the few
> > more knobs that (at least IT8728F) expose, such as the ability to switch
> > a few pre-defined inputs and outputs to GPIO instead, and so on...
> 
> Hm that sounds an awful lot like pin multiplexing. Is that the case?
> 
Depending on the chip configuration, a physical pin may be a GPIO pin, or a UART pin,
or a fan control pin, or a FD pin, or something else. This does not apply to all pins,
but to many of the GPIO pins.

On IT8721F (which is supposedly mostly compatible to IT8728F), only four of the 87 GPIO pins
are GPIO-only (unless I miscounted ;). All others have at least two different functions.

Not sure if it is a good idea to re-configure any of those pins. I would assume
there is a reason if a given set of pins is configured as UART, for example.

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