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:	Tue, 06 Aug 2013 12:54:03 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Laxman Dewangan <ldewangan@...dia.com>
CC:	linus.walleij@...aro.org, ian.campbell@...rix.com,
	rob.herring@...xeda.com, pawel.moll@....com, mark.rutland@....com,
	rob@...dley.net, sameo@...ux.intel.com, lee.jones@...aro.org,
	grant.likely@...aro.org, broonie@...nel.org,
	devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, gg@...mlogic.co.uk, kishon@...com
Subject: Re: [PATCH V3 2/3] pinctrl: pinconf-generic: add generic APIs for
 mapping pinctrl node

On 08/06/2013 07:12 AM, Laxman Dewangan wrote:
> Add generic APIs to map the DT node and its sub node in pinconf generic
> driver. These APIs can be used from driver to parse the DT node who
> uses the pinconf generic APIs for defining their nodes.

> Changes from V2:
> - Rebased the pinctrl binding doc on top of Stephen's cleanup.
> - Rename properties "pinctrl-pins" and "pinctrl-function" to
>   "pins" and "function".

> diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt b/Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt

> +
> +The valid pin names and function are device/chip specific and it can be
> +found from the device/chip specific binding documents.

Oh, I ended up posting a V2 of my cleanup of that file with a wordier
version of that text added:-) Linus may want to drop those 3 lines when
applying this.
--
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