public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 2/2] imx: mx6 add i2c4 clock support for i.MX6SX
Date: Mon, 29 Jun 2015 09:13:01 +0200	[thread overview]
Message-ID: <5590EFFD.70003@denx.de> (raw)
In-Reply-To: <20150629013332.GA31251@shlinux2>

Hi Peng,

On 29/06/2015 03:33, Peng Fan wrote:
> Hi Stefano,
> 
> On Sun, Jun 28, 2015 at 10:52:50AM +0200, Stefano Babic wrote:
>> Hi Peng,
>>
>> On 25/06/2015 03:33, Peng Fan wrote:
>>> Add I2C4 clock support for i.MX6SX. Since we use runtime check,
>>> but not macro, we need to remove `#ifdef ..` in crm_regs.h, or
>>> we will get compliation failure for other platforms.
>>
>>               ^----- compliation ?
> I mean gcc will complains about failing to compile the code.

Right. Fix the commit message.


>> Agree to group together macros that belong only to a SOC variant, else
>> it is difficult to find them. But what has
>> MXC_CCM_CCGR6_VDOAXICLK_OFFSET to do with addings I2C4 clock to i.MX6SX
>> ? It should be posted in a separate patch.
> 
> I just move this piece of code from the back to the front, see the end
> of the patch.
> I removed the #ifdef in header file, because it is really not a good idea
> to see so many #ifdefs in header file. The bad point here is some CCM macros
> are exposed to other platforms, so we should take care to use the CCM macros.

That is correct. We have a lot of macro across all i.MXes, not only
i.MX6es. This allow to have consistent code, and we must take care of
not breaking other SOCs.

> 
> Take the following as example:
> In crm_regs.h
> #ifdef CONFIG_MX6SX
> #define MXC_CCM_CCGR6_PWM7_MASK 	(3 << 30)
> #else
> #define MXC_CCM_CCGR6_VDOAXICLK_MASK	(3 << 12)
> #endif
> 
> u32 test()
> {
> 	if (is_cpu_type(MXC_CPU_MX6SX))
> 		return MXC_CCM_CCGR6_PWM7_MASK;		
> 	else
> 		return MXC_CCM_CCGR6_VDOAXICLK_OFFSET;
> }

Here there is a bad use of these kind of macro. To use a define, we
should have the same name and not different names as in this case.

> 
> Here gcc can not successfully compile the code if we want to build for i.mx6sx,
> becuase MXC_CCM_CCGR6_VDOAXICLK_OFFSET is not defined for i.mx6sx.

Right,  but this is bad code and must be fixed.

> 
> So:
> #define MXC_CCM_CCGR6_PWM7_MASK     (3 << 30)
> /* This CCM Definition does not exist on i.MX6SX */
> #define MXC_CCM_CCGR6_VDOAXICLK_MASK    (3 << 12)

Better should be to add also a common name for both, that is then used
in the function.

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================

  reply	other threads:[~2015-06-29  7:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25  1:33 [U-Boot] [PATCH V2 1/2] imx: mx6 remove duplicated enable_cspi_clock Peng Fan
2015-06-25  1:33 ` [U-Boot] [PATCH V2 2/2] imx: mx6 add i2c4 clock support for i.MX6SX Peng Fan
2015-06-28  8:52   ` Stefano Babic
2015-06-29  1:33     ` Peng Fan
2015-06-29  7:13       ` Stefano Babic [this message]
2015-06-29  7:29         ` Peng Fan
2015-06-28  8:53 ` [U-Boot] [PATCH V2 1/2] imx: mx6 remove duplicated enable_cspi_clock Stefano Babic
  -- strict thread matches above, loose matches on Subject: below --
2015-07-01  9:01 Peng Fan
2015-07-01  9:01 ` [U-Boot] [PATCH V2 2/2] imx: mx6 add i2c4 clock support for i.MX6SX Peng Fan
2015-07-10  7:37   ` 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=5590EFFD.70003@denx.de \
    --to=sbabic@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