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 4/7] dts: sun8i-h3: add UART1-3 to Orange Pi Plus
Date: Tue, 6 Sep 2016 22:01:08 +0200	[thread overview]
Message-ID: <20160906200108.GK9040@lukather> (raw)
In-Reply-To: <20160906085202.GA4854@carbon.kippendief.biz>

On Tue, Sep 06, 2016 at 10:52:02AM +0200, Jorik Jonker wrote:
> On Tue, Sep 06, 2016 at 11:04:38AM +0800, Chen-Yu Tsai wrote:
> >In short, I'm ok with it. But please put an explicit
> >
> >   status = "disabled";
> >
> >and probably a comment about how/where the peripheral can be
> >used in the board dts.
> 
> Allright, I will do that in v3.
> 
> >I intended to do this for the Banana Pis. Though my original plan
> >was to enable Raspberry Pi compatible peripherals by default, and
> >list the other peripherals that are defined by the vendor as
> >"disabled".
> >
> >"Defined by the vendor" means that the vendor has some sort of
> >document associating the gpio header pins with the peripherals,
> >as shown in:
> >
> >   http://www.orangepi.org/Docs/Pindefinition.html#CON3_Definition
> >
> >This should make it easier for the average user to enable the
> >peripherals. I'm not sure we should list _all_ possible ones
> >though. That would make the list very large, and some might
> >end up never being used.
> 
> This is exactly what I was thinking, albeit I wanted to go a bit 'bigger':
> move all unambiguous pinmux/peripheral associations from the H3 DTS files to
> the DTSI, complete them with known associations for which there are drivers,
> and have all of these disabled. Reduce the existing blocks in the DTS files
> to just "status = okay".
> 
> Peripherals requiring board-specific things (like emac, USB, voltage
> regulators, displays) stay put in the DTS.
> 
> It will explodes the scope of my proposed change a bit, but if you are OK
> with this, I will gladly do it.
> 
> Maxime, Chen-Yu: what do you think of this?

I'm not exactly sure what you have in mind. Please send a patch, and
we'll see then :)

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160906/52ae5713/attachment.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Jorik Jonker <jorik@kippendief.biz>
Cc: Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	devicetree <devicetree@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 4/7] dts: sun8i-h3: add UART1-3 to Orange Pi Plus
Date: Tue, 6 Sep 2016 22:01:08 +0200	[thread overview]
Message-ID: <20160906200108.GK9040@lukather> (raw)
In-Reply-To: <20160906085202.GA4854@carbon.kippendief.biz>

[-- Attachment #1: Type: text/plain, Size: 1884 bytes --]

On Tue, Sep 06, 2016 at 10:52:02AM +0200, Jorik Jonker wrote:
> On Tue, Sep 06, 2016 at 11:04:38AM +0800, Chen-Yu Tsai wrote:
> >In short, I'm ok with it. But please put an explicit
> >
> >   status = "disabled";
> >
> >and probably a comment about how/where the peripheral can be
> >used in the board dts.
> 
> Allright, I will do that in v3.
> 
> >I intended to do this for the Banana Pis. Though my original plan
> >was to enable Raspberry Pi compatible peripherals by default, and
> >list the other peripherals that are defined by the vendor as
> >"disabled".
> >
> >"Defined by the vendor" means that the vendor has some sort of
> >document associating the gpio header pins with the peripherals,
> >as shown in:
> >
> >   http://www.orangepi.org/Docs/Pindefinition.html#CON3_Definition
> >
> >This should make it easier for the average user to enable the
> >peripherals. I'm not sure we should list _all_ possible ones
> >though. That would make the list very large, and some might
> >end up never being used.
> 
> This is exactly what I was thinking, albeit I wanted to go a bit 'bigger':
> move all unambiguous pinmux/peripheral associations from the H3 DTS files to
> the DTSI, complete them with known associations for which there are drivers,
> and have all of these disabled. Reduce the existing blocks in the DTS files
> to just "status = okay".
> 
> Peripherals requiring board-specific things (like emac, USB, voltage
> regulators, displays) stay put in the DTS.
> 
> It will explodes the scope of my proposed change a bit, but if you are OK
> with this, I will gladly do it.
> 
> Maxime, Chen-Yu: what do you think of this?

I'm not exactly sure what you have in mind. Please send a patch, and
we'll see then :)

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-09-06 20:01 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31 19:30 [PATCH v2 0/7] dts: sun8i: add extra uart/i2c to H3 jorik at kippendief.biz
2016-08-31 19:30 ` jorik
2016-08-31 19:30 ` jorik-U9/BOH3cVv3CLqq/8VZgpA
2016-08-31 19:30 ` [PATCH v2 1/7] dts: sun8i-h3: add pinmux definitions for uart2/uart3 jorik at kippendief.biz
2016-08-31 19:30   ` jorik
2016-08-31 19:30 ` [PATCH v2 2/7] dts: sun8i-h3: add pinmux definitions for i2c0/i2c1 jorik at kippendief.biz
2016-08-31 19:30   ` jorik
2016-09-01  2:45   ` Chen-Yu Tsai
2016-09-01  2:45     ` Chen-Yu Tsai
2016-09-01  2:45     ` Chen-Yu Tsai
2016-08-31 19:30 ` [PATCH v2 3/7] dts: sun8i-h3: add i2c0/i2c1 SoC peripherals jorik at kippendief.biz
2016-08-31 19:30   ` jorik
2016-08-31 19:30   ` jorik-U9/BOH3cVv3CLqq/8VZgpA
2016-09-01  2:42   ` Chen-Yu Tsai
2016-09-01  2:42     ` Chen-Yu Tsai
2016-09-01  2:42     ` Chen-Yu Tsai
2016-09-01  6:31     ` Jorik Jonker
2016-09-01  6:42       ` Chen-Yu Tsai
2016-09-01  6:42         ` Chen-Yu Tsai
2016-09-01  6:42         ` Chen-Yu Tsai
2016-09-01  6:34     ` Jorik Jonker
2016-09-01  6:34       ` Jorik Jonker
2016-09-01  6:34       ` Jorik Jonker
2016-08-31 19:30 ` [PATCH v2 4/7] dts: sun8i-h3: add UART1-3 to Orange Pi Plus jorik at kippendief.biz
2016-08-31 19:30   ` jorik
2016-09-02  7:04   ` Maxime Ripard
2016-09-02  7:04     ` Maxime Ripard
2016-09-02  7:04     ` Maxime Ripard
2016-09-03 12:09     ` Jorik Jonker
2016-09-03 12:09       ` Jorik Jonker
2016-09-03 12:09       ` Jorik Jonker
2016-09-05 19:31       ` Maxime Ripard
2016-09-05 19:31         ` Maxime Ripard
2016-09-05 19:31         ` Maxime Ripard
2016-09-06  3:04         ` Chen-Yu Tsai
2016-09-06  3:04           ` Chen-Yu Tsai
2016-09-06  3:04           ` Chen-Yu Tsai
2016-09-06  8:52           ` Jorik Jonker
2016-09-06  8:52             ` Jorik Jonker
2016-09-06 20:01             ` Maxime Ripard [this message]
2016-09-06 20:01               ` Maxime Ripard
2016-09-06 20:02           ` Maxime Ripard
2016-09-06 20:02             ` Maxime Ripard
2016-09-06 20:02             ` Maxime Ripard
2016-08-31 19:30 ` [PATCH v2 5/7] dts: sun8i-h3: add UART1-3 to Orange Pi PC jorik at kippendief.biz
2016-08-31 19:30   ` jorik
2016-08-31 19:30 ` [PATCH v2 6/7] dts: sun8i-h3: add I2C0-1 to Orange Pi Plus jorik at kippendief.biz
2016-08-31 19:30   ` jorik
2016-08-31 19:30 ` [PATCH v2 7/7] dts: sun8i-h3: add I2C0-1 to Orange Pi PC jorik at kippendief.biz
2016-08-31 19:30   ` jorik

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=20160906200108.GK9040@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.