All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] x86: baytrail: Configure FSP UPD from device tree
Date: Sat, 8 Aug 2015 10:18:00 -0600	[thread overview]
Message-ID: <CAPnjgZ2uK=WkzA1D89Qp76bS8=HnMkJOA754-PLkvPWfvLO+vQ@mail.gmail.com> (raw)
In-Reply-To: <CAEUhbmU7wvJdBqK7Q3tGBugOM5n6BVuM5Dga_jsODXK3ZEoiag@mail.gmail.com>

Hi,

On 7 August 2015 at 06:44, Bin Meng <bmeng.cn@gmail.com> wrote:
> On Fri, Aug 7, 2015 at 8:36 PM, Andrew Bradford
> <andrew@bradfordembedded.com> wrote:
>> From: Andrew Bradford <andrew.bradford@kodakalaris.com>
>>
>> Allow for configuration of FSP UPD from the device tree which will
>> override any settings which the FSP was built with itself.
>>
>> Modify the MinnowMax and BayleyBay boards to transfer sensible UPD
>> settings from the Intel FSPv4 Gold release to the respective dts files,
>> with the condition that the memory-down parameters for MinnowMax are
>> also used.
>>
>> Signed-off-by: Andrew Bradford <andrew.bradford@kodakalaris.com>
>> ---
>>
>
> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
> Tested-by: Bin Meng <bmeng.cn@gmail.com>
>

Acked-by: Simon Glass <sjg@chromium.org>
Tested on minnowmax:
Tested-by: Simon Glass <sjg@chromium.org>

I found that I need to remove two properties from the minnowmax.dts:

- fsp,enable-xhci needs to be removed as this does not work in U-Boot
at present and stops EHCI from working
- fsp,mrc-debug-msg needs to be removed to prevent debug information
being displayed

I plan to apply this with these changes - please let me know if this
doesn't suit.

Regards,
Simon

  reply	other threads:[~2015-08-08 16:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 12:36 [U-Boot] [PATCH v4] x86: baytrail: Configure FSP UPD from device tree Andrew Bradford
2015-08-07 12:44 ` Bin Meng
2015-08-08 16:18   ` Simon Glass [this message]
2015-08-09  1:08     ` Andrew Bradford
2015-08-09  2:52       ` Bin Meng
2015-08-10 11:32         ` Andrew Bradford
2015-08-11  2:53           ` Bin Meng
2015-08-11  3:07             ` Simon Glass
2015-08-11  3:17               ` Bin Meng
2015-08-11  3:24                 ` Simon Glass
2015-08-11  3:31                   ` Bin Meng
2015-08-11  3:39                     ` Simon Glass
2015-08-11 12:27                       ` Andrew Bradford
2015-08-11 12:08               ` Andrew Bradford
2015-08-11 14:06                 ` Simon Glass
2015-08-11 15:20                   ` Andrew Bradford
2015-08-12  3:54                     ` Simon Glass
2015-08-12 11:52                       ` Andrew Bradford
2015-08-12 14:18                         ` Simon Glass
2015-08-13  7:55                       ` Bin Meng
2016-03-08 16:45                       ` Stefan Roese
2016-03-08 16:54                         ` Simon Glass
2016-03-08 17:41                           ` Stefan Roese
2016-03-08 23:33                             ` Simon Glass
2016-03-09 16:15                               ` Stefan Roese
2016-03-09 17:11                                 ` Simon Glass
2016-03-11 16:28                                   ` Stefan Roese
2016-03-12  0:33                                     ` Simon Glass
2015-08-13  7:50           ` Bin Meng
2015-08-09  2:47     ` Bin Meng

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='CAPnjgZ2uK=WkzA1D89Qp76bS8=HnMkJOA754-PLkvPWfvLO+vQ@mail.gmail.com' \
    --to=sjg@chromium.org \
    --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.