From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 4/6] arm: mach-omap2: am33xx: Disable EMIF_DEVOFF immediately before hw leveling
Date: Fri, 26 Apr 2019 12:46:03 -0400 [thread overview]
Message-ID: <20190426164603.GS31207@bill-the-cat> (raw)
In-Reply-To: <66f5b833-9393-3635-c342-1ba59cd343c2@ti.com>
On Fri, Apr 26, 2019 at 10:14:40PM +0530, Keerthy wrote:
>
>
> On 26/04/19 6:25 PM, Tom Rini wrote:
> >On Fri, Apr 26, 2019 at 05:23:28PM +0530, Lokesh Vutla wrote:
> >>
> >>
> >>On 26/04/19 4:46 PM, Tom Rini wrote:
> >>>On Fri, Apr 12, 2019 at 12:08:18PM +0530, Keerthy wrote:
> >>>
> >>>>From: Brad Griffis <bgriffis@ti.com>
> >>>>
> >>>>In case of RTC+DDR resume, need to restore EMIF context
> >>>>before initiating hardware leveling.
> >>>>
> >>>>Signed-off-by: Brad Griffis <bgriffis@ti.com>
> >>>>Signed-off-by: Keerthy <j-keerthy@ti.com>
> >>>
> >>>This part off the series blows up the AM335x and older SoCs that also
> >>>re-use this code, please build test for all the "am33xx" boards and fix
> >>>the problems that arise, thanks!
> >>
> >>We should b able to enable TINY_FIT support and save some space. Patches are
> >>already available in internal tree. Keerthy can you post them along with this
> >>series?
> >
> >That's a good point but I wasn't clear enough sorry. They all fail to
> >compile due to undefined new macros.
>
> Tom,
>
> I have fixed with having am43 #ifdef for this particular patch.
> I built omap3/omap4 and am335x defconfis and they are building fine.
> I will boot test at least on am335x_evm and am335x_beagleboneblack before
> posting v2. Is it okay if i post v2 of this patch alone?
Can you repost the whole series please? Thanks!
--
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/20190426/8c1f0bb0/attachment.sig>
next prev parent reply other threads:[~2019-04-26 16:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 6:38 [U-Boot] [PATCH 0/6] board: ti: am43xx: Enable hardware leveling Keerthy
2019-04-12 6:38 ` [U-Boot] [PATCH 1/6] arm: mach-omap2: am33xx: ddr: programming of EXT_PHY_CTRL1 and EXT_PHY_CTRL1_SHADOW Keerthy
2019-04-12 6:38 ` [U-Boot] [PATCH 2/6] arm: mach-omap2: am33xx: ddr: Add 1ms delay to avoid L3 error Keerthy
2019-04-12 6:38 ` [U-Boot] [PATCH 3/6] arm: mach-omap2: am33xx: Enable HW Leveling in the rtc+ddr path Keerthy
2019-04-12 6:38 ` [U-Boot] [PATCH 4/6] arm: mach-omap2: am33xx: Disable EMIF_DEVOFF immediately before hw leveling Keerthy
2019-04-26 11:16 ` [U-Boot] [U-Boot, " Tom Rini
2019-04-26 11:53 ` Lokesh Vutla
2019-04-26 12:55 ` Tom Rini
2019-04-26 16:44 ` Keerthy
2019-04-26 16:46 ` Tom Rini [this message]
2019-04-26 16:50 ` Keerthy
2019-04-26 16:39 ` Keerthy
2019-04-26 14:11 ` Keerthy
2019-04-12 6:38 ` [U-Boot] [PATCH 5/6] arm: mach-omap2: am33xx: ddr: update value for ext_phy_ctrl_36 Keerthy
2019-04-12 6:38 ` [U-Boot] [PATCH 6/6] board: ti: am43xx: Enable hardware leveling Keerthy
2019-04-13 13:02 ` [U-Boot] [PATCH 0/6] " Tom Rini
2019-04-15 0:49 ` keerthy
2019-04-15 1:05 ` Tom Rini
2019-04-15 2:13 ` keerthy
2019-04-15 8:56 ` Keerthy
2019-04-15 9:22 ` Tero Kristo
2019-04-15 11:28 ` Tom Rini
2019-04-15 12:10 ` Keerthy
2019-04-15 12:14 ` Tom Rini
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=20190426164603.GS31207@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