From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] pinctrl: at91: add drive strength configuration
Date: Mon, 1 Sep 2014 10:27:22 +0200 [thread overview]
Message-ID: <CACRpkdazv59T6xOSAxJQ7t5KDb7wyG4HwFTM+q4KC67ZFrZ26g@mail.gmail.com> (raw)
In-Reply-To: <1408849926-9603-1-git-send-email-mark.roszko@gmail.com>
On Sun, Aug 24, 2014 at 5:12 AM, Marek Roszko <mark.roszko@gmail.com> wrote:
> The SAMA5 and SAM9x5 series both have drive strength options for the PIOs. This
> patch adds the ability to set one of three hardware options for drive strengths of low,
> medium or high for the each pin. The actual current output of the chip based on the setting
> is defined in the datasheets and varies per pins separate from banks and with supply voltage.
>
> This patch adds three new dt-bindings that allow setting the strength when configuring
> pins. By default, no change will be made to the drive strength of a pin from its reset value.
> Due to the difference between the register addresses of the SAMA5 and SAM9x5 series, a new
> sama5d3-pinctrl id was added.
>
> Signed-off-by: Marek Roszko <mark.roszko@gmail.com>
Waiting for feedback from AT91 maintainers...
Yours,
Linus Walleij
next prev parent reply other threads:[~2014-09-01 8:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-24 3:12 [PATCH v2 1/3] pinctrl: at91: add drive strength configuration Marek Roszko
2014-08-24 3:12 ` [PATCH v2 2/3] ARM: at91/dt: at91: use new pinctrl id for sama5 Marek Roszko
2014-09-05 7:34 ` Linus Walleij
2014-09-08 8:07 ` Nicolas Ferre
2014-09-18 15:32 ` Nicolas Ferre
2014-08-24 3:12 ` [PATCH v2 3/3] pinctrl: at91: update documentation for drive strength options and tweaks Marek Roszko
2014-09-05 7:36 ` Linus Walleij
2014-09-01 8:27 ` Linus Walleij [this message]
2014-09-01 8:28 ` [PATCH v2 1/3] pinctrl: at91: add drive strength configuration Jean-Christophe PLAGNIOL-VILLARD
2014-09-05 7:33 ` Linus Walleij
2014-09-05 7:56 ` Nicolas Ferre
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=CACRpkdazv59T6xOSAxJQ7t5KDb7wyG4HwFTM+q4KC67ZFrZ26g@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).