All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PULL] u-boot-socfpga/master
Date: Sun, 21 Apr 2019 21:37:37 +0200	[thread overview]
Message-ID: <d1e2730c-f8f6-45b7-d384-130986419b0e@denx.de> (raw)
In-Reply-To: <CAAh8qszpJJ-=U00hWeLn4wz4zR16wuXuQvUwODouYvY660WyjQ@mail.gmail.com>

On 4/19/19 10:47 PM, Simon Goldschmidt wrote:
> 
> 
> Marek Vasut <marex at denx.de <mailto:marex@denx.de>> schrieb am Di., 16.
> Apr. 2019, 23:14:
> 
>     On 4/16/19 10:08 PM, Simon Goldschmidt wrote:
>     > Hi Marek,
>     >
>     > Am 12.04.2019 um 12:31 schrieb Marek Vasut:
>     >> On 4/11/19 10:07 PM, Simon Goldschmidt wrote:
>     >>>
>     >>>
>     >>> Marek Vasut <marex at denx.de <mailto:marex@denx.de>
>     <mailto:marex at denx.de <mailto:marex@denx.de>>> schrieb am Do., 11.
>     >>> Apr. 2019, 21:59:
>     >>>
>     >>>      On 4/11/19 9:30 PM, Simon Goldschmidt wrote:
>     >>>      >
>     >>>      >
>     >>>      > On 11.04.19 21:03, Tom Rini wrote:
>     >>>      >> On Thu, Apr 11, 2019 at 08:49:38PM +0200, Simon Goldschmidt
>     >>> wrote:
>     >>>      >>>
>     >>>      >>>
>     >>>      >>> On 11.04.19 20:20, Tom Rini wrote:
>     >>>      >>>> On Thu, Apr 11, 2019 at 08:19:38PM +0200, Marek Vasut
>     wrote:
>     >>>      >>>>> On 4/11/19 8:17 PM, Tom Rini wrote:
>     >>>      >>>>>> On Wed, Apr 10, 2019 at 04:46:28PM +0200, Marek
>     Vasut wrote:
>     >>>      >>>>>>
>     >>>      >>>>>>> The following changes since commit
>     >>>      >>>>>>> 3c99166441bf3ea325af2da83cfe65430b49c066:
>     >>>      >>>>>>>
>     >>>      >>>>>>>    Prepare v2019.04 (2019-04-08 21:40:40 -0400)
>     >>>      >>>>>>>
>     >>>      >>>>>>> are available in the Git repository at:
>     >>>      >>>>>>>
>     >>>      >>>>>>>    git://git.denx.de/u-boot-socfpga.git
>     <http://git.denx.de/u-boot-socfpga.git>
>     >>>      <http://git.denx.de/u-boot-socfpga.git> master
>     >>>      >>>>>>>
>     >>>      >>>>>>> for you to fetch changes up to
>     >>>      >>>>>>> ef8679b24ec6226b7198e06747ff047a16030ca4:
>     >>>      >>>>>>>
>     >>>      >>>>>>>    arm: dts: Stratix10: Add QSPI node (2019-04-09
>     13:11:06
>     >>>      +0200)
>     >>>      >>>>>>>
>     >>>      >>>>>>
>     >>>      >>>>>> Arg, sorry I didn't see this sooner:
>     >>>      >>>>>>         arm:  w+   socfpga_arria10
>     >>>      >>>>>> +(socfpga_arria10)
>     >>>      >>>>>> +(socfpga_arria10) WARNING: unmet direct dependencies
>     >>>      detected for
>     >>>      >>>>>> ALTERA_SDRAM
>     >>>      >>>>>> +(socfpga_arria10)   Depends on [n]: RAM [=n] &&
>     >>>      >>>>>> (TARGET_SOCFPGA_GEN5 [=n] || TARGET_SOCFPGA_ARRIA10
>     [=y])
>     >>>      >>>>>> +(socfpga_arria10)   Selected by [y]:
>     >>>      >>>>>> +(socfpga_arria10)   - TARGET_SOCFPGA_ARRIA10 [=y]
>     && ARM
>     >>> [=y] &&
>     >>>      >>>>>> ARCH_SOCFPGA [=y]
>     >>>      >>>>>
>     >>>      >>>>> Is this coming from this PR or not ?
>     >>>      >>>>
>     >>>      >>>> Yes, this PR.  Top of tree + this PR only.
>     >>>      >>>
>     >>>      >>> It's not only top of tree + this PR, it also fails for pure
>     >>>      >>> u-boot-socfpga/master.
>     >>>      >>>
>     >>>      >>> Seems like this bug has been introduced when I made the
>     gen5
>     >>> driver
>     >>>      >>> depend
>     >>>      >>> on RAM. Unfortunately, all the drivers use one Kconfig item
>     >>>      (although
>     >>>      >>> these
>     >>>      >>> are totally different drivers) but now only gen5 depends on
>     >>> RAM. Is
>     >>>      >>> there
>     >>>      >>> any Kconfig magic to fix this without duplicating the
>     config
>     >>> item
>     >>>      >>> entries?
>     >>>      >>
>     >>>      >> I think you may want something more like:
>     >>>      >> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
>     >>>      >> index 04a207c9403e..4a23e327dfb4 100644
>     >>>      >> --- a/arch/arm/Kconfig
>     >>>      >> +++ b/arch/arm/Kconfig
>     >>>      >> @@ -821,14 +821,12 @@ config ARCH_SOCFPGA
>     >>>      >>       select DM_SERIAL
>     >>>      >>       select ENABLE_ARM_SOC_BOOT0_HOOK if
>     TARGET_SOCFPGA_GEN5 ||
>     >>>      >> TARGET_SOCFPGA_ARRIA10
>     >>>      >>       select OF_CONTROL
>     >>>      >> -    select RAM if TARGET_SOCFPGA_GEN5
>     >>>      >>       select SPL_DM_RESET if DM_RESET
>     >>>      >>       select SPL_DM_SERIAL
>     >>>      >>       select SPL_LIBCOMMON_SUPPORT
>     >>>      >>       select SPL_LIBGENERIC_SUPPORT
>     >>>      >>       select SPL_NAND_SUPPORT if SPL_NAND_DENALI
>     >>>      >>       select SPL_OF_CONTROL
>     >>>      >> -    select SPL_RAM if TARGET_SOCFPGA_GEN5
>     >>>      >>       select SPL_SEPARATE_BSS if TARGET_SOCFPGA_STRATIX10
>     >>>      >>       select SPL_SERIAL_SUPPORT
>     >>>      >>       select SPL_WATCHDOG_SUPPORT
>     >>>      >> diff --git a/drivers/ddr/altera/Kconfig
>     >>> b/drivers/ddr/altera/Kconfig
>     >>>      >> index 7370d4133a67..8f60b56eb848 100644
>     >>>      >> --- a/drivers/ddr/altera/Kconfig
>     >>>      >> +++ b/drivers/ddr/altera/Kconfig
>     >>>      >> @@ -1,6 +1,7 @@
>     >>>      >>   config ALTERA_SDRAM
>     >>>      >>       bool "SoCFPGA DDR SDRAM driver"
>     >>>      >> -    depends on RAM
>     >>>      >>       depends on TARGET_SOCFPGA_GEN5 ||
>     TARGET_SOCFPGA_ARRIA10
>     >>>      >> +    select RAM if TARGET_SOCFPGA_GEN5
>     >>>      >> +    select SPL_RAM if TARGET_SOCFPGA_GEN5
>     >>>      >>       help
>     >>>      >>         Enable DDR SDRAM controller for the SoCFPGA devices.
>     >>>      >>
>     >>>      >> But I didn't test anything other than
>     socfpga_arria10/arria5 as
>     >>>      >> building.
>     >>>      >
>     >>>      > Tom,
>     >>>      > Thanks for the hint. I did just that and it works for me
>     >>> (cyclone5).
>     >>>      > As only this platform is affected by this patch, it should be
>     >>> fine.
>     >>>      >
>     >>>      > Marek,
>     >>>      > how should we proceed? I pushed the change as suggested
>     by Tom
>     >>> to:
>     >>>      >
>     >>>      > https://github.com/goldsimon/u-boot.git
>     >>>      >
>     >>>      > or I could send v5 of the series that broke arria10...?
>     >>>
>     >>>      Send me a single patch on top of u-boot-socfpga/master,
>     I'll add
>     >>> it and
>     >>>      that should take care of it. It would also make things well
>     >>> documented
>     >>>      for other people who run into this.
>     >>>
>     >>>
>     >>> To make it clear, patch 6/12 of this PR is ok for gen5 but breaks
>     >>> arria10. This is not something anyone could run into as it's
>     new. I'd
>     >>> rather fix the patches before merging them to master (keep things
>     >>> bisectable for a10).
>     >>>
>     >>> Unfortunately, I'll be more or less offline until Tuesday. If my
>     github
>     >>> branch isn't enough, I'll send something when I'm back with PC
>     access.
>     >>
>     >> I can squash the patch(es), that's fine. I just need the patch
>     posted to
>     >> the ML.
>     >
>     > Ok, I'm back online. I've just sent the updated patch to fix the build
>     > issue to the ML (see https://patchwork.ozlabs.org/patch/1086623/).
>     This
>     > one is meant as replacement for 82b40a096410 in current
>     > u-boot-socfpga/master.
>     >
>     > Let me know if there's anything else missing. Once this is
>     applied, I'll
>     > prepare a PR for the next batch.
> 
>     I was hoping for a patch I can squash into the previous one, so the diff
>     would be easily visible. Oh well, applied, let's see what CI has to
>     say now.
> 
> 
> Ok, thanks. So did CI complain? All I saw seemed good. Should I send my
> pending patches on top of master once this PR is through or on top of
> u-boot-socfpga?

Travis crashed once, so I had to restart it. Now it succeeded.

Feel free to send me a PR on top of u-boot-socfpga/master .

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2019-04-21 19:37 UTC|newest]

Thread overview: 192+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 14:46 [U-Boot] [PULL] u-boot-socfpga/master Marek Vasut
2019-04-11 18:17 ` Tom Rini
2019-04-11 18:19   ` Marek Vasut
2019-04-11 18:20     ` Tom Rini
2019-04-11 18:49       ` Simon Goldschmidt
2019-04-11 19:03         ` Tom Rini
2019-04-11 19:30           ` Simon Goldschmidt
2019-04-11 19:59             ` Marek Vasut
2019-04-11 20:07               ` Simon Goldschmidt
2019-04-12 10:31                 ` Marek Vasut
2019-04-16 20:08                   ` Simon Goldschmidt
2019-04-16 21:12                     ` Marek Vasut
2019-04-19 20:47                       ` Simon Goldschmidt
2019-04-21 19:37                         ` Marek Vasut [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-28 10:17 Marek Vasut
2019-12-02 15:16 ` Tom Rini
2019-11-22 12:41 Marek Vasut
2019-11-22 22:16 ` Tom Rini
2019-11-15  9:34 Marek Vasut
2019-11-15  9:44 ` Simon Goldschmidt
2019-11-15  9:52   ` Marek Vasut
2019-10-14 23:45 Marek Vasut
2019-10-15  3:05 ` Tom Rini
2019-08-17 12:19 Marek Vasut
2019-08-17 17:47 ` Tom Rini
2019-07-29 12:34 Marek Vasut
2019-07-30  1:21 ` Tom Rini
2019-06-14 10:45 Marek Vasut
2019-06-17 15:19 ` Tom Rini
2019-05-26 23:11 Marek Vasut
2019-05-27 18:35 ` Tom Rini
2019-05-15 22:53 Marek Vasut
2019-05-17 11:15 ` Tom Rini
2019-05-11 23:56 Marek Vasut
2019-05-14 14:07 ` Tom Rini
2019-05-07  3:43 Marek Vasut
2019-05-07 18:13 ` Tom Rini
2019-05-03 15:10 Marek Vasut
2019-05-04 17:01 ` Tom Rini
2019-04-26  9:31 Marek Vasut
2019-04-27 14:48 ` Tom Rini
2019-04-21 19:38 Marek Vasut
2019-04-22 13:23 ` Tom Rini
2019-03-26 17:44 Marek Vasut
2019-03-29  1:24 ` Tom Rini
2019-03-21 15:42 Marek Vasut
2019-03-22 11:25 ` Tom Rini
2019-03-18  3:08 Marek Vasut
2019-03-19 20:50 ` Tom Rini
2019-03-10 13:27 Marek Vasut
2019-03-11 19:41 ` Tom Rini
2019-02-28 21:24 Marek Vasut
2019-03-01 12:59 ` Tom Rini
2019-02-19  2:48 Marek Vasut
2019-02-20  1:56 ` Tom Rini
2019-01-11 14:52 Marek Vasut
2019-01-12 20:13 ` Tom Rini
2018-12-21 12:42 Marek Vasut
2018-12-23 17:31 ` Tom Rini
2018-12-10  4:52 Marek Vasut
2018-12-10 15:17 ` Tom Rini
2018-11-29 20:18 Marek Vasut
2018-11-30 16:19 ` Tom Rini
2018-10-31 20:36 Marek Vasut
2018-11-01 11:47 ` Tom Rini
2018-10-19 10:29 Marek Vasut
2018-10-19 14:12 ` Tom Rini
2018-10-19 14:16   ` Marek Vasut
2018-10-05 21:26 Marek Vasut
2018-10-06 12:57 ` Tom Rini
2018-09-16  1:12 Marek Vasut
2018-09-17 12:03 ` Tom Rini
2018-08-24 18:25 Marek Vasut
2018-08-25 13:16 ` Tom Rini
2018-08-17 10:08 Marek Vasut
2018-08-17 13:56 ` Tom Rini
2018-07-26  7:36 Marek Vasut
2018-07-26 19:53 ` Tom Rini
2018-07-13  9:04 Marek Vasut
2018-07-14  1:10 ` Tom Rini
2018-05-31 18:06 Marek Vasut
2018-06-01  0:23 ` Tom Rini
2018-06-01  6:31   ` Marek Vasut
2018-06-01  7:30     ` Ley Foon Tan
2018-06-01  7:49       ` Marek Vasut
2018-06-01  8:03         ` Ley Foon Tan
2018-06-01  8:08           ` Marek Vasut
2018-05-20 10:05 Marek Vasut
2018-05-21  1:59 ` Tom Rini
2018-05-11  2:20 Marek Vasut
2018-05-11 11:09 ` Tom Rini
2018-04-26 23:11 Marek Vasut
2018-04-27 11:20 ` Tom Rini
2018-04-17 18:26 Marek Vasut
2018-04-18 20:24 ` Tom Rini
2018-03-01 17:35 Marek Vasut
2018-03-02  2:32 ` Tom Rini
2018-02-16 15:59 Marek Vasut
2018-02-17 20:52 ` Tom Rini
2018-01-27 19:37 Marek Vasut
2018-01-28  2:54 ` Tom Rini
2018-01-11  1:58 Marek Vasut
2018-01-11 18:42 ` Tom Rini
2017-12-13  7:46 Marek Vasut
2017-12-14 20:45 ` Tom Rini
2017-11-28  7:33 Marek Vasut
2017-11-28 21:53 ` Tom Rini
2017-09-23 13:14 Marek Vasut
2017-09-24 14:40 ` Tom Rini
2017-07-29 15:27 Marek Vasut
2017-07-30  1:06 ` Tom Rini
2017-05-18  9:42 Marek Vasut
2017-05-19  0:38 ` Tom Rini
2017-04-25 10:49 Marek Vasut
2017-04-25 20:10 ` Tom Rini
2017-04-14 12:10 Marek Vasut
2017-04-14 21:09 ` Tom Rini
2017-02-08 23:38 Marek Vasut
2017-02-09 19:50 ` Tom Rini
2016-12-06  4:53 Marek Vasut
2016-12-08 14:31 ` Tom Rini
2016-10-29 18:01 Marek Vasut
2016-10-30 12:11 ` Tom Rini
2016-08-07 19:55 Marek Vasut
2016-08-08 17:08 ` Tom Rini
2016-07-02  1:42 Marek Vasut
2016-07-05  2:44 ` Tom Rini
2016-06-18  0:43 Marek Vasut
2016-06-19 14:12 ` Tom Rini
2016-06-02 13:19 Marek Vasut
2016-06-03 13:57 ` Tom Rini
2016-05-07  1:42 Marek Vasut
2016-05-11 16:23 ` Tom Rini
2016-05-11 19:20   ` Marek Vasut
2016-05-12  2:02     ` Tom Rini
2016-04-20  9:44 Marek Vasut
2016-04-21 11:25 ` Tom Rini
2016-04-10 19:18 Marek Vasut
2016-04-11 15:02 ` Tom Rini
2016-03-20 20:41 Marek Vasut
2016-03-21  1:27 ` Tom Rini
2016-02-24 18:14 Marek Vasut
2016-02-25 15:23 ` Tom Rini
2016-02-04 11:44 Marek Vasut
2016-02-04 17:39 ` Tom Rini
2016-01-16  6:09 Marek Vasut
2016-01-16 19:35 ` Tom Rini
2015-12-23  3:15 Marek Vasut
2015-12-23 15:27 ` Marek Vasut
2015-12-27 15:10   ` Tom Rini
2015-12-27 15:10 ` Tom Rini
2015-12-20  3:01 Marek Vasut
2015-12-21 14:34 ` Tom Rini
2015-12-06 23:17 Marek Vasut
2015-12-07 19:05 ` Tom Rini
2015-11-30 12:31 Marek Vasut
2015-11-30 20:17 ` Tom Rini
2015-11-05  2:50 Marek Vasut
2015-11-05 15:50 ` Tom Rini
2015-10-17  0:13 Marek Vasut
2015-10-17  0:22 ` Tom Rini
2015-09-23  1:56 Marek Vasut
2015-09-24  8:27 ` Marek Vasut
2015-09-24 21:10   ` Tom Rini
2015-09-12 18:26 Marek Vasut
2015-09-13  1:44 ` Tom Rini
2015-09-07 12:13 Marek Vasut
2015-09-08  0:19 ` Tom Rini
2015-08-23 10:02 Marek Vasut
2015-08-24 13:44 ` Tom Rini
2015-08-08 12:24 Marek Vasut
2015-08-09  0:19 ` Tom Rini
2015-08-09  0:22   ` Marek Vasut
2015-05-07 22:58 Marek Vasut
2015-05-10 14:07 ` Tom Rini
2015-04-29  0:39 Marek Vasut
2015-04-29 14:28 ` Tom Rini
2015-02-17 20:11 Marek Vasut
2015-02-18  3:04 ` Tom Rini
2015-02-18 21:34   ` Marek Vasut
2015-03-05 20:06   ` Marek Vasut
2015-03-06 15:43     ` Tom Rini
2014-12-30 21:32 Marek Vasut
2015-01-01 14:55 ` Tom Rini
2014-12-11 12:53 Marek Vasut
2014-12-11 17:02 ` Marek Vasut
2014-12-16 14:34   ` Marek Vasut
2014-12-17  0:45     ` Tom Rini
2014-11-11 17:20 Marek Vasut
2014-11-13 15:33 ` Tom Rini
2014-10-27  1:28 Marek Vasut
2014-10-27 14:32 ` 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=d1e2730c-f8f6-45b7-d384-130986419b0e@denx.de \
    --to=marex@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.