From: nicolas.ferre@atmel•com (Nicolas Ferre)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: at91/at91-pinctrl documentation: add missing sam9x5 compatible string
Date: Tue, 27 Aug 2013 16:57:28 +0200 [thread overview]
Message-ID: <521CBE58.9060402@atmel.com> (raw)
In-Reply-To: <1377609965-22154-1-git-send-email-b.brezillon@overkiz.com>
On 27/08/2013 15:26, Boris BREZILLON :
> Add missing "atmel,at91sam9x5-pinctrl" compatible string to the
> documentation.
>
> Signed-off-by: Boris BREZILLON <b.brezillon@overkiz•com>
Acked-by: Nicolas Ferre <nicolas.ferre@atmel•com>
> ---
> .../bindings/pinctrl/atmel,at91-pinctrl.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt
> index 648d60e..cf7c7bc 100644
> --- a/Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt
> +++ b/Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt
> @@ -18,7 +18,7 @@ mode) this pin can work on and the 'config' configures various pad settings
> such as pull-up, multi drive, etc.
>
> Required properties for iomux controller:
> -- compatible: "atmel,at91rm9200-pinctrl"
> +- compatible: "atmel,at91rm9200-pinctrl" or "atmel,at91sam9x5-pinctrl"
> - atmel,mux-mask: array of mask (periph per bank) to describe if a pin can be
> configured in this periph mode. All the periph and bank need to be describe.
>
>
--
Nicolas Ferre
next prev parent reply other threads:[~2013-08-27 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 13:26 [PATCH] ARM: at91/at91-pinctrl documentation: add missing sam9x5 compatible string Boris BREZILLON
2013-08-27 14:57 ` Nicolas Ferre [this message]
2013-09-19 14:05 ` Nicolas Ferre
2013-09-27 12:17 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=521CBE58.9060402@atmel.com \
--to=nicolas.ferre@atmel$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox