From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] dt-bindings: pinctrl: k3-am6: Introduce pinmux definitions
Date: Fri, 9 Nov 2018 03:00:33 -0600 [thread overview]
Message-ID: <20181109090033.jx4buin3xuogdgfo@kahuna> (raw)
In-Reply-To: <1c400ca6-9257-0831-6909-fb00b00c4698@ti.com>
On 14:20-20181109, Vignesh R wrote:
> >> +++ b/include/dt-bindings/pinctrl/k3-am6.h
> >
> > Are we thinking of creating headers for every single SoC?
>
> We would need one file per SoC family (i.e atleast one for K3 family as
> a whole) as pinctrl register layout is significantly different than
Yes, I am aware of the same.
> other TI SoCs. I can rename the file to include/dt-bindings/pinctrl/k3.h
> to indicate its intended to be common for all K3 SoCs, if you prefer.
Yes, that would be the preference. There are two types of IO muxing IPs
(the equivalent of padconf from omap days) that I
am aware of. However these are all within the same 32bit definitions and
I know there has been significant effort spend by designers based on
software team feedbacks to maintain consistency as much as possible
within technological constraints.
So macros could be used to differentiate within the same header. The
deltas do exist, however they can be differentiated easily.
You should have access to the alternative solution, and even if you
cannot publish it, you should plan the header to scale easily when the
time is appropriate as a trivial additional patch.
For the rest.. Will wait for v2.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2018-11-09 9:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 11:26 [PATCH 0/2] AM654: Add pinmux support Vignesh R
2018-11-08 11:26 ` [PATCH 1/2] dt-bindings: pinctrl: k3-am6: Introduce pinmux definitions Vignesh R
2018-11-08 13:45 ` Nishanth Menon
2018-11-09 8:50 ` Vignesh R
2018-11-09 9:00 ` Nishanth Menon [this message]
2018-11-08 11:26 ` [PATCH 2/2] arm64: dts: ti: k3-am65: Add pinctrl regions Vignesh R
2018-11-08 13:47 ` Nishanth Menon
2018-11-08 15:13 ` Tony Lindgren
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=20181109090033.jx4buin3xuogdgfo@kahuna \
--to=nm@ti.com \
--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