From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/6] board: ti: am43xx: Enable hardware leveling
Date: Sun, 14 Apr 2019 21:05:20 -0400 [thread overview]
Message-ID: <20190415010520.GT4664@bill-the-cat> (raw)
In-Reply-To: <5274f3fd-057e-04aa-5423-96ab6b304a28@ti.com>
On Mon, Apr 15, 2019 at 06:19:31AM +0530, keerthy wrote:
>
>
> On 4/13/2019 6:32 PM, Tom Rini wrote:
> >On Fri, Apr 12, 2019 at 12:08:14PM +0530, Keerthy wrote:
> >
> >>The series adds the support for hardware leveling. This needs the
> >>kernel to be patched with hardware leveling support and the
> >>kernel support is already in linux-next:
> >>
> >>https://patchwork.kernel.org/project/linux-omap/list/?series=100273
> >>
> >>Match recommended values from EMIF Tools app note:
> >>http://www.ti.com/lit/an/sprac70/sprac70.pdf
> >
> >What happens if you boot an old kernel with this series applied? I'm a
> >bit worried about applying something that breaks existing kernels,
> >thanks!
>
> Hi Tom,
>
> Deep Sleep 0 feature will fail as the corresponding hardware leveling
> patches will not be present.
So to be clear, some new functionality will not work, but there is no
functional regression?
--
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/20190414/c2c69e34/attachment.sig>
next prev parent reply other threads:[~2019-04-15 1:05 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
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 [this message]
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=20190415010520.GT4664@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