[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201103301338.57207.arnd@arndb.de>
Date: Wed, 30 Mar 2011 13:38:56 +0200
From: Arnd Bergmann <arnd@...db.de>
To: "Subhasish Ghosh" <subhasish@...tralsolutions.com>
Cc: linux-arm-kernel@...ts.infradead.org,
davinci-linux-open-source@...ux.davincidsp.com,
sachi@...tralsolutions.com, "Samuel Ortiz" <sameo@...ux.intel.com>,
nsekhar@...com, "open list" <linux-kernel@...r.kernel.org>,
m-watkins@...com, "Marc Kleine-Budde" <mkl@...gutronix.de>
Subject: Re: [PATCH v3 1/7] mfd: add pruss mfd driver.
On Wednesday 30 March 2011, Subhasish Ghosh wrote:
> I am using a .setup to initialize pin mux etc. To use the mfd_cells directly
> should I
> use .enable and .disable of the mfd_cells instead of the .setup.
I think it would be best not to define any per-board functions that
are needed to set up the cell, but rather to initialize it from
the ->probe function of the cell specific driver.
If you need board specific data such as GPIO lists, you can pass
them in the mfd_cell platform_data.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists