Message-ID: <1389638849.24905.51.camel@snotra.buserror.net>
Subject: Re: [PATCH] Driver/IFC: Move Freescale IFC driver to a common driver
From: Scott Wood <scottwood@freescale.com>
To: Arnd Bergmann <arnd@arndb.de>
CC: Prabhakar Kushwaha <prabhakar@freescale.com>, <gregkh@linuxfoundation.org>,
        <linux-kernel@vger.kernel.org>
Date: Mon, 13 Jan 2014 12:47:29 -0600
In-Reply-To: <201401131432.36880.arnd@arndb.de>
References: <1389590671-20289-1-git-send-email-prabhakar@freescale.com>
	 <201401131432.36880.arnd@arndb.de>
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

On Mon, 2014-01-13 at 14:32 +0100, Arnd Bergmann wrote:
> On Monday 13 January 2014, Prabhakar Kushwaha wrote:
> > Freescale IFC controller has been used for mpc8xxx. It will be used
> > for ARM-based SoC as well. This patch moves the driver to driver/misc
> > and fix the header file includes.
> > 
> > Signed-off-by: Prabhakar Kushwaha <prabhakar@freescale.com>
> 
> No objections to the driver, but drivers/misc doesn't seem like the
> right place. Why not drivers/mfd or drivers/memory?

It's not a memory controller in the sense that I think most people would
interpret the phrase, but I guess it's similar in function to
mvebu-devbus.  If drivers/memory is broad enough to cover such things,
and doesn't have a memory controller subsystem that drivers are supposed
to register with, then that could work.

Are things in drivers/mfd expected to interact with mfd-core.c?  It's
not clear to me what that does or how it would be useful to the IFC
code.

-Scott


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/