From: Sourav <sourav.poddar@ti.com>
To: Luciano Coelho <coelho@ti.com>
Cc: b-cousson@ti.com, tony@atomide.com, linux-omap@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, balbi@ti.com,
santosh.shilimkar@ti.com
Subject: Re: [PATCH] arm: dts: omap4-sdp: Add I2c pinctrl data
Date: Wed, 30 Jan 2013 12:10:18 +0530 [thread overview]
Message-ID: <5108C052.3070604@ti.com> (raw)
In-Reply-To: <1359527158.14894.37.camel@cumari.coelho.fi>
Hi Luciano,
On Wednesday 30 January 2013 11:55 AM, Luciano Coelho wrote:
> Hi Sourav,
>
> On Mon, 2013-01-28 at 16:47 +0530, Sourav Poddar wrote:
>> Booting 3.8-rc4 om omap 4430sdp results in the following error
>>
>> omap_i2c 48070000.i2c: did not get pins for i2c error: -19
>> [ 1.024261] omap_i2c 48070000.i2c: bus 0 rev0.12 at 100 kHz
>> [ 1.030181] omap_i2c 48072000.i2c: did not get pins for i2c error: -19
>> [ 1.037384] omap_i2c 48072000.i2c: bus 1 rev0.12 at 400 kHz
>> [ 1.043762] omap_i2c 48060000.i2c: did not get pins for i2c error: -19
>> [ 1.050964] omap_i2c 48060000.i2c: bus 2 rev0.12 at 100 kHz
>> [ 1.056823] omap_i2c 4807a000.i2c: did not get pins for i2c error: -19
>> [ 1.064025] omap_i2c 4807a000.i2c: bus 3 rev0.12 at 400 kHz
>>
>> This happens because omap4 dts file is not adapted to use i2c through pinctrl
>> framework. Populating i2c pinctrl data to get rid of the error.
>>
>> Tested on omap4430 sdp with 3.8-rc4 kernel.
>>
>> Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
>> Reported-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>> ---
> Could you do the same thing for panda? I'm getting the same kind of
> errors with it:
Sure, I will do that.
> [ 0.000000] Machine: Generic OMAP4 (Flattened Device Tree), model: TI OMAP4 PandaBoard
> [...]
> [ 2.884826] omap_i2c 48072000.i2c: did not get pins for i2c error: -19
> [ 2.890686] omap_i2c 48072000.i2c: bus 1 rev0.11 at 400 kHz
> [ 2.892028] omap_i2c 48060000.i2c: did not get pins for i2c error: -19
> [ 2.899047] omap_i2c 48060000.i2c: bus 2 rev0.11 at 100 kHz
> [ 2.906677] omap_i2c 48350000.i2c: did not get pins for i2c error: -19
> [ 2.912872] omap_i2c 48350000.i2c: bus 3 rev0.11 at 400 kHz
>
> --
> Cheers,
> Luca.
>
Thanks,
Sourav
WARNING: multiple messages have this Message-ID (diff)
From: sourav.poddar@ti.com (Sourav)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: dts: omap4-sdp: Add I2c pinctrl data
Date: Wed, 30 Jan 2013 12:10:18 +0530 [thread overview]
Message-ID: <5108C052.3070604@ti.com> (raw)
In-Reply-To: <1359527158.14894.37.camel@cumari.coelho.fi>
Hi Luciano,
On Wednesday 30 January 2013 11:55 AM, Luciano Coelho wrote:
> Hi Sourav,
>
> On Mon, 2013-01-28 at 16:47 +0530, Sourav Poddar wrote:
>> Booting 3.8-rc4 om omap 4430sdp results in the following error
>>
>> omap_i2c 48070000.i2c: did not get pins for i2c error: -19
>> [ 1.024261] omap_i2c 48070000.i2c: bus 0 rev0.12 at 100 kHz
>> [ 1.030181] omap_i2c 48072000.i2c: did not get pins for i2c error: -19
>> [ 1.037384] omap_i2c 48072000.i2c: bus 1 rev0.12 at 400 kHz
>> [ 1.043762] omap_i2c 48060000.i2c: did not get pins for i2c error: -19
>> [ 1.050964] omap_i2c 48060000.i2c: bus 2 rev0.12 at 100 kHz
>> [ 1.056823] omap_i2c 4807a000.i2c: did not get pins for i2c error: -19
>> [ 1.064025] omap_i2c 4807a000.i2c: bus 3 rev0.12 at 400 kHz
>>
>> This happens because omap4 dts file is not adapted to use i2c through pinctrl
>> framework. Populating i2c pinctrl data to get rid of the error.
>>
>> Tested on omap4430 sdp with 3.8-rc4 kernel.
>>
>> Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
>> Reported-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>> ---
> Could you do the same thing for panda? I'm getting the same kind of
> errors with it:
Sure, I will do that.
> [ 0.000000] Machine: Generic OMAP4 (Flattened Device Tree), model: TI OMAP4 PandaBoard
> [...]
> [ 2.884826] omap_i2c 48072000.i2c: did not get pins for i2c error: -19
> [ 2.890686] omap_i2c 48072000.i2c: bus 1 rev0.11 at 400 kHz
> [ 2.892028] omap_i2c 48060000.i2c: did not get pins for i2c error: -19
> [ 2.899047] omap_i2c 48060000.i2c: bus 2 rev0.11 at 100 kHz
> [ 2.906677] omap_i2c 48350000.i2c: did not get pins for i2c error: -19
> [ 2.912872] omap_i2c 48350000.i2c: bus 3 rev0.11 at 400 kHz
>
> --
> Cheers,
> Luca.
>
Thanks,
Sourav
WARNING: multiple messages have this Message-ID (diff)
From: Sourav <sourav.poddar@ti.com>
To: Luciano Coelho <coelho@ti.com>
Cc: <b-cousson@ti.com>, <tony@atomide.com>,
<linux-omap@vger.kernel.org>,
<devicetree-discuss@lists.ozlabs.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <balbi@ti.com>,
<santosh.shilimkar@ti.com>
Subject: Re: [PATCH] arm: dts: omap4-sdp: Add I2c pinctrl data
Date: Wed, 30 Jan 2013 12:10:18 +0530 [thread overview]
Message-ID: <5108C052.3070604@ti.com> (raw)
In-Reply-To: <1359527158.14894.37.camel@cumari.coelho.fi>
Hi Luciano,
On Wednesday 30 January 2013 11:55 AM, Luciano Coelho wrote:
> Hi Sourav,
>
> On Mon, 2013-01-28 at 16:47 +0530, Sourav Poddar wrote:
>> Booting 3.8-rc4 om omap 4430sdp results in the following error
>>
>> omap_i2c 48070000.i2c: did not get pins for i2c error: -19
>> [ 1.024261] omap_i2c 48070000.i2c: bus 0 rev0.12 at 100 kHz
>> [ 1.030181] omap_i2c 48072000.i2c: did not get pins for i2c error: -19
>> [ 1.037384] omap_i2c 48072000.i2c: bus 1 rev0.12 at 400 kHz
>> [ 1.043762] omap_i2c 48060000.i2c: did not get pins for i2c error: -19
>> [ 1.050964] omap_i2c 48060000.i2c: bus 2 rev0.12 at 100 kHz
>> [ 1.056823] omap_i2c 4807a000.i2c: did not get pins for i2c error: -19
>> [ 1.064025] omap_i2c 4807a000.i2c: bus 3 rev0.12 at 400 kHz
>>
>> This happens because omap4 dts file is not adapted to use i2c through pinctrl
>> framework. Populating i2c pinctrl data to get rid of the error.
>>
>> Tested on omap4430 sdp with 3.8-rc4 kernel.
>>
>> Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
>> Reported-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>> ---
> Could you do the same thing for panda? I'm getting the same kind of
> errors with it:
Sure, I will do that.
> [ 0.000000] Machine: Generic OMAP4 (Flattened Device Tree), model: TI OMAP4 PandaBoard
> [...]
> [ 2.884826] omap_i2c 48072000.i2c: did not get pins for i2c error: -19
> [ 2.890686] omap_i2c 48072000.i2c: bus 1 rev0.11 at 400 kHz
> [ 2.892028] omap_i2c 48060000.i2c: did not get pins for i2c error: -19
> [ 2.899047] omap_i2c 48060000.i2c: bus 2 rev0.11 at 100 kHz
> [ 2.906677] omap_i2c 48350000.i2c: did not get pins for i2c error: -19
> [ 2.912872] omap_i2c 48350000.i2c: bus 3 rev0.11 at 400 kHz
>
> --
> Cheers,
> Luca.
>
Thanks,
Sourav
next prev parent reply other threads:[~2013-01-30 6:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 11:17 [PATCH] arm: dts: omap4-sdp: Add I2c pinctrl data Sourav Poddar
2013-01-28 11:17 ` Sourav Poddar
2013-01-28 11:17 ` Sourav Poddar
2013-01-30 6:25 ` Luciano Coelho
2013-01-30 6:25 ` Luciano Coelho
2013-01-30 6:25 ` Luciano Coelho
2013-01-30 6:40 ` Sourav [this message]
2013-01-30 6:40 ` Sourav
2013-01-30 6:40 ` Sourav
[not found] ` <5108C052.3070604-l0cyMroinI0@public.gmane.org>
2013-01-30 8:43 ` Kumar, Anil
2013-01-30 8:43 ` Kumar, Anil
2013-01-30 8:43 ` Kumar, Anil
2013-01-30 8:48 ` Santosh Shilimkar
2013-01-30 8:48 ` Santosh Shilimkar
2013-01-30 9:06 ` Luciano Coelho
2013-01-30 9:06 ` Luciano Coelho
2013-01-31 2:32 ` Kumar, Anil
2013-01-31 2:32 ` Kumar, Anil
2013-01-31 2:32 ` Kumar, Anil
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=5108C052.3070604@ti.com \
--to=sourav.poddar@ti.com \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=coelho@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.