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  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:	Fri, 24 Oct 2014 13:53:28 +0200
From:	Linus Walleij <>
To:	Beniamino Galvani <>
Cc:	"" 
	"" <>,
	Arnd Bergmann <>,
	Russell King <>,
	Carlo Caione <>,
	"" <>,
	Rob Herring <>,
	Pawel Moll <>,
	Mark Rutland <>,
	Ian Campbell <>,
	Kumar Gala <>,
	Jerry Cao <>,
	Victor Wan <>
Subject: Re: [PATCH 2/3] pinctrl: meson: add device tree bindings documentation

On Tue, Oct 7, 2014 at 11:32 PM, Beniamino Galvani <> wrote:

> Add device tree bindings documentation for Amlogic Meson pinmux and
> GPIO controller.
> Signed-off-by: Beniamino Galvani <>
> +Required properties for gpio sub-nodes:
> + - reg: should contain address and size for mux, pull-enable, pull and
> +   gpio register sets
> + - reg-names: an array of strings describing the "reg" entries. Must
> +   contain "mux", "pull" and "gpio". "pull-enable" is optional and
> +   when it is missing the "pull" registers are used instead

So it seems segmenting the registers is done to sort of control the
hardware versioning.

I think it's better to use the compatible string to indicate different
versions of the hardware and then have just have one big
regs to cover all registers.

> +Valid gpio sub-nodes name are:
> + - "banks" for the standard banks
> + - "ao-bank" for the AO bank which belong to the special always-on
> +   power domain

I think it's unnecessary to split up banks, the compatible property
should be enough to know how many banks this controller has
and where they are located in relation to the base offset.

> +Required properties for configuration nodes:
> + - pins: the name of a pin group. The list of all available groups can
> +   be found in driver sources.
> + - function: the name of a function to activate for the specified set
> +   of groups. The list of all available functions can be found in
> +   driver sources.

This is interesting. I have established that for controllers mapping
functions to groups we use
"function" and "groups".

So for per-pin configuration, "function" and "pins" would be

Linus Walleij
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists