public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Adam Ford <aford173@gmail.com>
Cc: u-boot@lists.denx.de, trini@konsulko.com, lokeshvutla@ti.com
Subject: Re: [PATCH] ARM: omap3_logic: Cleanup usage of MUX_VAL
Date: Tue, 28 Sep 2021 08:48:10 +0200	[thread overview]
Message-ID: <2299718.1632811690@gemini.denx.de> (raw)
In-Reply-To: <20210927183030.506532-1-aford173@gmail.com>

Dear Adam Ford,

In message <20210927183030.506532-1-aford173@gmail.com> you wrote:
> The macro called MUX_VAL generates a writel instruction with
> semicolon at the end.  This table was written to use semicolons,
> however one was missed:
>
>    MUX_VAL(CP(SYS_BOOT2),      (IEN  | PTD | DIS | M4))    /* GPIO_4 */
>
> Since the extra semicolon is unnecessary with the use of the macro,
> remove all of them.

Thanks.

....
> +	MUX_VAL(CP(MCSPI2_SOMI),	(IEN  | PTD | DIS | M0))	/*HSUSB2_DATA5*/
> +	MUX_VAL(CP(MCSPI2_CS0),		(IEN  | PTD | EN  | M0))	/*HSUSB2_DATA6*/
> +	MUX_VAL(CP(MCSPI2_CLK),		(IEN  | PTD | DIS | M0))	/*HSUSB2_DATA7*/
>  	MUX_VAL(CP(SYS_BOOT2),      (IEN  | PTD | DIS | M4)) 	/* GPIO_4 */

This line stands out because indentation is different from all the
other lines.  You might want to fix that, too, while we are at it?

Reviewd-by: Wolfgang Denk <wd@denx.de>

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
When a program is being  tested,  it  is  too  late  to  make  design
changes.                  -- Geoffrey James, "The Tao of Programming"

      reply	other threads:[~2021-09-28  6:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 18:30 [PATCH] ARM: omap3_logic: Cleanup usage of MUX_VAL Adam Ford
2021-09-28  6:48 ` Wolfgang Denk [this message]

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=2299718.1632811690@gemini.denx.de \
    --to=wd@denx.de \
    --cc=aford173@gmail.com \
    --cc=lokeshvutla@ti.com \
    --cc=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox