From: Heiko Stuebner <heiko@sntech.de>
To: Nick Xie <xieqinick@gmail.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
robh@kernel.org, nick@khadas.com
Subject: Re: [PATCH] arm64: dts: rockchip: Add support for Khadas Edge/Edge-V/Captain boards
Date: Fri, 14 Jun 2019 13:31:28 +0200 [thread overview]
Message-ID: <4121108.4RU3k1uWxS@phil> (raw)
In-Reply-To: <CAP4nuTU1BjmpXk5zqWTjBVyO=1ks-Rn65ryaxdQ=GiGa+VK6-A@mail.gmail.com>
Am Montag, 10. Juni 2019, 09:19:52 CEST schrieb Nick Xie:
> Hello Heiko,
>
> Thanks for your review.
>
> > Both Captain and Edge-V seem to be identical from a component point
> > of view, so should likely share the same dts, or is there some major
> > difference coming later?
>
> This is the first patch to support Khadas Edge/Edge-V/Captain board, so I
> just add basic dts nodes.
>
> For Captain has more peripherals then Edge-V, so the dts will be different
> in the future, but it is the same now.
Sounds reasonable, thanks for the clarification.
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Nick Xie <xieqinick@gmail.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
robh@kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
nick@khadas.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: rockchip: Add support for Khadas Edge/Edge-V/Captain boards
Date: Fri, 14 Jun 2019 13:31:28 +0200 [thread overview]
Message-ID: <4121108.4RU3k1uWxS@phil> (raw)
In-Reply-To: <CAP4nuTU1BjmpXk5zqWTjBVyO=1ks-Rn65ryaxdQ=GiGa+VK6-A@mail.gmail.com>
Am Montag, 10. Juni 2019, 09:19:52 CEST schrieb Nick Xie:
> Hello Heiko,
>
> Thanks for your review.
>
> > Both Captain and Edge-V seem to be identical from a component point
> > of view, so should likely share the same dts, or is there some major
> > difference coming later?
>
> This is the first patch to support Khadas Edge/Edge-V/Captain board, so I
> just add basic dts nodes.
>
> For Captain has more peripherals then Edge-V, so the dts will be different
> in the future, but it is the same now.
Sounds reasonable, thanks for the clarification.
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-14 11:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 9:21 [PATCH] arm64: dts: rockchip: Add support for Khadas Edge/Edge-V/Captain boards xieqinick
2019-05-28 9:21 ` xieqinick
2019-06-04 14:08 ` Heiko Stuebner
2019-06-04 14:08 ` Heiko Stuebner
2019-06-10 7:19 ` Nick Xie
2019-06-14 11:31 ` Heiko Stuebner [this message]
2019-06-14 11:31 ` Heiko Stuebner
2019-06-10 7:57 ` [PATCH v2] " xieqinick
2019-06-10 7:57 ` xieqinick
2019-06-14 11:32 ` Heiko Stuebner
2019-06-14 11:32 ` Heiko Stuebner
2019-06-14 13:32 ` Nick Xie
2019-06-14 14:01 ` Heiko Stübner
2019-06-14 14:01 ` Heiko Stübner
2019-06-14 14:06 ` Nick Xie
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=4121108.4RU3k1uWxS@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=nick@khadas.com \
--cc=robh+dt@kernel.org \
--cc=robh@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 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.