From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 01/21] ARM: DTS: vybrid: Add vf-u-boot.dtsi to set 'u-boot, dm-pre-reloc' in soc
Date: Tue, 15 Jan 2019 21:24:31 -0500 [thread overview]
Message-ID: <20190116022431.GI27429@bill-the-cat> (raw)
In-Reply-To: <20190115085858.618bd4d9@jawa>
On Tue, Jan 15, 2019 at 08:58:58AM +0100, Lukasz Majewski wrote:
> Hi Tom,
>
> > On Mon, Jan 14, 2019 at 03:17:20PM +0100, Lukasz Majewski wrote:
> >
> > > This property is necessary to allow pinctrl configuration before
> > > relocation (uart, DDR pins).
> > >
> > > Separate file will facilitate updating vf.dtsi from the Linux
> > > kernel.
> > >
> > > Signed-off-by: Lukasz Majewski <lukma@denx.de>
> > > ---
> > >
> > > arch/arm/dts/vf-u-boot.dtsi | 11 +++++++++++
> > > arch/arm/dts/vf.dtsi | 1 +
> > > 2 files changed, 12 insertions(+)
> > > create mode 100644 arch/arm/dts/vf-u-boot.dtsi
> >
> > We should call the file 'vf610-u-boot.dtsi' which will get it
> > automatically included in all vf610 platforms but still allow boards
> > that need their own -u-boot.dtsi file to #include vf610-u-boot.dtsi
> >
>
> Please forgive me but I do have a hard time to parse the above sentence.
>
> Do you propose to:
>
> 1. Rename vf-u-boot.dtsi -> vf610-u-boot.dtsi ?
>
> And then just include it in the generic (easily ported from Linux)
> vf.dtsi file?
>
> or
>
> 2. Shall I rename vf-u-boot.dtsi -> vf610-u-boot.dtsi and then do not
> include it into vf.dtsi, but it shall be included in board dts files
> (like bk4.dtsi) ?
Neither exactly. See scripts/Makefile.lib for the rules that automatically pick up
various -u-boot.dtsi suffixed files. "vf610" will be picked up and "vf"
will not. You do _not_ need include it in other non "-u-boot.dtsi"
files. You will likely end up with vf610-bk4-u-boot.dtsi or something
to both set stdout-path under /chosen and #include vf610-u-boot.dtsi.
If you don't need a board specific -u-boot.dtsi file then just
vf610-u-boot.dtsi gets picked up automatically and you're done.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190115/4ea46e32/attachment.sig>
next prev parent reply other threads:[~2019-01-16 2:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 14:17 [U-Boot] [PATCH v1 00/21] imx: vybrid: Update BK4 and PCM052 boards to only use DM/DTS Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 01/21] ARM: DTS: vybrid: Add vf-u-boot.dtsi to set 'u-boot, dm-pre-reloc' in soc Lukasz Majewski
2019-01-14 14:30 ` Tom Rini
2019-01-15 7:58 ` Lukasz Majewski
2019-01-16 2:24 ` Tom Rini [this message]
2019-01-16 7:33 ` Lukasz Majewski
2019-01-16 12:23 ` Tom Rini
2019-01-14 14:17 ` [U-Boot] [PATCH v1 02/21] net: FEC: Add compatible for vybrid (vf610) to reuse fec_mxc.c driver Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 03/21] net: Kconfig: FEC: Add dependency on VF610 Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 04/21] vybrid: ddr: Extend vf610-pinfunc.h with DDR pads definitions Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 05/21] vybrid: clock: Provide enable_i2c_clk() function for Vybrid Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 06/21] vybrid: Define the imx_get_mac_from_fuse() as a __weak function Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 07/21] pcm052: board: Remove "m4go" command as it is superseded by "bootaux" Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 08/21] pcm052: board: vybrid: Update the board name for BK4 device Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 09/21] ARM: DTS: vybrid: Update vf.dtsi file to descibe more vf610 hardware Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 10/21] pcm052: board: cosmetic: Add copyright notice to pcm052.c Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 11/21] ARM: DTS: Update pcm052 based dts files (bk4r1/pcm052.dts) Lukasz Majewski
2019-01-14 14:32 ` Tom Rini
2019-01-15 8:20 ` Lukasz Majewski
2019-01-16 2:33 ` Tom Rini
2019-01-16 7:47 ` Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 12/21] defconfig: bk4/pcm052: Update bk4r1|pcm052_defconfig to support DM/DT Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 13/21] config: pcm052: Use SZ_X{MK} from linux/sizes.h for include/configs/pcm052.h Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 14/21] config: bk4: Update include/configs/bk4r1.h file Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 15/21] pcm052: board: Remove in-board setup code (it is now replaced by DM setup) Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 16/21] config: bk4: Update u-boot script to support recovery via SD card Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 17/21] config: bk4: Update u-boot envs to support NOR memories initial setup Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 18/21] pcm052: bk4: sdcard: Add support for SD card booting/recovery Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 19/21] pcm052: board: Add code to setup LED default states Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 20/21] pcm052: mac: Provide board specific imx_get_mac_from_fuse() function Lukasz Majewski
2019-01-14 14:17 ` [U-Boot] [PATCH v1 21/21] pcm052: bk4: Add board_phy_config() for BK4 to setup ksz8081 phy Lukasz Majewski
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=20190116022431.GI27429@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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