All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH v7 04/17] x86: apl: Add hostbridge driver
Date: Sun, 15 Dec 2019 08:36:49 +0800	[thread overview]
Message-ID: <CAEUhbmW6BaMoW68FwFgTskhNapvbBqO12bOJ9wWX=V0eP8ciBA@mail.gmail.com> (raw)
In-Reply-To: <20191208173929.v7.4.I5ba86662e42269ac50c05b6db34832a966dad79a@changeid>

On Mon, Dec 9, 2019 at 8:40 AM Simon Glass <sjg@chromium.org> wrote:
>
> This driver models the hostbridge as a northbridge. It simply sets up the
> graphics BAR. It supports of-platdata.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
> ---
>
> Changes in v7: None
> Changes in v6:
> - Fix comments for struct apl_hostbridge_platdata
>
> Changes in v5: None
> Changes in v4:
> - Avoid needing to know internals of pinctrl in this driver
> - Move code to pinctrl driver
> - Switch over to use pinctrl for pad init/config
>
> Changes in v3:
> - Move pad programming into the hostbridge to reduce TPL device-tree size
> - Use pci_get_devfn()
>
> Changes in v2: None
>
>  arch/x86/cpu/apollolake/Makefile     |   1 +
>  arch/x86/cpu/apollolake/hostbridge.c | 179 +++++++++++++++++++++++++++
>  2 files changed, 180 insertions(+)
>  create mode 100644 arch/x86/cpu/apollolake/hostbridge.c
>

applied to u-boot-x86/next, thanks!

  parent reply	other threads:[~2019-12-15  0:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09  0:40 [PATCH v7 04/17] x86: apl: Add hostbridge driver Simon Glass
2019-12-09  0:40 ` [PATCH v7 05/17] x86: apl: Add ITSS driver Simon Glass
2019-12-15  0:36   ` Bin Meng
2019-12-09  0:40 ` [PATCH v7 06/17] x86: apl: Add LPC driver Simon Glass
2019-12-15  0:38   ` Bin Meng
2019-12-09  0:40 ` [PATCH v7 07/17] x86: apl: Add PCH driver Simon Glass
2019-12-15  0:39   ` Bin Meng
2019-12-09  0:40 ` [PATCH v7 08/17] x86: apl: Add PUNIT driver Simon Glass
2019-12-15  0:40   ` Bin Meng
2019-12-09  0:40 ` [PATCH v7 09/17] spl: Add methods to find the position/size of next phase Simon Glass
2019-12-15  0:40   ` Bin Meng
2019-12-09  0:40 ` [PATCH v7 10/17] x86: apl: Add SPL loaders Simon Glass
2019-12-15  0:41   ` Bin Meng
2019-12-09  0:40 ` [PATCH v7 11/17] x86: apl: Add a CPU driver Simon Glass
2019-12-15  0:43   ` Bin Meng
2019-12-09  0:40 ` [PATCH v7 12/17] x86: apl: Add SPL/TPL init Simon Glass
2019-12-15  0:44   ` Bin Meng
2019-12-09  0:40 ` [PATCH v7 13/17] x86: apl: Add P2SB driver Simon Glass
2019-12-10 14:11   ` Bin Meng
2019-12-15  0:44     ` Bin Meng
2019-12-09  0:40 ` [PATCH v7 14/17] x86: apl: Add Kconfig and Makefile Simon Glass
2019-12-15  0:45   ` Bin Meng
2019-12-09  0:40 ` [PATCH v7 15/17] x86: apl: Add FSP structures Simon Glass
2019-12-15  0:46   ` Bin Meng
2019-12-09  0:40 ` [PATCH v7 16/17] x86: apl: Add FSP support Simon Glass
2019-12-15  0:46   ` Bin Meng
2019-12-09  0:40 ` [PATCH v7 17/17] x86: Add chromebook_coral Simon Glass
2019-12-15  0:47   ` Bin Meng
2019-12-15  0:36 ` Bin Meng [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-09  0:32 [PATCH v7 00/17] x86: Add initial support for apollolake Simon Glass
2019-12-09  0:32 ` [PATCH v7 04/17] x86: apl: Add hostbridge driver Simon Glass

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='CAEUhbmW6BaMoW68FwFgTskhNapvbBqO12bOJ9wWX=V0eP8ciBA@mail.gmail.com' \
    --to=bmeng.cn@gmail.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.