public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Raghuveer Murthy <x0075817@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "Murthy, Raghuveer" <raghuveer.murthy@ti.com>,
	"Semwal, Sumit" <sumit.semwal@ti.com>,
	"Hilman, Kevin" <khilman@ti.com>,
	"paul@pwsan.com" <paul@pwsan.com>,
	"Guruswamy, Senthilvadivu" <svadivu@ti.com>,
	"Hiremath, Vaibhav" <hvaibhav@ti.com>,
	"tomi.valkeinen@nokia.com" <tomi.valkeinen@nokia.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v10 18/18] OMAP2, 3: DSS2: Get DSS IRQ from platform	device
Date: Thu, 27 Jan 2011 18:34:41 +0530	[thread overview]
Message-ID: <4D416D69.6030200@ti.com> (raw)
In-Reply-To: <20110127125955.GC26418@n2100.arm.linux.org.uk>

On Thursday 27 January 2011 06:29 PM, Russell King - ARM Linux wrote:
> On Thu, Jan 27, 2011 at 06:19:21PM +0530, Raghuveer Murthy wrote:
>>> +	r = request_irq(dss_irq,
>>> +		cpu_is_omap24xx()
>>> +		? dss_irq_handler_omap2
>>> +		: dss_irq_handler_omap3,
>>
>> it should be
>>
>> 		cpu_is_omap24xx()
>> 		? dss_irq_handler_omap3
>> 		: dss_irq_handler_omap2,
>>
>> I am seeing a crash on Panda, which gets rectified with this
>> change. The root cause is access to DSS_IRQSTATUS register in the
>> dss_irq_handler_omap3 handler, which is not valid for OMAP4.
>
> That really doesn't look right.  Let me translate the code you've just
> written:
>
> 	if (cpu_is_omap24xx())
> 		handler = dss_irq_handler_omap3;
> 	else
> 		handler = dss_irq_handler_omap2;
>
> Which means: if we have an OMAP24xx device, use the OMAP3 handler,
> otherwise use the OMAP2 handler.  That's got to be wrong.
>
I agree, that the logic seems counter-intuitive. I was doing a quick test.

However, to  keep the correct sequence, the logic inside the respective 
handlers need to be looked at.

Regards,
Raghuveer

  reply	other threads:[~2011-01-27 13:09 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24  6:21 [PATCH v10 00/18] OMAP2,3: hwmod DSS Adaptation Sumit Semwal
2011-01-24  6:21 ` [PATCH v10 01/18] OMAP2,3: DSS2: remove forced clk-disable from omap_dss_remove Sumit Semwal
2011-01-24  6:21 ` [PATCH v10 02/18] OMAP2420: hwmod data: add DSS DISPC RFBI VENC Sumit Semwal
2011-01-24  6:21 ` [PATCH v10 03/18] OMAP2430: " Sumit Semwal
2011-01-24  6:21 ` [PATCH v10 04/18] OMAP3: hwmod data: add DSS DISPC RFBI DSI VENC Sumit Semwal
2011-01-24  6:21 ` [PATCH v10 05/18] OMAP2,3 DSS2 Change driver name to omap_display Sumit Semwal
2011-02-24  9:27   ` Tomi Valkeinen
2011-02-28  6:53     ` Tomi Valkeinen
2011-02-28  7:09       ` archit taneja
2011-02-28  7:19         ` Tomi Valkeinen
2011-02-28  7:27           ` archit taneja
2011-02-28  8:16             ` Semwal, Sumit
2011-02-28  8:29               ` Tomi Valkeinen
2011-02-28 11:36           ` Cousson, Benoit
2011-02-28 12:10             ` Tomi Valkeinen
2011-02-28 12:13               ` Russell King - ARM Linux
2011-02-28 13:38                 ` Cousson, Benoit
2011-02-28 14:06                   ` Russell King - ARM Linux
2011-02-28 14:55                     ` Cousson, Benoit
2011-02-28 14:00               ` Cousson, Benoit
2011-02-28 14:57                 ` Tomi Valkeinen
2011-03-01 10:18                   ` Cousson, Benoit
2011-01-24  6:21 ` [PATCH v10 06/18] OMAP2,3 DSS2 Use Regulator init with driver name Sumit Semwal
2011-01-24  6:21 ` [PATCH v10 07/18] OMAP2,3: DSS2: Create new file display.c for central dss driver registration Sumit Semwal
2011-01-24  6:21 ` [PATCH v10 08/18] OMAP2,3: DSS2: board files: replace platform_device_register with omap_display_init() Sumit Semwal
2011-01-24  6:21 ` [PATCH v10 09/18] OMAP2,3: DSS2: Build omap_device for each DSS HWIP Sumit Semwal
2011-01-24  6:21 ` [PATCH v10 10/18] OMAP2,3: DSS2: DSS: create platform_driver, move init,exit to driver Sumit Semwal
2011-01-24  6:21 ` [PATCH v10 11/18] OMAP2,3: DSS2: Move clocks from core driver to dss driver Sumit Semwal
2011-01-24  6:21 ` [PATCH v10 12/18] OMAP2,3: DSS2: RFBI: create platform_driver, move init,exit to driver Sumit Semwal
2011-01-24  6:22 ` [PATCH v10 13/18] OMAP2,3: DSS2: DISPC: " Sumit Semwal
2011-01-24  6:22 ` [PATCH v10 14/18] OMAP2,3: DSS2: VENC: " Sumit Semwal
2011-01-24  6:22 ` [PATCH v10 15/18] OMAP2,3: DSS2: DSI: " Sumit Semwal
2011-01-24  6:22 ` [PATCH v10 16/18] OMAP2,3: DSS2: replace printk with dev_dbg in init Sumit Semwal
2011-01-24  6:22 ` [PATCH v10 17/18] OMAP2,3: DSS2: Use platform device to get baseaddr Sumit Semwal
2011-01-24  6:22 ` [PATCH v10 18/18] OMAP2,3: DSS2: Get DSS IRQ from platform device Sumit Semwal
2011-01-27 12:49   ` Raghuveer Murthy
2011-01-27 12:59     ` [PATCH v10 18/18] OMAP2, 3: " Russell King - ARM Linux
2011-01-27 13:04       ` Raghuveer Murthy [this message]
2011-01-27 15:23         ` Semwal, Sumit
2011-02-14 14:09   ` [PATCH v10 18/18] OMAP2,3: " Tomi Valkeinen
2011-02-14 18:35     ` Semwal, Sumit
2011-01-24 21:57 ` [PATCH v10 00/18] OMAP2,3: hwmod DSS Adaptation Kevin Hilman
2011-01-25 17:03   ` Tony Lindgren
2011-01-28 12:01     ` Tomi Valkeinen

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=4D416D69.6030200@ti.com \
    --to=x0075817@ti.com \
    --cc=hvaibhav@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=paul@pwsan.com \
    --cc=raghuveer.murthy@ti.com \
    --cc=sumit.semwal@ti.com \
    --cc=svadivu@ti.com \
    --cc=tomi.valkeinen@nokia.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