linux-kernel - Re: [PATCHv2] drivers: pinctrl: add a pin

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: <CAJuYYwRLoT2Xf8PcBPx_Nr1dYvki-aKVmkmsMy2r5z1wKu9r7Q@mail.gmail.com>
Date:	Fri, 4 Nov 2011 12:13:50 -0400
From:	Thomas Abraham <thomas.abraham@...aro.org>
To:	Chanho Park <chanho61.park@...sung.com>
Cc:	linus.walleij@...aro.org, swarren@...dia.com, Barry.Song@....com,
	Rongjun.Ying@....com, linux-kernel@...r.kernel.org,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Deepak Saxena <deepak.saxena@...aro.org>
Subject: Re: [PATCHv2] drivers: pinctrl: add a pin_base for sparse gpio-ranges

Hi Chanho Park,

On 28 October 2011 01:41, Chanho Park <chanho61.park@...sung.com> wrote:
> This patch enables mapping a base offset of gpio ranges with
> a pin offset even if does'nt matched. A "base" of pinctrl_gpio_range
> means a start offset of gpio. However, we cannot convert gpio to pin
> number for sparse gpio ranges just only using a gpio base offset.
> We can convert a gpio to real pin number using a new pin_base
> (which means a base pin offset of requested gpio range).
> If the pin_base is not specified explicitly, the controller sybsystem
> makes to equal with gpio's base offset. Now, a pinctrl subsystem passes
> the pin number to the driver instead a offset.

Just wanted to check with you if you have started the implementation
of pinctrl driver for Samsung platforms or do plan to start on it?

Thanks,
Thomas.

[...]
--
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/