All of lore.kernel.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 5/5] ARM: dts: sun6i: Add support for Sinlinx A31s SDK board
Date: Mon, 19 Oct 2015 08:15:35 +0200	[thread overview]
Message-ID: <20151019061535.GR2711@lukather> (raw)
In-Reply-To: <CAGb2v66KcHA3rROM2GizEY4xD51eKhZRyUnqrtkRNU89KjqoRg@mail.gmail.com>

On Fri, Oct 16, 2015 at 03:25:13PM +0800, Chen-Yu Tsai wrote:
> On Fri, Oct 16, 2015 at 3:20 PM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> > Hi,
> >
> > On Mon, Oct 12, 2015 at 05:42:10PM +0800, Chen-Yu Tsai wrote:
> >> On Mon, Oct 12, 2015 at 5:30 PM, Maxime Ripard
> >> <maxime.ripard@free-electrons.com> wrote:
> >> > Hi,
> >> >
> >> > On Sat, Oct 10, 2015 at 10:49:00PM +0800, Chen-Yu Tsai wrote:
> >> >> +&i2c0 {
> >> >> +     /* Available on camera header */
> >> >> +     pinctrl-names = "default";
> >> >> +     pinctrl-0 = <&i2c0_pins_a>;
> >> >> +     status = "okay";
> >> >> +};
> >> >> +
> >> >> +&i2c1 {
> >> >> +     /* Available on LCD header */
> >> >> +     pinctrl-names = "default";
> >> >> +     pinctrl-0 = <&i2c1_pins_a>;
> >> >> +     status = "okay";
> >> >> +};
> >> >
> >> > Are those two actually used anywhere on the board itself, or just
> >> > exposed on the pin headers?
> >>
> >> They are exposed as grouped headers. 1 header has all the camera
> >> related stuff, like the CSI pins, and various voltage sources
> >> from the PMIC. The other has the LCD pins, resistive touchpanel,
> >> I2C for capacitive touchpanel, and of course voltage sources.
> >>
> >> The LCD header is an FPC connector, while the camera header is
> >> the common (common for sunxi devboards) 2.0mm pins. I'm not sure
> >> if there is some common pinout amongst vendors, but at least
> >> Sinlinx sells their own 7" LCD display w/ CTP, VGA converter,
> >> and camera modules. I have both the LCD and VGA converter.
> >>
> >> Note that these I2C pins have valid external pull-ups. I doubt
> >> they can be easily re-purposed.
> >
> > Still, the policy we've had so far is that if the user can use it for
> > something else (like a GPIO, which is the case here), we don't do
> > enforce any default, and the user will make the right choice.
> 
> To clarify, unless an actual device is connected, forcing a choice,
> we won't make that choice for the user, even if the connector is
> specifically designed for one type of application.
> 
> Did I get that right?

Yep.

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/20151019/049a7d7f/attachment.sig>

  reply	other threads:[~2015-10-19  6:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-10 14:48 [PATCH v2 0/5] ARM: sunxi: Sinlinx SinA31s support / AXP22x dtsi conversion Chen-Yu Tsai
2015-10-10 14:48 ` [PATCH v2 1/5] ARM: dts: sun6i: hummingbird: Fix VDD-CPU and VDD-GPU regulator names Chen-Yu Tsai
2015-10-12  8:31   ` Maxime Ripard
2015-10-12  8:35     ` Chen-Yu Tsai
2015-10-13 18:46   ` Maxime Ripard
2015-10-10 14:48 ` [PATCH v2 2/5] ARM: dts: sunxi: Add dtsi for AXP22x PMIC Chen-Yu Tsai
2015-10-12  9:27   ` Maxime Ripard
2015-10-10 14:48 ` [PATCH v2 3/5] ARM: dts: sun6i: hummingbird: Use axp22x.dtsi for AXP221 regulators Chen-Yu Tsai
2015-10-13 18:46   ` Maxime Ripard
2015-10-10 14:48 ` [PATCH v2 4/5] ARM: dts: sun6i: hummingbird: Enable AXP221 DC5LDO regulator as "vdd-cpus" Chen-Yu Tsai
2015-10-13 18:46   ` Maxime Ripard
2015-10-10 14:49 ` [PATCH v2 5/5] ARM: dts: sun6i: Add support for Sinlinx A31s SDK board Chen-Yu Tsai
2015-10-12  9:30   ` Maxime Ripard
2015-10-12  9:42     ` Chen-Yu Tsai
2015-10-16  7:20       ` Maxime Ripard
2015-10-16  7:25         ` Chen-Yu Tsai
2015-10-19  6:15           ` Maxime Ripard [this message]
2015-10-19  6:22             ` Chen-Yu Tsai

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=20151019061535.GR2711@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.