On 2/24/2012 5:00 AM, Rajendra Nayak wrote:
On Friday 24 February 2012 12:27 AM, Tony Lindgren wrote:
--- a/arch/arm/boot/dts/omap3.dtsi
+++ b/arch/arm/boot/dts/omap3.dtsi
@@ -113,5 +113,31 @@
#size-cells =0;
ti,hwmods = i2c3;
};
+
+ mmc1: mmc@1 {
+ compatible = ti,omap2-hsmmc;
+ ti,hwmods =
On 2/24/2012 12:35 PM, Rajendra Nayak wrote:
On Friday 24 February 2012 05:02 PM, T Krishnamoorthy, Balaji wrote:
On Thu, Feb 23, 2012 at 5:31 PM, Rajendra Nayakrna...@ti.com wrote:
Define dt bindings for the ti-omap-hsmmc, and adapt
the driver to extract data (which was earlier passed as
On 2/24/2012 1:58 PM, Rajendra Nayak wrote:
On Friday 24 February 2012 06:21 PM, Cousson, Benoit wrote:
On 2/24/2012 12:35 PM, Rajendra Nayak wrote:
On Friday 24 February 2012 05:02 PM, T Krishnamoorthy, Balaji wrote:
On Thu, Feb 23, 2012 at 5:31 PM, Rajendra Nayakrna...@ti.com wrote
On 2/17/2012 2:44 PM, Daniel Mack wrote:
ping? Could anyone care for queueing this please?
There is no OMAP HSMMC dedicated maintainer anymore so I guess you should ping
Chris Ball c...@laptop.org.
Regards,
Benoit
--
To unsubscribe from this list: send the line unsubscribe linux-mmc in
the
Hi Balaji,
On 6/30/2011 9:04 PM, Krishnamoorthy, Balaji T wrote:
Removing the custom state machine - lazy disable framework in omap_hsmmc
to make way for runtime pm to handle host controller
power states.
This allows mmc_host_enable/mmc_host_disable to be replaced by
runtime get_sync and
Hi Balaji,
On 6/22/2011 4:18 PM, Krishnamoorthy, Balaji T wrote:
Removing the custom state machine - lazy disable framework in omap_hsmmc
to make way for runtime pm to handle host controller
power states.
This allows mmc_host_enable/mmc_host_disable to be replaced by
runtime get_sync and
On 6/22/2011 4:18 PM, Krishnamoorthy, Balaji T wrote:
After runtime conversion to handle clk,
iclk node is not used
However fclk node is still used to get clock rate.
Signed-off-by: Balaji T Kbalaj...@ti.com
---
drivers/mmc/host/omap_hsmmc.c | 10 --
1 files changed, 0
Hi Kishore,
On 2/24/2011 8:26 PM, Kadiyala, Kishore wrote:
Adding hwmod data for hsmmc device on OMAP2430/OMAP3/OMAP4.
Adapting the omap_hsmmc driver to hwmod framework.
The patch series is based on omap-for-linus and tested on
OMAP2430, OMAP3430SDP OMAP4430SDP.
Also boot tested on
On 2/25/2011 2:06 PM, Kadiyala, Kishore wrote:
Hi Benoit,
On Fri, Feb 25, 2011 at 6:24 PM, Cousson, Benoitb-cous...@ti.com wrote:
Hi Kishore,
On 2/24/2011 8:26 PM, Kadiyala, Kishore wrote:
Adding hwmod data for hsmmc device on OMAP2430/OMAP3/OMAP4.
Adapting the omap_hsmmc driver to hwmod
Hi Kishore,
On 2/24/2011 8:26 PM, Kadiyala, Kishore wrote:
Add a device attribute to hwmod data of omap2430, omap3, omap4.
Currently the device attribute holds information regarding dual volt MMC card
support by the controller which will be later passed to the host driver via
platform data.
Hi Kishore,
On 2/23/2011 6:47 PM, Kadiyala, Kishore wrote:
Adding hwmod data for hsmmc device on OMAP2430/OMAP3/OMAP4.
Adapting the omap_hsmmc driver to hwmod framework.
The patch series is based on -rc6 and tested on OMAP2430, OMAP3430SDP
OMAP4430SDP.
Could you rebase it on top of
On 2/23/2011 6:47 PM, Kadiyala, Kishore wrote:
From: Anand Gadiyargadi...@ti.com
Enabling hsmmc hwmod for OMAP4
Signed-off-by: Anand Gadiyargadi...@ti.com
Signed-off-by: Kishore Kadiyalakishore.kadiy...@ti.com
Cc: Benoit Coussonb-cous...@ti.com
Cc: Paul Walmsleyp...@pwsan.com
CC: Kevin
On 2/23/2011 6:47 PM, Kadiyala, Kishore wrote:
Add a device attribute to hwmod data of omap2430, omap3, omap4.
Currently the device attribute holds information regarding dual volt MMC card
support by the controller which will be later passed to the host driver via
platform data.
Signed-off-by:
On 2/23/2011 6:47 PM, Kadiyala, Kishore wrote:
Changes involves:
1) Remove controller reset in devices.c which is taken care of
by hwmod framework.
2) Removing all base address macro defines except keeping one for OMAP2420.
3) Using omap-device layer to register device and utilizing data
On 2/24/2011 2:55 PM, Kadiyala, Kishore wrote:
On Thu, Feb 24, 2011 at 5:19 PM, Cousson, Benoitb-cous...@ti.com wrote:
On 2/23/2011 6:47 PM, Kadiyala, Kishore wrote:
[...]
static struct hsmmc_controller {
charname[HSMMC_NAME_LEN + 1];
-}
Hi Kishore
On 9/18/2010 6:34 PM, Kadiyala, Kishore wrote:
The offset handling implementation of omap4 mmc registers which
was already present can't be reused once hwmod modifications are done
for mmc driver.
Since hwmod data file for OMAP4 is an auto generated the base
address for MMC will
Hi Kishore,
On 8/30/2010 7:48 PM, Kadiyala, Kishore wrote:
OMAP4 not only have newly added hsmmc registers but also
have registers which were there in OMAP3 and which doesn't
have a common offset deviation compared to OMAP3.
For generic handling, OMAP3 and OMAP4 has different array's of
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of David Vrabel
Sent: Wednesday, February 17, 2010 7:10 PM
David Vrabel wrote:
+static void omap_hsmmc_enable_sdio_irq(struct mmc_host *mmc, int enable)
+{
+struct omap_hsmmc_host *host =
18 matches
Mail list logo
