public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ruehl <chris.ruehl@gtsys.com.hk>
To: Markus Pargmann <mpa@pengutronix.de>
Cc: linus.walleij@linaro.org, linux-kernel@vger.kernel.org,
	linux-arm@lists.infradead.org
Subject: Re: [PATCH] imx27: pinctrl: fix wrong offset to ICONFB
Date: Wed, 22 Jan 2014 10:13:55 +0800	[thread overview]
Message-ID: <52DF2963.7000608@gtsys.com.hk> (raw)
In-Reply-To: <20140121102452.GA25016@pengutronix.de>

Hi Markus,

On Tuesday, January 21, 2014 06:24 PM, Markus Pargmann wrote:
> Hi,
>
> On Thu, Jan 16, 2014 at 09:18:23AM +0800, Chris Ruehl wrote:
>> The offset to ICONFB was incorrect, this patch set the correct value 0x14.
>> dev_dbg in function imx1_write_2bit print the wrong address and had been
>> moved after address calculation.
>>
>> Signed-off-by: Chris Ruehl <chris.ruehl@gtsys.com.hk>
>
> Reviewed-by: Markus Pargmann <mpa@pengutronix.de>
>
> Perhaps this should go to the stable tree too for 3.13 and 3.14?

Yes of cause, and I have one more, the offset in

@@ -139,7 +139,7 @@ static int imx1_read_2bit(struct imx1_pinctrl *ipctl, 
unsigned int pin_id,
                 u32 reg_offset)
  {
         void __iomem *reg = imx1_mem(ipctl, pin_id) + reg_offset;
-       int offset = pin_id % 16;
+       int offset = (pin_id % 16) * 2;

         /* Use the next register if the pin's port pin number is >=16 */
         if (pin_id % 32 >= 16)

should fixed, otherwise the printout of 
/sys/kernel/debug/pinctrl/10015000.iomuxc/pins show prints the wrong confo / 
iconfa / iconfb

I prepare a patch.

With kind regards,
Chris

>
> Regards,
>
> Markus
>
>> ---
>>   drivers/pinctrl/pinctrl-imx1-core.c |    8 ++++----
>>   1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/pinctrl/pinctrl-imx1-core.c b/drivers/pinctrl/pinctrl-imx1-core.c
>> index f77914a..8dfc3dc 100644
>> --- a/drivers/pinctrl/pinctrl-imx1-core.c
>> +++ b/drivers/pinctrl/pinctrl-imx1-core.c
>> @@ -45,7 +45,7 @@ struct imx1_pinctrl {
>>   #define MX1_DDIR 0x00
>>   #define MX1_OCR 0x04
>>   #define MX1_ICONFA 0x0c
>> -#define MX1_ICONFB 0x10
>> +#define MX1_ICONFB 0x14
>>   #define MX1_GIUS 0x20
>>   #define MX1_GPR 0x38
>>   #define MX1_PUEN 0x40
>> @@ -97,13 +97,13 @@ static void imx1_write_2bit(struct imx1_pinctrl *ipctl, unsigned int pin_id,
>>   	u32 old_val;
>>   	u32 new_val;
>>
>> -	dev_dbg(ipctl->dev, "write: register 0x%p offset %d value 0x%x\n",
>> -			reg, offset, value);
>> -
>>   	/* Use the next register if the pin's port pin number is >=16 */
>>   	if (pin_id % 32 >= 16)
>>   		reg += 0x04;
>>
>> +	dev_dbg(ipctl->dev, "write: register 0x%p offset %d value 0x%x\n",
>> +			reg, offset, value);
>> +
>>   	/* Get current state of pins */
>>   	old_val = readl(reg);
>>   	old_val &= mask;
>> --
>> 1.7.10.4
>>
>>
>

-- 
GTSYS Limited RFID Technology
A01 24/F Gold King Industrial Bld
35-41 Tai Lin Pai Road, Kwai Chung, Hong Kong
Fax (852) 8167 4060 - Tel (852) 3598 9488

Disclaimer: http://www.gtsys.com.hk/email/classified.html

      reply	other threads:[~2014-01-22  2:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16  1:18 [PATCH] imx27: pinctrl: fix wrong offset to ICONFB Chris Ruehl
2014-01-21 10:24 ` Markus Pargmann
2014-01-22  2:13   ` Chris Ruehl [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=52DF2963.7000608@gtsys.com.hk \
    --to=chris.ruehl@gtsys.com.hk \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpa@pengutronix.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