From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/7] ARM: dts: sun8i: h3: Split out common board design for ALL-H3-CC
Date: Tue, 24 Apr 2018 21:37:54 +0200 [thread overview]
Message-ID: <20180424193754.jsuucbq57onhxhqe@flea> (raw)
In-Reply-To: <CAGb2v65iwbmOvQ2YA0e4QyTzQVj=F+5n6cWt2q6K80Y2b_3q3g@mail.gmail.com>
On Tue, Apr 24, 2018 at 08:17:11PM +0800, Chen-Yu Tsai wrote:
> On Tue, Apr 24, 2018 at 8:13 PM, Maxime Ripard
> <maxime.ripard@bootlin.com> wrote:
> > On Tue, Apr 24, 2018 at 07:34:19PM +0800, Chen-Yu Tsai wrote:
> >> The Libre Computer Project ALL-H3-CC has three models, all using the
> >> same board design, but with different pin compatible SoCs and amount of
> >> DRAM.
> >>
> >> Currently only the H3 1GB DRAM variant is supported. To support the two
> >> other variants, first split the original device tree into a common board
> >> design part and an SoC specific part.
> >>
> >> The SoC part only defines which SoC is used and model name, and includes
> >> the SoC specific dtsi file and the common design dtsi file.
> >>
> >> Also fix up the SPDX identifier line to use the correct comment style,
> >> and place it on the first line.
> >>
> >> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> >> ---
> >> .../boot/dts/sun8i-h3-libretech-all-h3-cc.dts | 213 +-----------------
> >> ....dts => sunxi-hx-libretech-all-h3-cc.dtsi} | 11 +-
> >
> > I think I prefer the name of Neil's DTSI better, and since pretty much
> > the same patches (a couple of hours) before, we'll merge them (while
> > merging the rest of your patches, obviously).
> >
> > Does that work for you?
>
> I would like for the regulator voltage fix to be merged before the split.
> This will make it trivial to back port, instead of having to reverse the
> split, and maybe failing.
Yes, I was just talking about replacing your two redundant patches,
but keeping the order you have.
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-04-24 19:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 11:34 [PATCH 0/7] ARM: dts: sunxi: Support ALL-H3-CC H2+/H5 variants Chen-Yu Tsai
2018-04-24 11:34 ` [PATCH 1/7] ARM: dts: sun8i: h3: fix ALL-H3-CC H3 ver VCC-1V2 regulator voltage Chen-Yu Tsai
2018-04-24 11:52 ` Maxime Ripard
2018-04-24 11:34 ` [PATCH 2/7] ARM: dts: sun8i: h3: Split out common board design for ALL-H3-CC Chen-Yu Tsai
2018-04-24 12:13 ` Maxime Ripard
2018-04-24 12:17 ` Chen-Yu Tsai
2018-04-24 19:37 ` Maxime Ripard [this message]
2018-04-25 3:19 ` Chen-Yu Tsai
2018-04-25 12:39 ` Maxime Ripard
2018-04-25 13:59 ` Chen-Yu Tsai
2018-04-24 11:34 ` [PATCH 3/7] ARM: dts: sun8i: h2-plus: Sort dtb entries in Makefile Chen-Yu Tsai
2018-04-24 11:53 ` Maxime Ripard
2018-04-24 11:34 ` [PATCH 4/7] ARM: dts: sun8i: h2+: Add Libre Computer Board ALL-H3-CC H2+ ver Chen-Yu Tsai
2018-04-24 11:54 ` Maxime Ripard
2018-04-24 11:34 ` [PATCH 5/7] arm64: dts: allwinner: h5: Add cpu0 label for first cpu Chen-Yu Tsai
2018-04-24 11:54 ` Maxime Ripard
2018-04-24 11:34 ` [PATCH 6/7] arm64: dts: allwinner: Sort dtb entries in Makefile Chen-Yu Tsai
2018-04-24 11:54 ` Maxime Ripard
2018-04-24 11:34 ` [PATCH 7/7] arm64: dts: allwinner: h5: Add Libre Computer Board ALL-H3-CC H5 ver 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=20180424193754.jsuucbq57onhxhqe@flea \
--to=maxime.ripard@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox