From: codekipper@gmail.com (codekipper at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] pinctrl: sun4i: add spdif to pin description
Date: Wed, 12 Aug 2015 19:27:47 +0200 [thread overview]
Message-ID: <1439400468-1563-1-git-send-email-codekipper@gmail.com> (raw)
From: Marcus Cooper <codekipper@gmail.com>
The Allwinner A20(sun7i) SoC is pin to pin compatible with the Allwinner
A10(sun4i) SoC. However the user manual for the A10 devices does not make
any reference to the SPDIF whereas the pins, clocks, DMAs and Interrupts
are mentioned in the A20 documentation.
As products exist based on the A10 with an SPDIF transmitter and with the
code exposed then it is safe to assume that we can include SPDIF in the
pin definitions.
We can also look at the fex file of such a device where the SPDIF pin is
defined.
For example
https://github.com/linux-sunxi/sunxi-boards/blob/master/sys_config/a10/mele_a1000.fex#L822
shows
spdif_dout = port:PB13<4><1><default><default>.
Referring to the http://sunxi.org/Fex_Guide#Port_Definitions this shows
that the spdif out pin is PB13 using multiplex function 4. The enabling
of the pull up will be done in the device tree includes and this will be
delivered in a future patch series.
Changes in v2:
-Add comments to highlight that the spdif pins are not officially documented.
Marcus Cooper (1):
pinctrl: sun4i: add spdif to pin description.
drivers/pinctrl/sunxi/pinctrl-sun4i-a10.c | 17 ++++++++++++++---
1 file changed, 14 insertions(+), 3 deletions(-)
--
2.5.0
next reply other threads:[~2015-08-12 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 17:27 codekipper at gmail.com [this message]
2015-08-12 17:27 ` [PATCH v2] pinctrl: sun4i: add spdif to pin description codekipper at gmail.com
2015-08-13 8:58 ` [linux-sunxi] " Hans de Goede
2015-08-13 14:06 ` 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=1439400468-1563-1-git-send-email-codekipper@gmail.com \
--to=codekipper@gmail.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;
as well as URLs for NNTP newsgroup(s).