linux-kernel - Re: GPIO support for HTC Dream

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]

Message-ID: <d6200be20912142248n67cf020fw2bda313febe90fb9@mail.gmail.com>
Date:	Mon, 14 Dec 2009 22:48:01 -0800
From:	Arve Hjønnevåg <arve@...roid.com>
To:	Pavel Machek <pavel@....cz>
Cc:	H Hartley Sweeten <hartleys@...ionengravers.com>,
	Ryan Mallon <ryan@...ewatersys.com>,
	Daniel Walker <dwalker@...eaurora.org>,
	Iliyan Malchev <malchev@...gle.com>,
	Brian Swetland <swetland@...gle.com>,
	kernel list <linux-kernel@...r.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: GPIO support for HTC Dream

On Sun, Dec 13, 2009 at 10:45 PM, Pavel Machek <pavel@....cz> wrote:
>> > +int __init dream_init_gpio(void)
>> > +{
>> > +        int i;
>> > +
>> > +        for (i = 0; i < ARRAY_SIZE(msm_gpio_banks); i++)
>> > +                gpiochip_add(&msm_gpio_banks[i].chip);
>> > +
>> > +   return 0;
>> > +}
>>
>> Your original patch was initially writing the shadow values to the registers.
>> Do you still need to do that?
>
> It seems to boot this way :-). If writing the shadow values is not
> needed, lets try getting away without it...

I may boot this way, but unless you know that the bootloader
initialized all the registers to the same value, some outputs will be
in the wrong state until someone writes to a gpio in the same bank.

-- 
Arve Hjønnevåg
--
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/