linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Felipe Balbi <balbi@ti.com>
Cc: "Tony Lindgren" <tony@atomide.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Jason Cooper" <jason@lakedaemon.net>,
	"Aaro Koskinen" <aaro.koskinen@iki.fi>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Pavel Machek" <pavel@ucw.cz>,
	"Santosh Shilimkar" <ssantosh@kernel.org>,
	"Peter Kümmel" <syntheticpp@gmx.net>,
	"Linux OMAP Mailing List" <linux-omap@vger.kernel.org>,
	"Linux ARM Kernel Mailing List"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] irqchip: omap-intc: fix legacy DMA regression
Date: Tue, 6 Jan 2015 18:05:32 +0000	[thread overview]
Message-ID: <20150106180532.GO11502@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1420563093-26026-1-git-send-email-balbi@ti.com>

On Tue, Jan 06, 2015 at 10:51:33AM -0600, Felipe Balbi wrote:
> +	/*
> +	 * FIXME legacy OMAP DMA driver sitting under arch/arm/plat-omap/dma.c
> +	 * depends is still not ready for linear IRQ domains; because of that
> +	 * we need to temporarily "blacklist" OMAP2 and OMAP3 devices from using
> +	 * linear IRQ Domain until that driver is finally fixed.

"finally fixed" or finally killed off like it really needs to be, once
all users of it are killed.

We've been trying to do this for, what, three years now... I finally
pushed a WARN_ON() into that code to make it obvious to anyone who
uses omap_request_dma() that they really need to update their code.

Here's the list of references to that symbol which *still* need to be
fixed so that we can kill the legacy DMA driver:

drivers/media/platform/omap/omap_vout_vrfb.c:   ret = omap_request_dma(vout->vrfb_dma_tx.dev_id, "VRFB DMA TX",
drivers/media/platform/omap3isp/isphist.c:              ret = omap_request_dma(OMAP24XX_DMA_NO_DEVICE, "DMA_ISP_HIST",
drivers/media/platform/soc_camera/omap1_camera.c:       err = omap_request_dma(OMAP_DMA_CAMERA_IF_RX, DRIVER_NAME,
drivers/mtd/onenand/omap2.c:            r = omap_request_dma(0, pdev->dev.driver->name,
drivers/usb/gadget/udc/omap_udc.c:              status = omap_request_dma(dma_channel,
drivers/usb/gadget/udc/omap_udc.c:              status = omap_request_dma(dma_channel,
drivers/usb/musb/tusb6010_omap.c:               ret = omap_request_dma(chdat->sync_dev, dev_name,
drivers/usb/musb/tusb6010_omap.c:               ret = omap_request_dma(tusb_dma->sync_dev, "TUSB shared",

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.

  parent reply	other threads:[~2015-01-06 18:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01 18:12 3.18.1->3.19-rc2: In-band Error seen by MPU Peter Kümmel
2015-01-01 18:20 ` Aaro Koskinen
2015-01-02 16:19   ` Tony Lindgren
2015-01-02 18:31     ` Peter Kümmel
2015-01-02 20:19       ` Aaro Koskinen
2015-01-02 20:40         ` Tony Lindgren
2015-01-02 22:34           ` Aaro Koskinen
2015-01-03  0:02             ` Tony Lindgren
2015-01-03 11:24               ` Peter Kümmel
2015-01-03 12:16               ` Aaro Koskinen
2015-01-05 15:43                 ` Felipe Balbi
2015-01-05 23:16                   ` Aaro Koskinen
2015-01-06  0:12                     ` Tony Lindgren
2015-01-06  2:02                       ` Felipe Balbi
2015-01-06  2:01                     ` Felipe Balbi
2015-01-06 12:38                       ` Aaro Koskinen
2015-01-06 16:51                         ` [PATCH] irqchip: omap-intc: fix legacy DMA regression Felipe Balbi
2015-01-06 17:48                           ` Aaro Koskinen
2015-01-06 17:52                             ` Tony Lindgren
2015-01-06 18:05                           ` Russell King - ARM Linux [this message]
2015-01-06 18:24                             ` Aaro Koskinen
2015-01-06 18:30                             ` Tony Lindgren
2015-01-06 20:38                           ` [PATCH v2] " Felipe Balbi
2015-01-07  3:00                             ` Jason Cooper
2015-01-19 18:34                               ` Tony Lindgren
2015-01-07 11:12                           ` [PATCH] " Peter Kümmel
2015-01-06 11:25                   ` 3.18.1->3.19-rc2: In-band Error seen by MPU Peter Kümmel
2015-01-06 11:52                     ` Sebastian Reichel
2015-01-06 12:47                       ` Aaro Koskinen
2015-01-06 13:47                         ` Peter Kümmel
2015-01-06 13:04                       ` Peter Kümmel

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=20150106180532.GO11502@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=aaro.koskinen@iki.fi \
    --cc=balbi@ti.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=ssantosh@kernel.org \
    --cc=syntheticpp@gmx.net \
    --cc=tglx@linutronix.de \
    --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).