linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Aswath Govindraju <a-govindraju@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, <devicetree@vger.kernel.org>,
	Suman Anna <s-anna@ti.com>, Lokesh Vutla <lokeshvutla@ti.com>,
	Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-am64-main: Update the location of ATF in SRAM and increase its max size
Date: Mon, 14 Jun 2021 09:32:15 -0500	[thread overview]
Message-ID: <20210614143215.4dzkwux4bijn47hs@cylinder> (raw)
In-Reply-To: <162343800075.7434.10921347563461214925.b4-ty@ti.com>

On 14:00-20210611, Nishanth Menon wrote:
> On Mon, 7 Jun 2021 19:08:06 +0530, Aswath Govindraju wrote:
> > Due to a limitation for USB DFU boot mode, SPL load address has to be less
> > than  or equal to 0x70001000. So, load address of SPL and ATF have been
> > moved to 0x70000000 and 0x701a0000 respectively.
> > 
> > Also, the maximum size of ATF has been increased to 0x1c000 [1].
> > 
> > Therefore, update ATF's location and maximum size accordingly in the device
> > tree file.
> > 
> > [...]
> 
> Hi Aswath Govindraju,
> 
> I have applied the following to branch ti-k3-dts-next on [1].
> Thank you!
> 
> [1/1] arm64: dts: ti: k3-am64-main: Update the location of ATF in SRAM and increase its max size
>       commit: d05c19bd3f588445eb6769fb71f2e5e02b7a959e
> 
> 
> All being well this means that it will be integrated into the linux-next
> tree (usually sometime in the next 24 hours) and sent up the chain during
> the next merge window (or sooner if it is a relevant bug fix), however if
> problems are discovered then the patch may be dropped or reverted.
> 
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems and
> send followup patches addressing any issues that are reported if needed.
> 
> If any updates are required or you are submitting further changes they
> should be sent as incremental updates against current git, existing
> patches will not be replaced.
> 
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
> 
> [1] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git


Based on discussion in [1], I have dropped this patch from my queue.


[1] https://lore.kernel.org/linux-arm-kernel/20210614142849.ogi4emuqgxg3m7ls@constrict/T/#t
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

      reply	other threads:[~2021-06-14 14:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 13:38 [PATCH v2] arm64: dts: ti: k3-am64-main: Update the location of ATF in SRAM and increase its max size Aswath Govindraju
2021-06-09 14:09 ` Lokesh Vutla
2021-06-09 14:29 ` Lokesh Vutla
2021-06-09 15:22   ` Aswath Govindraju
2021-06-09 15:24     ` Lokesh Vutla
2021-06-14 18:16       ` Suman Anna
2021-06-11 19:00 ` Nishanth Menon
2021-06-14 14:32   ` Nishanth Menon [this message]

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=20210614143215.4dzkwux4bijn47hs@cylinder \
    --to=nm@ti.com \
    --cc=a-govindraju@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=s-anna@ti.com \
    --cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).