From: Sourav <sourav.poddar@ti.com>
To: Sebastien Guiriec <s-guiriec@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Benoit Cousson <b-cousson@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/4] ARM/dts: omap5: Update UART with address space and interrupts
Date: Mon, 22 Oct 2012 19:25:22 +0530 [thread overview]
Message-ID: <5085504A.60704@ti.com> (raw)
In-Reply-To: <50854273.5080504@ti.com>
Hi Sebestien,
On Monday 22 October 2012 06:26 PM, Sourav wrote:
> On Monday 22 October 2012 06:20 PM, Benoit Cousson wrote:
>> On 10/22/2012 02:27 PM, Sourav wrote:
>>> Hi Benoit,
>>> On Monday 22 October 2012 05:37 PM, Benoit Cousson wrote:
>>>> On 10/22/2012 01:57 PM, Benoit Cousson wrote:
>>>>> Hi Sourav,
>>>>>
>>>>> On 10/22/2012 01:16 PM, Sourav wrote:
>>>>>> Hi Sebastien,
>>>>>> On Monday 22 October 2012 03:52 PM, Sebastien Guiriec wrote:
>>>>>>> Add base address and interrupt line inside Device Tree data for
>>>>>> Incomplete sentence!
>>>>>>> Signed-off-by: Sebastien Guiriec <s-guiriec@ti.com>
>>>>>>> ---
>>>>>>> arch/arm/boot/dts/omap5.dtsi | 16 ++++++++++++++--
>>>>>>> 1 file changed, 14 insertions(+), 2 deletions(-)
>>>>>>>
>>>>>>> diff --git a/arch/arm/boot/dts/omap5.dtsi
>>>>>>> b/arch/arm/boot/dts/omap5.dtsi
>>>>>>> index 6c22e1b..413df94 100644
>>>>>>> --- a/arch/arm/boot/dts/omap5.dtsi
>>>>>>> +++ b/arch/arm/boot/dts/omap5.dtsi
>>>>>>> @@ -237,36 +237,48 @@
>>>>>>> uart1: serial@4806a000 {
>>>>>>> compatible = "ti,omap4-uart";
>>>>>>> + reg = <0x4806a000 0x100>;
>>>>>>> + interrupts = <0 72 0x4>;
>>>>>>> ti,hwmods = "uart1";
>>>>>>> clock-frequency = <48000000>;
>>>>>>> };
>>>>>>> uart2: serial@4806c000 {
>>>>>>> compatible = "ti,omap4-uart";
>>>>>>> + reg = <0x4806c000 0x100>;
>>>>>>> + interrupts = <0 73 0x4>;
>>>>>>> ti,hwmods = "uart2";
>>>>>>> clock-frequency = <48000000>;
>>>>>>> };
>>>>>>> uart3: serial@48020000 {
>>>>>>> compatible = "ti,omap4-uart";
>>>>>>> + reg = <0x48020000 0x100>;
>>>>>>> + interrupts = <0 74 0x4>;
>>>>>>> ti,hwmods = "uart3";
>>>>>>> clock-frequency = <48000000>;
>>>>>>> };
>>>>>>> uart4: serial@4806e000 {
>>>>>>> compatible = "ti,omap4-uart";
>>>>>>> + reg = <0x4806e000 0x100>;
>>>>>>> + interrupts = <0 70 0x4>;
>>>>>>> ti,hwmods = "uart4";
>>>>>>> clock-frequency = <48000000>;
>>>>>>> };
>>>>>>> uart5: serial@48066000 {
>>>>>>> - compatible = "ti,omap5-uart";
>>>>>>> + compatible = "ti,omap4-uart";
>>>>>>> + reg = <0x48066000 0x100>;
>>>>>>> + interrupts = <0 105 0x4>;
>>>>>> In Omap5 TRM, the interrupt number mentioned for uart5 is 138.
>>>>>> How is
>>>>>> 105 coming?
>>>>> It is from hwmod and thus from the HW spec. It looks like the TRM is
>>>>> wrong... or the HW spec :-)
>>>>>
>>>>>>> ti,hwmods = "uart5";
>>>>>>> clock-frequency = <48000000>;
>>>>>>> };
>>>>>>> uart6: serial@48068000 {
>>>>>>> - compatible = "ti,omap6-uart";
>>>>>>> + compatible = "ti,omap4-uart";
>>>>>>> + reg = <0x48068000 0x100>;
>>>>>>> + interrupts = <0 106 0x4>;
>>>>>> Same here, TRM shows this number to be 139 ?
>>>> In fact, even the TRM (ES1.0 NDA vM) is aligned with these data.
>>>> Where did you see 138 and 139?
>>> I looked at Page 6300 of the above TRM, Figure 24-60. Is this place not
>>> correct to look
>>> up for these data?
>> Nope. Well it should be accurate but since it is a diagram, it does not
>> necessarily reflect the latest integration data like IRQ line.
>>
>> You'd better use the table that list all the IRQ per CPU:
>>
>> 18.3.2 Interrupt Requests to INTC_MPU
> Ahh. True. The table does show the numbers to be 105 and 106.
> Thanks for the pointer.
>
> ~Sourav
>> Regards,
>> Benoit
>>
>
After fixing the minor comment on the commit log, you can add
Acked-by: Sourav Poddar <sourav.poddar@ti.com>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2012-10-22 13:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 10:22 [PATCH 0/4] ARM/dts: Update OMAP5 with address space and interrupts Sebastien Guiriec
2012-10-22 10:22 ` [PATCH 1/4] ARM/dts: omap5: Update GPIO with address space and interrupt Sebastien Guiriec
2012-10-22 10:22 ` [PATCH 2/4] ARM/dts: omap5: Update I2C with address space and interrupts Sebastien Guiriec
2012-10-22 11:14 ` Shubhrajyoti Datta
2012-10-22 10:22 ` [PATCH 3/4] ARM/dts: omap5: Update UART " Sebastien Guiriec
2012-10-22 11:16 ` Sourav
2012-10-22 11:57 ` Benoit Cousson
2012-10-22 12:07 ` Benoit Cousson
2012-10-22 12:27 ` Sourav
2012-10-22 12:31 ` Felipe Balbi
2012-10-22 12:50 ` Benoit Cousson
2012-10-22 12:56 ` Sourav
2012-10-22 13:55 ` Sourav [this message]
2012-10-22 10:22 ` [PATCH 4/4] ARM/dts: omap5: Update MMC " Sebastien Guiriec
2012-10-22 14:11 ` [PATCH 0/4] ARM/dts: Update OMAP5 " Benoit Cousson
2012-10-22 15:21 ` Sebastien Guiriec
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=5085504A.60704@ti.com \
--to=sourav.poddar@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=s-guiriec@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).