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 2/5] board_r: Do not initialize IDE when DM BLK is on
Date: Wed, 20 Jun 2018 11:51:50 -0600	[thread overview]
Message-ID: <CAPnjgZ1ZkVx9FhnWZP3zOsE9EwJSTfgQB5aL3-pAhc-KaWvhuw@mail.gmail.com> (raw)
In-Reply-To: <1529240273-32045-2-git-send-email-bmeng.cn@gmail.com>

On 17 June 2018 at 06:57, Bin Meng <bmeng.cn@gmail.com> wrote:
> With driver model philosophy, we should avoid explicitly calling
> driver initialization routine during boot. This updates the ram
> init sequence table to exclude the IDE initialization for DM BLK.
>
> Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
> ---
>
>  common/board_r.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>

Reviewed-by: Simon Glass <sjg@chromium.org>

  reply	other threads:[~2018-06-20 17:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-17 12:57 [U-Boot] [PATCH 1/5] x86: qemu: Change default vesa mode to 1024x768x32 Bin Meng
2018-06-17 12:57 ` [U-Boot] [PATCH 2/5] board_r: Do not initialize IDE when DM BLK is on Bin Meng
2018-06-20 17:51   ` Simon Glass [this message]
2018-06-22  4:24     ` Bin Meng
2018-06-17 12:57 ` [U-Boot] [PATCH 3/5] efi: stub: Move the use_uart assignment immediately after exit_boot_services() call Bin Meng
2018-06-17 12:57 ` [U-Boot] [PATCH 4/5] x86: efi-x86_payload: Enumerate PCI bus during early boot Bin Meng
2018-06-20 17:51   ` Simon Glass
2018-06-21 11:19     ` Bin Meng
2018-06-21 19:45       ` Simon Glass
2018-06-22  4:24         ` Bin Meng
2018-06-17 12:57 ` [U-Boot] [PATCH 5/5] x86: efi-x86_payload: Enable usb keyboard during boot Bin Meng
2018-06-20 17:51   ` Simon Glass
2018-06-22  4:24     ` Bin Meng
2018-06-20 17:51 ` [U-Boot] [PATCH 1/5] x86: qemu: Change default vesa mode to 1024x768x32 Simon Glass
2018-06-22  4:24   ` 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=CAPnjgZ1ZkVx9FhnWZP3zOsE9EwJSTfgQB5aL3-pAhc-KaWvhuw@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.