From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: khilman@baylibre.com, linux-amlogic@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] arm64: dts: khadas-vim3: move common nodes into meson-khadas-vim3.dtsi
Date: Sun, 25 Aug 2019 21:41:14 +0200 [thread overview]
Message-ID: <CAFBinCACwWqMGDJ9R7f5D2YhyWz7n7UgH7A4fJbkAp2drKC2Kg@mail.gmail.com> (raw)
In-Reply-To: <20190823081427.17228-2-narmstrong@baylibre.com>
On Fri, Aug 23, 2019 at 10:15 AM Neil Armstrong <narmstrong@baylibre.com> wrote:
>
> To prepare support of the Amlogic SM1 based Khadas VIM3, move the non-G12B
> specific nodes (all except DVFS and Audio) to a new meson-khadas-vim3.dtsi
out of curiosity: is audio because of different routing on the board
or is it just because the audio driver needs more work for SM1?
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
WARNING: multiple messages have this Message-ID (diff)
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: khilman@baylibre.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 1/3] arm64: dts: khadas-vim3: move common nodes into meson-khadas-vim3.dtsi
Date: Sun, 25 Aug 2019 21:41:14 +0200 [thread overview]
Message-ID: <CAFBinCACwWqMGDJ9R7f5D2YhyWz7n7UgH7A4fJbkAp2drKC2Kg@mail.gmail.com> (raw)
In-Reply-To: <20190823081427.17228-2-narmstrong@baylibre.com>
On Fri, Aug 23, 2019 at 10:15 AM Neil Armstrong <narmstrong@baylibre.com> wrote:
>
> To prepare support of the Amlogic SM1 based Khadas VIM3, move the non-G12B
> specific nodes (all except DVFS and Audio) to a new meson-khadas-vim3.dtsi
out of curiosity: is audio because of different routing on the board
or is it just because the audio driver needs more work for SM1?
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: khilman@baylibre.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 1/3] arm64: dts: khadas-vim3: move common nodes into meson-khadas-vim3.dtsi
Date: Sun, 25 Aug 2019 21:41:14 +0200 [thread overview]
Message-ID: <CAFBinCACwWqMGDJ9R7f5D2YhyWz7n7UgH7A4fJbkAp2drKC2Kg@mail.gmail.com> (raw)
In-Reply-To: <20190823081427.17228-2-narmstrong@baylibre.com>
On Fri, Aug 23, 2019 at 10:15 AM Neil Armstrong <narmstrong@baylibre.com> wrote:
>
> To prepare support of the Amlogic SM1 based Khadas VIM3, move the non-G12B
> specific nodes (all except DVFS and Audio) to a new meson-khadas-vim3.dtsi
out of curiosity: is audio because of different routing on the board
or is it just because the audio driver needs more work for SM1?
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-08-25 19:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 8:14 [PATCH 0/3] arm64: meson-sm1: add support for the SM1 based VIM3 Neil Armstrong
2019-08-23 8:14 ` Neil Armstrong
2019-08-23 8:14 ` Neil Armstrong
2019-08-23 8:14 ` [PATCH 1/3] arm64: dts: khadas-vim3: move common nodes into meson-khadas-vim3.dtsi Neil Armstrong
2019-08-23 8:14 ` Neil Armstrong
2019-08-23 8:14 ` Neil Armstrong
2019-08-25 19:41 ` Martin Blumenstingl [this message]
2019-08-25 19:41 ` Martin Blumenstingl
2019-08-25 19:41 ` Martin Blumenstingl
2019-08-26 7:36 ` Neil Armstrong
2019-08-26 7:36 ` Neil Armstrong
2019-08-26 7:36 ` Neil Armstrong
2019-08-23 8:14 ` [PATCH 2/3] amlogic: arm: add Amlogic SM1 based Khadas VIM3 variant bindings Neil Armstrong
2019-08-23 8:14 ` Neil Armstrong
2019-08-23 8:14 ` Neil Armstrong
2019-08-25 19:51 ` Martin Blumenstingl
2019-08-25 19:51 ` Martin Blumenstingl
2019-08-25 19:51 ` Martin Blumenstingl
2019-08-26 7:42 ` Neil Armstrong
2019-08-26 7:42 ` Neil Armstrong
2019-08-26 7:42 ` Neil Armstrong
2019-08-26 7:42 ` Neil Armstrong
2019-08-27 21:18 ` Martin Blumenstingl
2019-08-27 21:18 ` Martin Blumenstingl
2019-08-27 21:18 ` Martin Blumenstingl
2019-08-23 8:14 ` [PATCH 3/3] arm64: dts: khadas-vim3: add support for the SM1 based VIM3 Neil Armstrong
2019-08-23 8:14 ` Neil Armstrong
2019-08-23 8:14 ` Neil Armstrong
2019-08-25 19:55 ` Martin Blumenstingl
2019-08-25 19:55 ` Martin Blumenstingl
2019-08-25 19:55 ` Martin Blumenstingl
2019-08-26 7:43 ` Neil Armstrong
2019-08-26 7:43 ` Neil Armstrong
2019-08-26 7:43 ` Neil Armstrong
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=CAFBinCACwWqMGDJ9R7f5D2YhyWz7n7UgH7A4fJbkAp2drKC2Kg@mail.gmail.com \
--to=martin.blumenstingl@googlemail.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=narmstrong@baylibre.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 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.