public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Neil Armstrong <narmstrong@baylibre.com>
To: xieqinick@gmail.com, robh+dt@kernel.org, devicetree@vger.kernel.org
Cc: nick@khadas.com, artem@khadas.com, khilman@baylibre.com,
	jbrunet@baylibre.com, martin.blumenstingl@googlemail.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 0/6] Add serial and i2c aliases for Khadas VIM boards
Date: Mon, 7 Jun 2021 09:01:34 +0200	[thread overview]
Message-ID: <4e1e960c-16b3-59a5-61c2-6d6e2f8204ac@baylibre.com> (raw)
In-Reply-To: <20210605062313.418343-1-xieqinick@gmail.com>

Hi Nick,

On 05/06/2021 08:23, xieqinick@gmail.com wrote:
> From: Nick Xie <nick@khadas.com>
> 
> This patch series update / add serial and i2c aliases to
> keep the same with 4.9 kernel for Khadas VIM boards
> (VIM1, VIM2, VIM3 and VIM3L).
> 
> Nick Xie (6):
>   arm64: dts: meson: vim3: add serial aliases
>   arm64: dts: meson: vim1: update serial aliases
>   arm64: dts: meson: vim2: update serial aliases
>   arm64: dts: meson: vim3: add i2c aliases
>   arm64: dts: meson: vim1: add i2c aliases
>   arm64: dts: meson: vim2: add i2c aliases
> 
>  .../boot/dts/amlogic/meson-gxl-s905x-khadas-vim.dts      | 8 +++++++-
>  arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts    | 7 ++++++-
>  arch/arm64/boot/dts/amlogic/meson-khadas-vim3.dtsi       | 9 +++++++++
>  3 files changed, 22 insertions(+), 2 deletions(-)
> 

Thanks for these patches.

I'm not sure about the current policy about aliases, but when we started upstreaming the amlogic boards,
only the exposed interfaces could have an alias and in the board.dts file only. But since other vendors
added a bunch of aliases of all the possible i2c/spi/uart/mmc/ethernet interfaces in the SoC dtsi....

But the question of the 40pins header remains, should we add aliases for interfaces present on the 40pin header ?????

Personally, we should'nt since these pins has no defined functions, so any alias should be added by a DT overlay loaded from U-boot.

But it's my own opinion.

Rob ? what's the current policy on that ?

Neil

      parent reply	other threads:[~2021-06-07  7:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-05  6:23 [PATCH 0/6] Add serial and i2c aliases for Khadas VIM boards xieqinick
2021-06-05  6:23 ` [PATCH 1/6] arm64: dts: meson: vim3: add serial aliases xieqinick
2021-06-05  9:52   ` Martin Blumenstingl
2021-06-05  6:23 ` [PATCH 2/6] arm64: dts: meson: vim1: update " xieqinick
2021-06-05  6:23 ` [PATCH 3/6] arm64: dts: meson: vim2: " xieqinick
2021-06-05  6:23 ` [PATCH 4/6] arm64: dts: meson: vim3: add i2c aliases xieqinick
2021-06-05  9:56   ` Martin Blumenstingl
2021-06-05  6:23 ` [PATCH 5/6] arm64: dts: meson: vim1: " xieqinick
2021-06-05  6:23 ` [PATCH 6/6] arm64: dts: meson: vim2: " xieqinick
2021-06-07  7:01 ` Neil Armstrong [this message]

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=4e1e960c-16b3-59a5-61c2-6d6e2f8204ac@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=artem@khadas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=nick@khadas.com \
    --cc=robh+dt@kernel.org \
    --cc=xieqinick@gmail.com \
    /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