linux-kernel - Re: [PATCH 1/1] of/documentation: Update s5m8767-regulator bindings document

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: <CAK9yfHzBPO1Yr7_qLtw3oZKVVtqDBK_Yj7_r=HrU+94pod+XVA@mail.gmail.com>
Date:	Tue, 25 Jun 2013 11:56:12 +0530
From:	Sachin Kamat <sachin.kamat@...aro.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	devicetree-discuss@...ts.ozlabs.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, grant.likely@...aro.org,
	rob@...dley.net, patches@...aro.org
Subject: Re: [PATCH 1/1] of/documentation: Update s5m8767-regulator bindings document

On 24 June 2013 20:55, Mark Brown <broonie@...nel.org> wrote:
> On Mon, Jun 24, 2013 at 03:06:57PM +0530, Sachin Kamat wrote:
>> s5m8767 regulator is used on Exynos platforms which use pin controller
>> to configure GPIOs. Update the example accordingly.
>
> This smells bad, why does a driver using GPIOs through the GPIO API see
> a change in the binding?

There is no change in the bindings, but just a correction in the
documentation to reflect the
implementation. Earlier when Samsung platforms did not have pinctrl
driver, legacy GPIO driver
was used which took those 5 parameters. Now since we are using
pinctrl, we need only 3 parameters.
The document was somehow not updated to reflect this change.

-- 
With warm regards,
Sachin
--
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/