From: Rob Herring <robh@kernel.org>
Cc: Tero Kristo <t-kristo@ti.com>, Nishanth Menon <nm@ti.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Vignesh R <vigneshr@ti.com>,
linux-omap@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH v2 1/4] dt-bindings: pinctrl: k3: Introduce pinmux definitions
Date: Sat, 17 Nov 2018 09:43:28 -0600 [thread overview]
Message-ID: <20181117154328.GA4095@bogus> (raw)
In-Reply-To: <20181113060111.16374-2-vigneshr@ti.com>
On Tue, 13 Nov 2018 11:31:08 +0530, Vignesh R wrote:
> The dt-bindings header for TI K3 AM6 SoCs define a set of macros for
> defining pinmux configs in human readable form, instead of raw-coded
> hex values.
>
> Signed-off-by: Vignesh R <vigneshr@ti.com>
> ---
> MAINTAINERS | 1 +
> include/dt-bindings/pinctrl/k3.h | 35 ++++++++++++++++++++++++++++++++
> 2 files changed, 36 insertions(+)
> create mode 100644 include/dt-bindings/pinctrl/k3.h
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-11-17 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 6:01 [PATCH v2 0/4] AM654: Add pinmux support Vignesh R
2018-11-13 6:01 ` [PATCH v2 1/4] dt-bindings: pinctrl: k3: Introduce pinmux definitions Vignesh R
2018-11-17 12:27 ` Linus Walleij
2018-11-17 15:43 ` Rob Herring [this message]
2018-11-17 16:05 ` Nishanth Menon
2018-11-19 7:19 ` Tero Kristo
2018-11-20 10:09 ` Vignesh R
2018-11-20 10:37 ` Tero Kristo
2018-11-20 10:44 ` Vignesh R
2018-11-23 10:21 ` Tero Kristo
2018-11-23 15:07 ` Nishanth Menon
2018-11-17 16:08 ` Tony Lindgren
2018-11-13 6:01 ` [PATCH v2 2/4] arm64: dts: ti: k3-am65: Add pinctrl regions Vignesh R
2018-11-13 6:01 ` [PATCH v2 3/4] arm64: dts: ti: am654-base-board: Add pinmux for main uart0 Vignesh R
2018-11-13 6:01 ` [PATCH v2 4/4] arm64: dts: ti: k3-am654-base-board: Add I2C nodes Vignesh R
2018-11-17 16:09 ` Nishanth Menon
2018-11-17 16:10 ` [PATCH v2 0/4] AM654: Add pinmux support Nishanth Menon
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=20181117154328.GA4095@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
--cc=vigneshr@ti.com \
/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).