From: Tony Lindgren <tony@atomide.com>
To: Roger Quadros <rogerq@ti.com>
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
bcousson@baylibre.com, ezequiel@vanguardiasur.com.ar,
linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 03/12] mtd: nand: omap: Move IRQ handling from GPMC to NAND driver
Date: Mon, 13 Jul 2015 00:10:09 -0700 [thread overview]
Message-ID: <20150713071008.GC26485@atomide.com> (raw)
In-Reply-To: <1436531019-18088-4-git-send-email-rogerq@ti.com>
* Roger Quadros <rogerq@ti.com> [150710 05:26]:
> Since the Interrupt Events are used only by the NAND driver,
> there is no point in managing the Interrupt registers
> in the GPMC driver and complicating it with irqchip modeling.
I don't think it's a good idea to allow external drivers to
tinker directly with GPMC registers. How about just set up GPMC
as an irqchip for the edge detection interrupts?
I think we already have devices with multiple NAND chips. And
there's nothing stopping other drivers from using the edge
detection interrupts.
Regards,
Tony
next prev parent reply other threads:[~2015-07-13 7:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 12:23 [PATCH 00/12] ARM: omap: mtd: nand: Support GPMC NAND on non-OMAP platforms Roger Quadros
[not found] ` <1436531019-18088-1-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2015-07-10 12:23 ` [PATCH 01/12] ARM: OMAP2+: gpmc: Add platform data Roger Quadros
2015-07-10 12:23 ` [PATCH 05/12] mtd: nand: omap: Move NAND write protect code from GPMC to NAND driver Roger Quadros
2015-07-10 12:23 ` [PATCH 02/12] ARM: OMAP2+: gpmc: Add gpmc timings and settings to platform data Roger Quadros
[not found] ` <1436531019-18088-3-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2015-07-13 13:31 ` Tony Lindgren
2015-07-13 13:34 ` Roger Quadros
2015-07-10 12:23 ` [PATCH 03/12] mtd: nand: omap: Move IRQ handling from GPMC to NAND driver Roger Quadros
2015-07-13 7:10 ` Tony Lindgren [this message]
[not found] ` <20150713071008.GC26485-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-07-13 10:04 ` Roger Quadros
2015-07-13 12:40 ` Tony Lindgren
2015-07-13 12:51 ` nick
[not found] ` <55A3B467.8030409-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-07-13 13:01 ` Tony Lindgren
2015-07-13 13:03 ` nick
2015-07-13 13:12 ` Roger Quadros
2015-07-13 13:15 ` nick
2015-07-13 13:21 ` Roger Quadros
2015-07-13 13:32 ` nick
[not found] ` <55A3BDE3.2080004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-07-13 13:35 ` Roger Quadros
[not found] ` <20150713124059.GF26485-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-07-29 12:06 ` Roger Quadros
2015-07-29 12:13 ` nick
2015-07-29 13:52 ` Roger Quadros
2015-07-29 14:08 ` nick
2015-07-29 15:12 ` Roger Quadros
2015-07-29 15:26 ` nick
[not found] ` <55B8F0B3.5000009-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-07-29 15:39 ` Roger Quadros
[not found] ` <55B8C1D5.3090807-l0cyMroinI0@public.gmane.org>
2015-07-31 10:21 ` Roger Quadros
[not found] ` <55BB4C1D.5080905-l0cyMroinI0@public.gmane.org>
2015-08-03 13:08 ` Tony Lindgren
2015-07-10 12:23 ` [PATCH 04/12] mtd: nand: omap: Move gpmc_update_nand_reg to nand driver Roger Quadros
2015-07-10 12:23 ` [PATCH 06/12] mtd: nand: omap: Copy platform data parameters to omap_nand_info data Roger Quadros
2015-07-10 12:23 ` [PATCH 07/12] mtd: nand: omap: Clean up device tree support Roger Quadros
2015-07-10 12:23 ` [PATCH 08/12] mtd: nand: omap: Update DT binding documentation Roger Quadros
2015-07-10 12:23 ` [PATCH 09/12] memory: omap-gpmc: use module_platform_driver() Roger Quadros
2015-07-10 12:23 ` [PATCH 10/12] memory: omap-gpmc: Prevent mapping into 1st 16MB Roger Quadros
2015-07-10 12:23 ` [PATCH 11/12] ARM: dts: OMAP2+: Fix NAND device nodes Roger Quadros
2015-07-10 12:23 ` [PATCH 12/12] ARM: dts: omap3: Fix gpmc memory resource size Roger Quadros
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=20150713071008.GC26485@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@ti.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).