All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-marvell/master
Date: Mon, 11 Feb 2019 13:34:36 +0100	[thread overview]
Message-ID: <8e30d573-f41d-7280-5787-173bc68c5b43@denx.de> (raw)

Hi Tom,

please pull the following Marvell related patches, mostly board
specific changes and one platform build fix:

----------------------------------------------------------------
- Fix BUILD_TARGET for ARCH_MVEBU from Baruch
- Fix MVEBU PCIe reset issues from Baruch
- Increase DDR stability on x530 from Chris
----------------------------------------------------------------

Thanks,
Stefan


The following changes since commit dbe70c7d4e3d5c705a98d82952e05a591efd0683:

   Merge branch 'master' of git://git.denx.de/u-boot-sh (2019-02-10 08:11:53 -0500)

are available in the Git repository at:

   git://www.denx.de/git/u-boot-marvell.git

for you to fetch changes up to a6ac775bae7fad1534ffe2b20244b7e7106b12b0:

   ARM: mvebu: x530: use MV_DDR_FREQ_SAR (2019-02-11 09:39:12 +0100)

----------------------------------------------------------------
Baruch Siach (4):
       arm: mvebu: mcbin: dts: fix PCIe reset polarity
       pcie: designware: mvebu: fix reset release polarity
       arm: mvebu: cf gt-8k: dts: add PCIe slot reset support
       Kconfig: fix BUILD_TARGET for ARCH_MVEBU

Chris Packham (1):
       ARM: mvebu: x530: use MV_DDR_FREQ_SAR

  Kconfig                                     | 2 +-
  arch/arm/dts/armada-8040-clearfog-gt-8k.dts | 8 ++++++++
  arch/arm/dts/armada-8040-mcbin.dts          | 2 +-
  board/alliedtelesis/x530/x530.c             | 2 +-
  drivers/pci/pcie_dw_mvebu.c                 | 4 +++-
  5 files changed, 14 insertions(+), 4 deletions(-)

             reply	other threads:[~2019-02-11 12:34 UTC|newest]

Thread overview: 130+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 12:34 Stefan Roese [this message]
2019-02-11 22:41 ` [U-Boot] Please pull u-boot-marvell/master Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2019-11-14  7:39 Stefan Roese
2019-11-18  2:14 ` Tom Rini
2019-08-12 12:08 Stefan Roese
2019-08-13 16:50 ` Tom Rini
2019-07-11 16:01 Stefan Roese
2019-07-12 13:32 ` Tom Rini
2019-06-04  6:39 Stefan Roese
2019-06-05 14:24 ` Tom Rini
2019-05-27 11:35 Stefan Roese
2019-05-27 18:35 ` Tom Rini
2019-05-20  7:59 Stefan Roese
2019-05-20 17:53 ` Tom Rini
2019-05-09 10:08 Stefan Roese
2019-05-09 22:25 ` Tom Rini
2019-05-03 11:49 Stefan Roese
2019-05-04 17:01 ` Tom Rini
2019-04-26 10:58 Stefan Roese
2019-04-27 14:48 ` Tom Rini
2019-04-11 12:34 Stefan Roese
2019-04-11 14:49 ` Tom Rini
2019-04-11 14:51   ` Stefan Roese
2019-04-11 14:52     ` Tom Rini
2019-03-19 12:49 Stefan Roese
2019-03-20 13:46 ` Tom Rini
2019-02-05 13:36 Stefan Roese
2019-02-08  3:13 ` Tom Rini
2019-01-21 10:52 Stefan Roese
2019-01-22  2:29 ` Tom Rini
2018-12-21 15:31 Stefan Roese
2018-12-23 17:31 ` Tom Rini
2018-12-09 10:15 Stefan Roese
2018-12-09 21:44 ` Chris Packham
2018-12-09 22:11 ` Tom Rini
2018-11-30 14:45 Stefan Roese
2018-11-30 22:09 ` Tom Rini
2018-11-20 12:15 Stefan Roese
2018-11-20 21:48 ` Tom Rini
2018-09-19 15:12 Stefan Roese
2018-09-20 13:24 ` Tom Rini
2018-08-07 13:10 Stefan Roese
2018-08-08  1:35 ` Tom Rini
2018-06-05  9:33 Stefan Roese
2018-06-05 14:14 ` Tom Rini
2018-05-16 12:05 Stefan Roese
2018-05-16 15:37 ` Tom Rini
2018-05-17  8:36   ` Chris Packham
2018-05-17  8:45     ` Chris Packham
2018-05-17  8:48       ` Stefan Roese
2018-05-17  9:06         ` Chris Packham
2018-05-14 11:58 Stefan Roese
2018-05-14 15:11 ` Tom Rini
2018-05-14 15:16   ` Stefan Roese
2018-05-15  1:23     ` Chris Packham
2018-04-17  8:53 Stefan Roese
2018-04-17 19:39 ` Tom Rini
2018-01-29 12:42 Stefan Roese
2018-01-29 16:55 ` Tom Rini
2018-01-20  9:01 Stefan Roese
2018-01-20 16:58 ` Tom Rini
2018-01-10 11:40 Stefan Roese
2018-01-10 16:42 ` Tom Rini
2017-11-30 12:33 Stefan Roese
2017-11-30 18:45 ` Tom Rini
2017-11-16 13:09 Stefan Roese
2017-11-17  1:52 ` Tom Rini
2017-09-26  8:55 Stefan Roese
2017-09-27  2:45 ` Tom Rini
2017-08-30  8:06 Stefan Roese
2017-09-01 16:42 ` Tom Rini
2017-08-21  9:43 Stefan Roese
2017-08-22 20:53 ` Tom Rini
2017-08-10  8:26 Stefan Roese
2017-08-10 20:17 ` Tom Rini
2017-08-08 12:26 Stefan Roese
2017-08-09 15:26 ` Tom Rini
2017-07-12  6:00 Stefan Roese
2017-07-12 14:25 ` Tom Rini
2017-06-23  8:42 Stefan Roese
2017-06-23 13:22 ` Tom Rini
2017-05-31  9:02 Stefan Roese
2017-06-01 12:10 ` Tom Rini
2017-05-09 14:45 Stefan Roese
2017-05-09 23:49 ` Tom Rini
2017-03-29  9:24 Stefan Roese
2017-04-04 20:00 ` Tom Rini
2017-03-24  5:58 Stefan Roese
2017-03-24 17:36 ` Tom Rini
2017-02-17 11:15 Stefan Roese
2017-02-17 22:56 ` Tom Rini
2017-02-01 11:46 Stefan Roese
2017-02-01 21:33 ` Tom Rini
2017-01-25  7:46 Stefan Roese
2017-01-27  1:43 ` Tom Rini
2016-12-21  9:56 Stefan Roese
2016-12-21 13:06 ` Tom Rini
2016-12-12 10:47 Stefan Roese
2016-12-12 15:56 ` Tom Rini
2016-12-05 13:01 Stefan Roese
2016-12-05 16:01 ` Tom Rini
2016-12-01 12:57 Stefan Roese
2016-12-01 18:16 ` Tom Rini
2016-10-09  9:05 Stefan Roese
2016-10-13  0:48 ` Tom Rini
2016-09-27 15:33 Stefan Roese
2016-09-27 21:32 ` Tom Rini
2016-09-24  8:13 Stefan Roese
2016-09-24 16:04 ` Tom Rini
2016-08-26  6:46 Stefan Roese
2016-08-26 14:52 ` Tom Rini
2016-05-31  6:08 Stefan Roese
2016-05-31 14:50 ` Tom Rini
2016-05-20  9:10 Stefan Roese
2016-05-23 22:12 ` Tom Rini
2016-04-12  9:19 Stefan Roese
2016-04-12 17:23 ` Tom Rini
2016-04-12 17:23 ` Tom Rini
2016-04-06 13:47 Stefan Roese
2016-04-06 14:47 ` Tom Rini
2016-04-04 12:07 Stefan Roese
2016-04-05  0:01 ` Tom Rini
2016-03-24 10:09 Stefan Roese
2016-03-25 22:59 ` Tom Rini
2016-03-14 22:37 Luka Perkov
2016-03-15 11:52 ` Tom Rini
2016-01-27  6:58 Stefan Roese
2016-01-28 23:18 ` Tom Rini
2016-01-14 13:28 Stefan Roese
2016-01-14 18:04 ` 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=8e30d573-f41d-7280-5787-173bc68c5b43@denx.de \
    --to=sr@denx.de \
    --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.