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] [PATCH] arm: mvebu: Add Helios4 Armada 38x initial support
Date: Mon, 11 Jun 2018 11:45:02 +0200	[thread overview]
Message-ID: <64b89da3-90bd-3699-b83d-9385676e71bf@denx.de> (raw)
In-Reply-To: <20180606132508.19221-1-dgilmore@redhat.com>

Hi Dennis,

On 06.06.2018 15:25, dgilmore at redhat.com wrote:
> From: Dennis Gilmore <dennis@ausil.us>
> 
> The helios4 is built on the SolidRun Armada 38x SOM.
> The port os based on the ClearFog board, using information from
> https://github.com/helios-4/u-boot-marvell as well as dtb input
> from https://github.com/helios-4/linux-marvell
> 
> Signed-off-by: Dennis Gilmore <dennis@ausil.us>
> Signed-off-by: Dennis Gilmore <dgilmore@redhat.com>
> ---
> changes since RFC
> add armada-38x-solidrun-microsom.dtsi minus buffer-memory nodes from linux kernel
> fix up maintainers file
> use correct switch in README file
> add SPDX header to kwbimage.cfg and dts file
> Port to DM_I2C
> 
> Changes since V1
> moved to kobol namespace at the request of the board supplier
> remove gpio resets they are clearfog specific
> set maintainer to myself and update copyrights
> remove unused config options

Before pulling this patch into mainline, I ran the checkpatch
--git test as requested by Tom. This reveals some mostly minor
issues:

WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#51: 
new file mode 100644

WARNING: line over 80 characters
#245: FILE: arch/arm/dts/armada-388-helios4.dts:190:
+                                               line-name = "usb-overcurrent-status";

CHECK: Prefer using the BIT macro
#617: FILE: board/kobol/helios4/helios4.c:22:
+#define ETH_PHY_CTRL_POWER_DOWN_MASK   (1 << ETH_PHY_CTRL_POWER_DOWN_BIT)

WARNING: Missing a blank line after declarations
#730: FILE: board/kobol/helios4/helios4.c:135:
+               int ret;
+               ret = i2c_get_chip_for_busnum(0, io_exp[i].addr, 1, &dev);

ERROR: code indent should use tabs where possible
#890: FILE: include/configs/helios4.h:44:
+                                         CONFIG_SYS_SCSI_MAX_LUN)$

WARNING: please, no spaces at the start of a line
#890: FILE: include/configs/helios4.h:44:
+                                         CONFIG_SYS_SCSI_MAX_LUN)$

CHECK: Macro argument reuse 'func' - possible side-effects?
#987: FILE: include/configs/helios4.h:141:
+#define BOOT_TARGET_DEVICES(func) \
+       BOOT_TARGET_DEVICES_MMC(func) \
+       BOOT_TARGET_DEVICES_USB(func) \
+       BOOT_TARGET_DEVICES_SATA(func) \
+       func(PXE, pxe, na) \
+       func(DHCP, dhcp, na)

total: 1 errors, 4 warnings, 2 checks, 914 lines checked

Could you please check and fix most of these issues (BIT macro, missing
blank line, code indentation and space@start of line)?

Thanks,
Stefan

  parent reply	other threads:[~2018-06-11  9:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06 13:25 [U-Boot] [PATCH] arm: mvebu: Add Helios4 Armada 38x initial support dgilmore at redhat.com
2018-06-07  8:56 ` Chris Packham
2018-06-11  9:45 ` Stefan Roese [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-04 21:48 dgilmore at redhat.com
2018-06-05 11:20 ` Chris Packham

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=64b89da3-90bd-3699-b83d-9385676e71bf@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.