From: Marek Behun <marek.behun@nic.cz>
To: "Pali Rohár" <pali@kernel.org>
Cc: Stefan Roese <sr@denx.de>, u-boot@lists.denx.de
Subject: Re: [PATCH u-boot-marvell v2 5/6] arm: mvebu: dts: turris_mox: add nodes for SPI NOR partitions
Date: Thu, 10 Jun 2021 16:28:59 +0200 [thread overview]
Message-ID: <20210610162859.4ec5cf7a@thinkpad> (raw)
In-Reply-To: <20210610140705.y42ghe3z624ady7n@pali>
On Thu, 10 Jun 2021 16:07:05 +0200
Pali Rohár <pali@kernel.org> wrote:
> On Thursday 10 June 2021 07:12:53 Stefan Roese wrote:
> > Hi Pali,
> >
> > On 08.06.21 11:51, Pali Rohár wrote:
> > > On Monday 07 June 2021 16:34:50 Marek Behún wrote:
> > > > Add nodes for SPI NOR partitions to the device tree of Turris MOX, as
> > > > are in Linux' device tree.
> > >
> > > This patch is not needed (for now) as U-Boot cannot parse SPI NOR
> > > partitions from DT yet. U-Boot for SPI NOR currently supports specifying
> > > partitions only via CONFIG_MTDPARTS_DEFAULT compile option.
> >
> > But do you agree that this patch "does not hurt"? I'm asking to check,
> > if I should include this patch in a potential pull request.
>
> Yes. This does not hurt and currently does nothing. And after patches
> for SPI NOR parsing are merged then this patch can be useful.
>
> So if you are fine with merging which which currently does noting and in
> future is useful then there is no problem with it.
Moreover this definition is also in kernel's DTS. I am going to try to
work on the U-Boot's A3720 comphy driver so that we can completely
align U-Boot's A3720 DTS files with kernel's.
Marek
next prev parent reply other threads:[~2021-06-10 14:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 17:09 [PATCH u-boot-marvell 0/7] Changes for Turris MOX Marek Behún
2021-06-02 17:09 ` [PATCH u-boot-marvell 1/7] arm: mvebu: dts: turris_mox: add button and LED nodes Marek Behún
2021-06-02 17:09 ` [PATCH u-boot-marvell 2/7] arm: mvebu: turris_mox: add support for board rescue mode Marek Behún
2021-06-03 15:18 ` Marek Behún
2021-06-02 17:09 ` [PATCH u-boot-marvell 3/7] arm: mvebu: turris_mox: start blinking PHY LEDs when entering rescue Marek Behún
2021-06-02 17:09 ` [PATCH u-boot-marvell 4/7] arm: mvebu: configs: turris_mox: add fdtfile default env variable Marek Behún
2021-06-02 17:09 ` [PATCH u-boot-marvell 5/7] arm: mvebu: dts: turris_mox: add nodes for SPI NOR partitions Marek Behún
2021-06-02 17:10 ` [PATCH u-boot-marvell 6/7] arm: mvebu: turris_mox: enable options for Turris network boot Marek Behún
2021-06-02 17:10 ` [PATCH u-boot-marvell 7/7] arm64: a37xx: dts: rename internal-regs node Marek Behún
2021-06-03 15:20 ` Marek Behún
2021-06-07 14:34 ` [PATCH u-boot-marvell v2 0/6] Changes for Turris MOX Marek Behún
2021-06-07 14:34 ` [PATCH u-boot-marvell v2 1/6] arm: mvebu: dts: turris_mox: add button and LED nodes Marek Behún
2021-06-08 9:47 ` Pali Rohár
2021-06-10 5:06 ` Stefan Roese
2021-06-07 14:34 ` [PATCH u-boot-marvell v2 2/6] arm: mvebu: turris_mox: add support for board rescue mode Marek Behún
2021-06-08 9:48 ` Pali Rohár
2021-06-10 5:09 ` Stefan Roese
2021-06-07 14:34 ` [PATCH u-boot-marvell v2 3/6] arm: mvebu: turris_mox: start blinking PHY LEDs when entering rescue Marek Behún
2021-06-08 9:49 ` Pali Rohár
2021-06-10 5:09 ` Stefan Roese
2021-06-07 14:34 ` [PATCH u-boot-marvell v2 4/6] arm: mvebu: configs: turris_mox: add fdtfile default env variable Marek Behún
2021-06-08 9:50 ` Pali Rohár
2021-06-10 5:10 ` Stefan Roese
2021-06-07 14:34 ` [PATCH u-boot-marvell v2 5/6] arm: mvebu: dts: turris_mox: add nodes for SPI NOR partitions Marek Behún
2021-06-08 9:51 ` Pali Rohár
2021-06-10 5:12 ` Stefan Roese
2021-06-10 14:07 ` Pali Rohár
2021-06-10 14:28 ` Marek Behun [this message]
2021-06-11 4:14 ` Stefan Roese
2021-06-10 5:11 ` Stefan Roese
2021-06-07 14:34 ` [PATCH u-boot-marvell v2 6/6] arm: mvebu: turris_mox: enable options for Turris network boot Marek Behún
2021-06-08 9:52 ` Pali Rohár
2021-06-10 5:11 ` Stefan Roese
2021-06-10 7:54 ` [PATCH u-boot-marvell v2 0/6] Changes for Turris MOX Stefan Roese
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=20210610162859.4ec5cf7a@thinkpad \
--to=marek.behun@nic.cz \
--cc=pali@kernel.org \
--cc=sr@denx.de \
--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