From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi][PATCH v3 3/5] ARM: dts: sun7i: Add Itead Ibox support
Date: Thu, 21 Jan 2016 16:54:08 +0100 [thread overview]
Message-ID: <20160121155408.GG3997@lukather> (raw)
In-Reply-To: <CAEKpxBkTStWMNE6FT=zFLGhvxvb0Con-_idD9Oj8eKf2B5TKGg@mail.gmail.com>
Hi,
On Tue, Jan 19, 2016 at 08:43:34AM +0100, Code Kipper wrote:
> >> +&spi0 {
> >> + pinctrl-names = "default";
> >> + pinctrl-0 = <&spi0_pins_a>,
> >> + <&spi0_cs0_pins_a>;
> >> + status = "okay";
> >
> > What device is connected to that bus?
>
> These lead out to the header on the side of the box and is also
> enabled in the fex. If we remove this we might as well remove sata as
> that is also done via this header.
AFAIK, the SATA is not muxable, so the pins on this header can only be
used for that anyway.
What I'm more concerned about is pins that are just "generic" pins
that can have multiple functions that are not really enforced by any
design choice.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160121/16db483f/attachment.sig>
next prev parent reply other threads:[~2016-01-21 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 10:15 [linux-sunxi][PATCH v3 0/5] ARM: dt: sunxi: Add Itead Ibox support codekipper at gmail.com
2016-01-14 10:15 ` [linux-sunxi][PATCH v3 1/5] ARM: dts: sunxi: Add sunxi-itead-core-common.dtsi codekipper at gmail.com
2016-01-18 19:38 ` Maxime Ripard
2016-01-14 10:15 ` [linux-sunxi][PATCH v3 2/5] ARM: dts: sun7i: Add Itead A20 Core support codekipper at gmail.com
2016-01-14 10:15 ` [linux-sunxi][PATCH v3 3/5] ARM: dts: sun7i: Add Itead Ibox support codekipper at gmail.com
2016-01-18 19:41 ` Maxime Ripard
[not found] ` <CAEKpxBkTStWMNE6FT=zFLGhvxvb0Con-_idD9Oj8eKf2B5TKGg@mail.gmail.com>
2016-01-21 15:54 ` Maxime Ripard [this message]
2016-01-23 14:50 ` Code Kipper
2016-01-14 10:15 ` [linux-sunxi][PATCH v3 4/5] ARM: dts: sun4i: Add Itead A10 Core support codekipper at gmail.com
2016-01-18 19:44 ` Maxime Ripard
[not found] ` <CAEKpxBnt18EWoamdUtPO6FSyXdVc2Ct6aMgBJQo3P9HPweKi-w@mail.gmail.com>
2016-01-21 15:56 ` Maxime Ripard
2016-01-23 14:46 ` Code Kipper
2016-01-14 10:15 ` [linux-sunxi][PATCH v3 5/5] ARM: dts: sun4i: Itead Iteaduino to use common code codekipper at gmail.com
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=20160121155408.GG3997@lukather \
--to=maxime.ripard@free-electrons.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).