2014-03-24 17:02 GMT+01:00 Ulf Hansson :
> On 24 March 2014 15:59, Andreas Fenkart wrote:
>> Hi,
>>
>> 2014-03-24 13:43 GMT+01:00 Ulf Hansson :
>>> On 21 March 2014 17:17, Balaji T K wrote:
From: Andreas Fenkart
There have been various patches floating around for enabling
the
On Sun, Mar 23, 2014 at 11:19 PM, Adrian Hunter wrote:
> On 24.03.2014 03:43, Andrew Bresticker wrote:
>> sdhci_request() and sdhci_card_event() read the cd-gpio via
>> mmc_gpio_get_cd(), which can sleep, while holding host->lock.
>> This may result in the following BUG:
>>
>> BUG: spinlock wron
On 24 March 2014 15:59, Andreas Fenkart wrote:
> Hi,
>
> 2014-03-24 13:43 GMT+01:00 Ulf Hansson :
>> On 21 March 2014 17:17, Balaji T K wrote:
>>> From: Andreas Fenkart
>>>
>>> There have been various patches floating around for enabling
>>> the SDIO IRQ for hsmmc, but none of them ever got merg
On 14 March 2014 13:16, Seungwon Jeon wrote:
> This patch adds HS400 mode support for eMMC5.0 device.
> HS400 mode is high speed DDR interface timing from HS200.
> Clock frequency is up to 200MHz and only 8-bit bus width is
> supported. In addition, tuning process of HS200 is required
> to synchro
Hi,
2014-03-24 13:43 GMT+01:00 Ulf Hansson :
> On 21 March 2014 17:17, Balaji T K wrote:
>> From: Andreas Fenkart
>>
>> There have been various patches floating around for enabling
>> the SDIO IRQ for hsmmc, but none of them ever got merged.
>>
>> Probably the reason for not merging the SDIO int
On Wed, Mar 19, 2014 at 04:39:45PM -0700, Mike Turquette wrote:
> Quoting Maxime Ripard (2014-02-18 06:05:16)
> > On Mon, Feb 17, 2014 at 11:02:15AM +0100, David Lanzendörfer wrote:
> > > From: Emilio López
> > >
> > > This commit implements .determine_rate, so that our factor clocks can be
> > >
Hi,
On Wed, Mar 12 2014, Matt Porter wrote:
> On Mon, Sep 23, 2013 at 10:20:35AM -0700, Christian Daudt wrote:
>> Currently ARCH_BCM has been used for Broadcom
>> Mobile V7 based SoCs. In order to allow other Broadcom
>> SoCs to also use mach-bcm directory and files, this patch
>> renames the orig
On 22 March 2014 13:04, Seungwon Jeon wrote:
> On Fri, March 21, 2014, Ulf Hansson wrote:
>> On 14 March 2014 13:16, Seungwon Jeon wrote:
>> > Current implementation for bus speed mode selection is too
>> > complicated. This patch is to simplify the codes and remove
>> > some duplicate parts.
>>
On 21 March 2014 17:17, Balaji T K wrote:
> From: Andreas Fenkart
>
> There have been various patches floating around for enabling
> the SDIO IRQ for hsmmc, but none of them ever got merged.
>
> Probably the reason for not merging the SDIO interrupt patches
> has been the lack of wake-up path for
Mon, 24 Mar 2014 10:29:45 +0100 от Ulf Hansson :
> On 22 March 2014 09:52, Alexander Shiyan wrote:
> > Replace existing resource handling in the driver with managed
> > device resource, this ensures more consistent error values and
> > simplifies error paths.
> >
> > Signed-off-by: Alexander Shiya
Hi,
I've tested the branch omap_hsmmc_sdio_irq_devm_cleanup on custom OMAP5
based board.
We have mwifiex connected to MMC3.
I used two approaches:
* Using dat1 line as GPIO with dynamic remuxing
* Using separate GPIO connected to dat1 with static mux settings
Both works just fine. Thanks And
On 22 March 2014 09:52, Alexander Shiyan wrote:
> Replace existing resource handling in the driver with managed
> device resource, this ensures more consistent error values and
> simplifies error paths.
>
> Signed-off-by: Alexander Shiyan
> ---
> drivers/mmc/host/mxcmmc.c | 101
> ++
12 matches
Mail list logo
