All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] omap3: Variant and revision checks for ARM Cortex-A8 errata workarounds
Date: Tue, 24 Feb 2015 17:02:12 -0600	[thread overview]
Message-ID: <54ED02F4.5070605@ti.com> (raw)
In-Reply-To: <1424794176.2496.9.camel@collins>

On 02/24/2015 10:09 AM, Paul Kocialkowski wrote:
> Le mardi 24 f?vrier 2015 ? 09:22 -0600, Nishanth Menon a ?crit :
>> On Tue, Feb 24, 2015 at 6:02 AM, Paul Kocialkowski <contact@paulk.fr> wrote:
>>> Le lundi 23 f?vrier 2015 ? 16:43 -0600, Nishanth Menon a ?crit :
>>>> On Mon, Feb 23, 2015 at 4:21 PM, Tom Rini <trini@ti.com> wrote:
>>>>> On Mon, Feb 23, 2015 at 08:16:44PM +0100, Paul Kocialkowski wrote:
>>>>>
>>>>>> Not every version and revision of the Cortex-A8 ARM core requires the same
>>>>>> errata workarounds. In addition, enabling those requires to have similar
>>>>>> workarounds enabled in the kernel or it will cause numerous segmentation faults.
>>>>>>
>>>>>> This enables those workarounds when they are needed, according to what is done
>>>>>> in Linux.
>>>>>>
>>>>>> Follow-up to the discussion from July 2013:
>>>>>> http://lists.denx.de/pipermail/u-boot/2013-July/158377.html
>>>>>>
>>>>>> Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
>>>>>
>>>>> Nishanth, any comments here, since you've been thinking about errata
>>>>> stuff lately?  Thanks!
>>>>>
>>>>> Reviewed-by: Tom Rini <trini@ti.com>
>>>>>
>>>>
>>>> I would probably go with v7 start code triggering the logic. even
>>>> though the secure logic is probably unique..
>>>
>>> It does seem like the secure logic is specific to the OMAP, even though
>>> the GP part (omap3_gp_romcode_call) seems to be generic.
>>>
>>> I don't think it would fit well in common v7 code and overall, I don't
>>> think I have sufficient knowledge of those issues to take the decision
>>> to move that code around.
>>>
>>> Hence, I'll keep my proposal to what it is now, and let someone else
>>> move the code around in the future if they feel the need to.
>>
>> Do you mind if i took a shot at it? would be great if you could test the same.
> 
> Alright, please go ahead! I'm available to test any patch on my omap
> 3630 device.
> 

Alright, the series should now include OMAP3 as well.. Sorry about
confusion when list blocked me for too many cc folks etc.. anyways..

https://patchwork.ozlabs.org/patch/443261/
https://patchwork.ozlabs.org/patch/443264/
https://patchwork.ozlabs.org/patch/443268/
https://patchwork.ozlabs.org/patch/443265/
https://patchwork.ozlabs.org/patch/443263/
https://patchwork.ozlabs.org/patch/443262/
https://patchwork.ozlabs.org/patch/443267/
https://patchwork.ozlabs.org/patch/443266/
https://patchwork.ozlabs.org/patch/443260/

-- 
Regards,
Nishanth Menon

      reply	other threads:[~2015-02-24 23:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-22 11:36 [U-Boot] [PATCH] omap3: ARM Cortex-A8 errata workarounds config option Paul Kocialkowski
2015-02-22 12:06 ` Igor Grinberg
2015-02-22 15:45   ` Paul Kocialkowski
2015-02-22 15:55     ` Paul Kocialkowski
2015-02-22 16:02     ` Paul Kocialkowski
2015-02-22 16:42       ` [U-Boot] [PATCH v2] omap3: Variant and revision checks for ARM Cortex-A8 errata workarounds Paul Kocialkowski
2015-02-23 11:09         ` Igor Grinberg
2015-02-23 15:07           ` Paul Kocialkowski
2015-02-23 19:16             ` [U-Boot] [PATCH] " Paul Kocialkowski
2015-02-23 22:21               ` Tom Rini
2015-02-23 22:43                 ` Nishanth Menon
2015-02-24 12:02                   ` Paul Kocialkowski
2015-02-24 15:22                     ` Nishanth Menon
2015-02-24 16:09                       ` Paul Kocialkowski
2015-02-24 23:02                         ` 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=54ED02F4.5070605@ti.com \
    --to=nm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.