linux-kernel - Re: [PATCH 1/5] mmc: pwrseq: Document that simple sequence support more than one GPIO

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: <54C90FD7.40601@collabora.co.uk>
Date:	Wed, 28 Jan 2015 17:35:35 +0100
From:	Javier Martinez Canillas <javier.martinez@...labora.co.uk>
To:	Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
	Ulf Hansson <ulf.hansson@...aro.org>
CC:	devicetree@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
	linux-mmc@...r.kernel.org, Doug Anderson <dianders@...omium.org>,
	linux-kernel@...r.kernel.org, Kukjin Kim <kgene@...nel.org>,
	Olof Johansson <olof@...om.net>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/5] mmc: pwrseq: Document that simple sequence support
 more than one GPIO

Srinivas,

On 01/28/2015 05:34 PM, Srinivas Kandagatla wrote:
>> -- reset-gpios : contains a GPIO specifier. The reset GPIO is asserted at
>> -	initialization and prior we start the power up procedure of the card. It
>> -	will be de-asserted right after the power has been provided to the card.
>> +- reset-gpios : contains a list of GPIO specifiers. The reset GPIOs are asserted
>> +	at initialization and prior we start the power up procedure of the card.
>> +	Will be de-asserted right after the power has been provided to the card.
> Makes sense if you add "They" before last sentence.

Thanks, I'll change it.

Best regards,
Javier

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