public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Keerthy <j-keerthy@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/6] board: ti: am43xx: Enable hardware leveling
Date: Mon, 15 Apr 2019 17:40:27 +0530	[thread overview]
Message-ID: <769ff12b-b671-031d-2dc9-7a50a23e7e7a@ti.com> (raw)
In-Reply-To: <20190415112820.GU4664@bill-the-cat>



On 15/04/19 4:58 PM, Tom Rini wrote:
> On Mon, Apr 15, 2019 at 12:22:22PM +0300, Tero Kristo wrote:
>> On 15/04/2019 11:56, Keerthy wrote:
>>>
>>>
>>> On 15/04/19 7:43 AM, keerthy wrote:
>>>>
>>>>
>>>> On 4/15/2019 6:35 AM, Tom Rini wrote:
>>>>> 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?
>>>>
>>>> Okay i got your concern. Deep sleep 0 is currently working with software
>>>> leveling that will stop working with this patch series(hardware
>>>> leveling) applied on older kernels. EMIF tools application note
>>>> recommends hardware leveling over what existed previously.
>>>>
>>>> Hence i posted this series. Older kernels with this patch series Deep
>>>> sleep 0 feature will regress.
>>>
>>> Tom,
>>>
>>> We need hardware leveling as per EMIF document. So older kernels at best
>>> can backport the patches here:
>>>
>>> https://patchwork.kernel.org/patch/10882123/
>>> https://patchwork.kernel.org/patch/10882127/
>>>
>>> I do not see any other way to enable hardware leveling.
>>>
>>> Tero/Dave,
>>>
>>> Any concerns?
>>
>> Well, if we are to enable the feature, I can't see how we can avoid conflict
>> with older kernels. However, most of the time I would say people upgrade
>> their kernel before upgrading u-boot so this should be fine. If we are
>> really worried, we could maybe add the support to kernel first, wait some
>> time and merge the support to u-boot after that.
> 
> I assume that as the patches are working their way through -next now,
> we're also talking about older vendor tree kernels being where this did
> work?
> 

older kernels will have to port the above patches else Deep Sleep 0 will 
fail with newer u-boot with hardware leveling enabled. I assume they 
would be using older u-boot as well?

  reply	other threads:[~2019-04-15 12:10 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
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 [this message]
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=769ff12b-b671-031d-2dc9-7a50a23e7e7a@ti.com \
    --to=j-keerthy@ti.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