Marek Szyprowski wrote:
> Hello,
>
> On Thursday, September 16, 2010 10:37 AM Jeongbae Seo wrote:
>
> > From: Hyuk Lee
> >
> > This patch adds to support HSMMC for S5PV310 and S5PC210 and setup for
> > HSMMC host controller and also related GPIO.
> > At most 4 channel can be used at the same tim
Marek Szyprowski wrote:
> Hello,
>
> I'm sorry for a late replay, I've just noticed this patch and have some
> comments.
>
> On Thursday, September 16, 2010 10:37 AM Jeongbae Seo wrote:
>
> > From: Hyuk Lee
> >
> > This patch adds to use of HSMMC on S5PV310 and S5PC210.
> > The HSMMC platform d
Hi David,
On Thu, Sep 30, 2010 at 08:03:14PM -0700, Philip Rakity wrote:
> From: Philip Rakity
> Date: Thu, 30 Sep 2010 15:34:24 -0700
> Subject: [PATCH] sdhci: adjust sd 3.0 host controller spec clock divider
>
> The sd 3.0 host spec does not require the clock divider to be a power of 2.
>
> S
Hi Linus,
On Thu, Sep 30, 2010 at 09:22:17AM +0200, Linus Walleij wrote:
> That's it. If there is interest I can surely pick it up and wrap the
> current enable/disable calls around it or even rewrite all drivers
> to use the set_ios() approach as in this patchset I think.
>
> What happened was t
On Mon, Oct 4, 2010 at 10:33 AM, Madhusudhan wrote:
>
>
>> -Original Message-
>> From: Steve Sakoman [mailto:sako...@gmail.com]
>> Sent: Monday, October 04, 2010 11:57 AM
>> To: Madhusudhan
>> Cc: Mike Rapoport; David Vrabel; Chris Ball; linux-mmc@vger.kernel.org;
>> linux-o...@vger.kernel
> -Original Message-
> From: Steve Sakoman [mailto:sako...@gmail.com]
> Sent: Monday, October 04, 2010 11:57 AM
> To: Madhusudhan
> Cc: Mike Rapoport; David Vrabel; Chris Ball; linux-mmc@vger.kernel.org;
> linux-o...@vger.kernel.org
> Subject: Re: [PATCH 0/2] mmc: omap_hsmmc: support SDIO
On Mon, Oct 4, 2010 at 9:45 AM, Madhusudhan wrote:
>
>
>> -Original Message-
>> From: Steve Sakoman [mailto:sako...@gmail.com]
>> Sent: Monday, October 04, 2010 11:32 AM
>> To: Mike Rapoport
>> Cc: David Vrabel; Chris Ball; linux-mmc@vger.kernel.org; linux-
>> o...@vger.kernel.org; madhu..
> -Original Message-
> From: Steve Sakoman [mailto:sako...@gmail.com]
> Sent: Monday, October 04, 2010 11:32 AM
> To: Mike Rapoport
> Cc: David Vrabel; Chris Ball; linux-mmc@vger.kernel.org; linux-
> o...@vger.kernel.org; madhu...@ti.com
> Subject: Re: [PATCH 0/2] mmc: omap_hsmmc: support
On Wed, Sep 1, 2010 at 11:02 PM, Mike Rapoport wrote:
> David Vrabel wrote:
>>
>> On 27/08/2010 20:22, Chris Ball wrote:
>>>
>>> Hi David,
>>>
>>> On Mon, Feb 22, 2010 at 02:24:17PM +, David Vrabel wrote:
These patches add support for SDIO cards to the omap_hsmmc driver.
Power m
From: Xiaochen Shen
Basic support for the Intel Medfield devices
Give them their own quirks as we will need to update this later.
Signed-off-by: Xiaochen Shen
Signed-off-by: Alan Cox
---
drivers/mmc/host/sdhci-pci.c | 48 ++
include/linux/pci_ids.h
From: Xiaochen Shen
Basic support for the Intel Medfield devices
Give them their own quirks as we will need to update this later.
Signed-off-by: Xiaochen Shen
Signed-off-by: Alan Cox
---
drivers/mmc/host/sdhci-pci.c | 48 ++
include/linux/pci_ids.h
From: Alan Cox
Currently we write it to the chip data, but if the probe handler overrides
it we ignore the new value and keep using our cached one. Fix this so that
a probe handler can adjust the slot count
Signed-off-by: Alan Cox
---
drivers/mmc/host/sdhci-pci.c |2 ++
1 files changed, 2
From: Alan Cox
This adds the basic identifiers. Due to the various chip quirks it's not
enough to make MRST support very useful for earlier steppings but that can
follow.
(I'm currently trying to verify which steps actually matter outside Intel
so I can avoid unneeded stuff going upstream)
[Ex
This adds the basic identifiers. Due to the various chip quirks it's not
enough to make MRST support very useful for earlier steppings but that can
follow.
(I'm currently trying to verify which steps actually matter outside Intel
so I can avoid unneeded stuff going upstream)
[Extracted from orig
This implements the basic bits, it's not sufficient for the early steppings
but I want to verify which early steppings are actually worth supporting
outside of Intel before I resubmit the various callback quirk stuff.
---
Alan Cox (2):
sdhci: Add Moorestown devices
sdhci: Allow the pro
Try again...
This adds basic support for the Intel MID platform devices. It doesn't include
the callback stuff to handle some of the errata but I'm trying to verify
which if any of those make sense outside of Intel before resubmitting that
bit.
---
Alan Cox (2):
sdhci: Add Moorestown devic
Currently we write it to the chip data, but if the probe handler overrides
it we ignore the new value and keep using our cached one. Fix this so that
a probe handler can adjust the slot count
Signed-off-by: Alan Cox
---
drivers/mmc/host/sdhci-pci.c |2 ++
1 files changed, 2 insertions(+), 0
Hello,
I'm sorry for a late replay, I've just noticed this patch and have some
comments.
On Thursday, September 16, 2010 10:37 AM Jeongbae Seo wrote:
> From: Hyuk Lee
>
> This patch adds to use of HSMMC on S5PV310 and S5PC210.
> The HSMMC platform data like card detect, data bus width
> and c
Hello,
On Thursday, September 16, 2010 10:37 AM Jeongbae Seo wrote:
> From: Hyuk Lee
>
> This patch adds to support HSMMC for S5PV310 and S5PC210 and setup for
> HSMMC host controller and also related GPIO.
> At most 4 channel can be used at the same time.
> A user can configure SDHCI data bus
> In the near future I'll have to start using SDIO and eMMC devices.
> I wonder if I'll be able to continue to use the platform driver or if
> I'll need to actually have own driver (to solve specific limits/features
> due to our Hw) or if we'll extend the sdhci-pltfm d.d.
>
> What do you thin
Hi,
we are running an embedded system here based on the PXA300 platform.
Suspend/resume used to work well so far. However after upgrading the
kernel from 2.6.34.7 to 2.6.35.6, we get the following error when trying
to suspend the system:
# echo "mem" > "/sys/power/state"
[ 5647.295953] PM: Syncin
On Mon, Oct 4, 2010 at 3:30 PM, Sven Neumann wrote:
> Hi,
>
> we are running an embedded system here based on the PXA300 platform.
> Suspend/resume used to work well so far. However after upgrading the
> kernel from 2.6.34.7 to 2.6.35.6, we get the following error when trying
> to suspend the syst
Hi Chris.
On 10/01/2010 01:25 AM, Chris Ball wrote:
> Looks like we're waiting for a version of your STM driver with final
> changes from Wolfram's review -- do you think you'll submit that soon?
Concerning the stm driver I've a doubt: currently on our platforms I can
use both the sdhci-stm and s
23 matches
Mail list logo
