SUPERH platform development
 help / color / mirror / Atom feed
From: Khiem Nguyen <khiem.nguyen.xt@renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2] ARM: shmobile: Lager: Correct I2C bus for VDD MPU regulator
Date: Sun, 06 Jul 2014 22:39:24 +0000	[thread overview]
Message-ID: <53B9D01C.4030303@renesas.com> (raw)
In-Reply-To: <53B5F327.5040301@renesas.com>

Dear Simon-san, Magnus-san,
cc Inami-san,

>> 	Thanks for your patch. Can you please extend the commit message to
>> 	include the reason behind this patch?

>> In particular I think you still need to address his feedback:

I'd like to explain it here. After all parties agree,
I will send new version of my patch.

The reason of this patch is simply to align with information
in datasheet of R-Car H2.
With this change, CPUFreq implementation for Lager board is aligned 
with implementation for Koelsch board.

Is it reasonable enough ?

Thanks.

Best regards,
KHIEM Nguyen

On 7/6/2014 11:58 PM, Simon Horman wrote:
> On Sun, Jul 06, 2014 at 04:37:28PM +0200, Simon Horman wrote:
>> On Fri, Jul 04, 2014 at 03:41:21PM +0900, Khiem Nguyen wrote:
>>> Hi Inami-san,
>>>
>>> On 7/4/2014 2:40 PM, Gaku Inami wrote:
>>>>> I2C bus for VDD MPU regulator is IIC3, not I2C3.
>>> [...]
>>>>> Signed-off-by: Khiem Nguyen <khiem.nguyen.xt@renesas.com>
>>> [...]
>>>> Thank you for updating patch. 
>>>> I tested your patch. Test reult is good.
>>> Thanks for your testing.
>>>
>>> [...]
>>>> Tested-by: Gaku Inami <gaku.inami.xw@bp.renesas.com>
>>> [...]
>>>> This is a bug fix of my cpufreq patch. Thank you for your fix.
>>> OK. 
>>> Let's wait for final comment from Magnus-san.
>>
>> Thanks, I have decided to queue this up.
> 
> On second thoughts I will wait for Magnus.
> 
> In particular I think you still need to address his feedback:
> 
> 	Hi Khiem-san,
> 
> 	Thanks for your patch. Can you please extend the commit message to
> 	include the reason behind this patch?
> 
> 	From my side this looks like a software policy change. Unless I'm
> 	mistaken both I2C3 and IIC3 share the same pins on the SoC, and
> 	because of that it should be possible to access that particular I2C
> 	bus already without any modification.
> 
> 	So please explain why you want to change this.
> 

  parent reply	other threads:[~2014-07-06 22:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04  0:19 [PATCH v2] ARM: shmobile: Lager: Correct I2C bus for VDD MPU regulator Khiem Nguyen
2014-07-04  5:40 ` Gaku Inami
2014-07-04  6:41 ` Khiem Nguyen
2014-07-06 14:37 ` Simon Horman
2014-07-06 14:58 ` Simon Horman
2014-07-06 22:39 ` Khiem Nguyen [this message]
2014-07-10  8:23 ` Magnus Damm
2014-07-10  8:43 ` Khiem Nguyen
2014-07-10  9:40 ` Wolfram Sang
2014-07-10  9:46 ` Magnus Damm
2014-07-10 10:01 ` Khiem Nguyen
2014-07-10 10:03 ` Magnus Damm
2014-07-11  8:45 ` Simon Horman
2014-07-13 23:19 ` Khiem Nguyen

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=53B9D01C.4030303@renesas.com \
    --to=khiem.nguyen.xt@renesas.com \
    --cc=linux-sh@vger.kernel.org \
    /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