From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 1/7] arm: vf610: Add IOMUX support for Vybrid VF610
Date: Wed, 29 May 2013 16:54:31 +0200 (CEST) [thread overview]
Message-ID: <2078601675.1324075.1369839271762.JavaMail.root@advansee.com> (raw)
In-Reply-To: <51A59E4C.3030306@denx.de>
Hi Stefano,
On Wednesday, May 29, 2013 8:21:00 AM, Stefano Babic wrote:
> On 29/05/2013 07:29, Wang Huan-B18965 wrote:
>
> >> Where is this one defined? I don't see it in include/configs/vf610twr.h.
> >>
> > [Alison Wang] CONFIG_IOMUX_SHARE_CONF_REG is defined in
> > arch/arm/include/asm/arch-vf610/imx-regs.h. Because this is not a board
> > configuration, it is related to the SOC.
> >
> > Please refer to Stefano's comments below which also could be found in the
> > email on May 15th.
> >
> > Stefano wrote:
> >> +
> >> +/* MUX mode and PAD ctrl are in one register */
> >> +#define CONFIG_IOMUX_SHARE_CONF_REG
> >
> > NAK. This is not a board configuration, it is related to the SOC. This
> > setup should flow into the related imx-regs.h for this SOC. When you set
> > CONFIG_MVF600, this value should be set automatically.
> >
> >> Why not use "#ifdef CONFIG_VF610" since this is a platform-dependent
> >> code, and not a board-specific config option?
> > [Alison Wang] I use this CONFIG_IOMUX_SHARE_CONF_REG option, because this
> > part of codes
> > not only could be used on VF610 platform, but also could be used on VF620
> > or other platforms.
> > When it is used on VF620 or others, you could just enable
> > CONFIG_IOMUX_SHARE_CONF_REG
> > in the related imx-regs.h.
> > Otherwise, if "ifdef CONFIG_VF610" is used, you need to add "#if
> > defined(CONFIG_VF610) || defined(CONFIG_VF620)"
> > When this part of codes is also used on VF620. Then when this part of codes
> > is used on VF630 too, this line
> > will be very very long.
>
> Agree. This is a property of the processor and should be automatically
> set. It should not flow into board config file, and having a family of
> processor we cannot use ifdef CONFIG_VF610.
>
> IMHO the patch is ok.
>
> Acked-by: Stefano Babic <sbabic@denx.de>
I agree:
Reviewed-by: Beno?t Th?baudeau <benoit.thebaudeau@advansee.com>
Best regards,
Beno?t
next prev parent reply other threads:[~2013-05-29 14:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 8:55 [U-Boot] [PATCH v4 0/7] arm: vf610: Add Freescale Vybrid VF610 CPU and VF610TWR board support Alison Wang
2013-05-28 8:55 ` [U-Boot] [PATCH v4 1/7] arm: vf610: Add IOMUX support for Vybrid VF610 Alison Wang
2013-05-28 18:57 ` Benoît Thébaudeau
2013-05-29 5:29 ` Wang Huan-B18965
2013-05-29 6:21 ` Stefano Babic
2013-05-29 14:54 ` Benoît Thébaudeau [this message]
2013-06-03 9:03 ` Stefano Babic
2013-05-28 8:55 ` [U-Boot] [PATCH v4 2/7] arm: vf610: Add Vybrid VF610 CPU support Alison Wang
2013-05-28 19:16 ` Benoît Thébaudeau
2013-05-28 19:30 ` Benoît Thébaudeau
2013-05-29 5:37 ` Wang Huan-B18965
2013-05-29 14:46 ` Benoît Thébaudeau
2013-05-31 8:59 ` Stefano Babic
2013-05-31 16:10 ` Benoît Thébaudeau
2013-05-29 5:32 ` Wang Huan-B18965
2013-06-03 9:03 ` Stefano Babic
2013-05-28 8:55 ` [U-Boot] [PATCH v4 3/7] net: fec_mxc: Add support for Vybrid VF610 Alison Wang
2013-05-28 19:21 ` Benoît Thébaudeau
2013-06-03 9:03 ` Stefano Babic
2013-05-28 8:55 ` [U-Boot] [PATCH v4 4/7] arm: vf610: Add watchdog " Alison Wang
2013-06-03 9:03 ` Stefano Babic
2013-05-28 8:55 ` [U-Boot] [PATCH v4 5/7] arm: vf610: Add uart " Alison Wang
2013-06-03 9:03 ` Stefano Babic
2013-05-28 8:55 ` [U-Boot] [PATCH v4 6/7] arm: vf610: Add Vybrid VF610 to mxc_ocotp document Alison Wang
2013-05-31 16:10 ` Benoît Thébaudeau
2013-06-03 9:03 ` Stefano Babic
2013-05-28 8:55 ` [U-Boot] [PATCH v4 7/7] arm: vf610: Add basic support for Vybrid VF610TWR board Alison Wang
2013-05-28 19:57 ` Benoît Thébaudeau
2013-05-29 5:52 ` Wang Huan-B18965
2013-05-29 14:49 ` Benoît Thébaudeau
2013-06-03 9:03 ` Stefano Babic
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=2078601675.1324075.1369839271762.JavaMail.root@advansee.com \
--to=benoit.thebaudeau@advansee.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