public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 08/10] arm: socfpga: Add Altera Arria V DK support
Date: Tue, 10 Feb 2015 16:50:45 +0100	[thread overview]
Message-ID: <201502101650.45728.marex@denx.de> (raw)
In-Reply-To: <54D99CCF.6050806@denx.de>

On Tuesday, February 10, 2015 at 06:53:19 AM, Stefan Roese wrote:
> On 09.02.2015 20:09, Marek Vasut wrote:
> > On Monday, February 02, 2015 at 08:47:52 AM, Stefan Roese wrote:
> >> On 30.01.2015 23:08, Marek Vasut wrote:
> >>> Add support for the Altera Arria V development kit.
> >>> 
> >>> Signed-off-by: Marek Vasut <marex@denx.de>
> >>> Cc: Chin Liang See <clsee@opensource.altera.com>
> >>> Cc: Dinh Nguyen <dinguyen@opensource.altera.com>
> >>> Cc: Pavel Machek <pavel@denx.de>
> >>> Cc: Stefan Roese <sr@denx.de>
> >>> Cc: Vince Bridgers <vbridger@opensource.altera.com>
> >>> ---
> > 
> > [...]
> > 
> >>> +/* The rest of the configuration is shared */
> >>> +#include <configs/socfpga_common.h>
> >>> +
> >>> +#endif	/* __CONFIG_SOCFPGA_ARRIA5_H__ */
> >> 
> >> Without really diff'ing this file with socfpga_cyclone5.h, I'm pretty
> >> sure that they share many lines. Wouldn't it make sense to move those
> >> common defines / configs to a common file instead (socfpga_common.h)?
> > 
> > Hi!
> > 
> > I agree they share a lot, but I would not recommend moving any of this
> > into socfpga_common.h . Not all boards which include socfpga_common.h
> > will want all that's common between socfpga_cyclone5.h and
> > socfpga_arria5.h as well.
> > 
> > We need to switch to DM really soon, since without DM, we cannot really
> > make any "common" configuration. The socfpga_cyclone5.h file in fact
> > represents a configuration for SoCDK with Cyclone 5, same for Arria 5.
> > 
> > Unless you have any suggestion, I'd just apply this stuff as is for now
> > with the note that these config files must be cleaned up once DM is in
> > place. Or do you have any suggestions please ?
> 
> No. Please go ahead with this series. We can merge stuff later as well.
> Once we have better view on how this multi-board support for SoCFPGA
> will really end up.

Yeah, I'm kinda tempted to merge it as-is, but I wanted to collect more
feedback, since this was a discussed change. Thanks!

Best regards,
Marek Vasut

  reply	other threads:[~2015-02-10 15:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 22:08 [U-Boot] [PATCH 01/10] arm: socfpga: Minor coding style fix Marek Vasut
2015-01-30 22:08 ` [U-Boot] [PATCH 02/10] arm: socfpga: Sync Cyclone V DK pinmux configuration Marek Vasut
2015-01-30 22:08 ` [U-Boot] [PATCH 03/10] arm: socfpga: Sync Cyclone V DK PLL configuration Marek Vasut
2015-01-30 22:08 ` [U-Boot] [PATCH 04/10] arm: socfpga: Add USB and UDC support for Cyclone V DK Marek Vasut
2015-01-30 22:08 ` [U-Boot] [PATCH 05/10] arm: socfpga: Drop cyclone5 suffix from board file name Marek Vasut
2015-01-30 22:08 ` [U-Boot] [PATCH V2 06/10] arm: socfpga: Zap checkboard() Marek Vasut
2015-02-02  7:43   ` Stefan Roese
2015-02-04 13:39   ` Pavel Machek
2015-02-09 19:10     ` Marek Vasut
2015-01-30 22:08 ` [U-Boot] [PATCH 07/10] arm: socfpga: Zap board_early_init_f() Marek Vasut
2015-01-30 22:08 ` [U-Boot] [PATCH V2 08/10] arm: socfpga: Add Altera Arria V DK support Marek Vasut
2015-02-02  7:47   ` Stefan Roese
2015-02-09 19:09     ` Marek Vasut
2015-02-10  5:53       ` Stefan Roese
2015-02-10 15:50         ` Marek Vasut [this message]
2015-02-10 10:29       ` Pavel Machek
2015-02-10 15:53         ` Marek Vasut
2015-02-12 20:29           ` Pavel Machek
2015-02-12 21:37             ` Marek Vasut
2015-01-30 22:08 ` [U-Boot] [PATCH 09/10] dt: socfpga: Import and enable Cyclone V DK DTS Marek Vasut
2015-01-30 22:08 ` [U-Boot] [PATCH 10/10] dt: socfpga: Import and enable Arria " Marek Vasut

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=201502101650.45728.marex@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox