Hi Chris,
would you like to take this one, or should we merge it through the OMAP
tree?
- Paul
From: Paul Walmsley p...@pwsan.com
Date: Fri, 25 Feb 2011 18:22:08 -0700
Subject: [PATCH] MMC: omap_hsmmc: enable interface clock before calling
mmc_host_enable()
The code path entered via
Hi Paul,
On Fri, Feb 25, 2011 at 06:26:45PM -0700, Paul Walmsley wrote:
Hi Chris,
would you like to take this one, or should we merge it through the OMAP
tree?
Thanks for asking -- OMAP folks seem to like merging patches to host/*omap*
directly through the OMAP tree, and that's fine with
Hi Chris,
On Sat, 26 Feb 2011, Chris Ball wrote:
Thanks for asking -- OMAP folks seem to like merging patches to host/*omap*
directly through the OMAP tree, and that's fine with me; I don't want to
get in the way of a good workflow with responsive maintainers. I do like
the patches to be
On Tue, Dec 7, 2010 at 5:27 PM, Paul Walmsley p...@pwsan.com wrote:
In the OMAP HSMMC driver, the code path entered via mmc_host_enable() can
include register accesses to the HSMMC IP block. For this to work, both
the device interface clock and functional clock need to be enabled before
In the OMAP HSMMC driver, the code path entered via mmc_host_enable() can
include register accesses to the HSMMC IP block. For this to work, both
the device interface clock and functional clock need to be enabled before
mmc_host_enable() is called. However, omap_hsmmc_probe() calls
