Hello Folks,
Sorry for interruption.
I wanted to know when and which version of kernel mmc driver will have SD
4.0(UHS-II) support?
Regards,
Sachin Nikam.
NVIDIA.
-Original Message-
From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-ow...@vger.kernel.org]
On Behalf Of Arindam Nath
From: Philip Rakity
eMMC voltage change not required for 1.8V. 3.3V and 1.8V vcc
are capable of doing DDR. vccq of 1.8v is not required.
Signed-off-by: Philip Rakity
Reviewed-by: Arindam Nath
---
drivers/mmc/core/core.c | 14 ++
drivers/mmc/core/core.h |2 --
drivers/mmc/
From: Philip Rakity
eMMC chips do not use CMD11 when changing voltage. Add extra
argument to call to indicate if CMD11 needs to be sent.
Signed-off-by: Philip Rakity
Reviewed-by: Arindam Nath
---
drivers/mmc/core/core.c |5 +++--
drivers/mmc/core/core.h |3 ++-
drivers/mmc/core/sd.c
From: Philip Rakity
Marvell controller requires 1.8V bit in UHS control register 2
be set when doing UHS. eMMC does not require 1.8V for DDR.
add platform code to handle this.
Signed-off-by: Philip Rakity
Reviewed-by: Arindam Nath
---
drivers/mmc/host/sdhci-pxa.c | 41 +
From: Philip Rakity
Allow platform specific code to set UHS registers if
implementation requires speciial platform specific handling
Signed-off-by: Philip Rakity
Reviewed-by: Arindam Nath
---
drivers/mmc/host/sdhci.c | 33 ++---
drivers/mmc/host/sdhci.h |2 ++
V2
[PATCH 1/4]: Fixed tabbing for comment.
[PATCH 2/4]: Use switch-case instead of if-else.
[PATCH 3/4]: Use bool type for argument *cmd11* instead of int.
Philip Rakity (4):
[PATCH 1/4]: sdhci add hooks for UHS setting by platform specific code
[PATCH 2/4]: sdhci-pxa add platform specifi
Hello Folks,
Sorry for interruption.
I wanted to know when and which version of mmc driver will have SD 4.0(UHS-II)
support?
Regards,
Sachin Nikam.
NVIDIA.
-Original Message-
From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-ow...@vger.kernel.org]
On Behalf Of Chris Ball
Sent: Thu
Hi Chris..
My question is others..I agreed the using frequency table..
But my questions is this...
For example, if f_min is 300KHz, you can the below message.
mmc1: mmc_rescan_try_freq: trying to init card at 40 Hz
mmc1: mmc_rescan_try_freq: trying to init card at 30 Hz
mmc1: mmc_rescan_
All other platform specific code is in the host/ directory.
This moves it to arch/arm
If that is the direction the group wants to go in --> then the patch is fine
provided the mmc group can review the patches.
Otherwise they are handled by the arm maintainer.
On May 12, 2011, at 3:25 PM, Chri
Hi,
On Wed, May 11 2011, Tony Olech wrote:
> With reference to Arnd's summation of issues with the
> previous version of the patch which can be found at
> "http://ns3.spinics.net/lists/linux-mmc/msg06693.html";
> I have made nearly all of the changes requested.
>
> I have not removed of the __pack
Hi,
On Thu, Apr 28 2011, zhangfei gao wrote:
> Subject: [PATCH 2/2] sdhci-pxa: add call back interface to share sdhci-pxa
>
> Call back functions is added to support mmp2, pxa910, and pxa955
>
> Signed-off-by: Zhangfei Gao
> Signed-off-by: RaymondWu
> Signed-off-by: Jun Nie
This patchset
Hi, (adding Nico to CC in case he has comments)
On Mon, May 09 2011, Eliad Peller wrote:
> Since the MMC_PM_KEEP_POWER flag should be set on each suspend,
> it should also cleared on each resume.
>
> Upon resuming, we have to know if power was kept
> (for re-initialization, etc.), so clear it just
Hi Jaehoon,
On Wed, May 11 2011, Jaehoon Chung wrote:
> In suspend function, regulator_enable() need not.
> regulator_enable() should be locate in resume function.
>
> Signed-off-by: Jaehoon Chung
> Signed-off-by: Kyungmin Park
> ---
> drivers/mmc/host/dw_mmc.c |6 +++---
> 1 files changed,
Hi Guennadi,
On Thu, May 12 2011, Guennadi Liakhovetski wrote:
>> > Please could you send a full patchset against mmc-next for tmio for .40?
>>
>> Can I also base my patches on next-2.6? I need both - latest mmc and pm,
>> so, using next would make it much easier.
>
> I rebased my stack on top o
Forwarding to linux-mmc@.
From: bugzilla-dae...@bugzilla.kernel.org
Subject: [Bug 35002] New: SDHC memory card causes divide error: [#1]
PREEMPT SMP
https://bugzilla.kernel.org/show_bug.cgi?id=35002
Summary: SDHC memory card causes divide error: [#1]
PRE
Hi,
On Thu, May 12 2011, Huang Changming-R66093 wrote:
> The required min frequency (f_min) is 400KHz during identify stage, is
> it necessary to use the frequency table (freqs[], including 300KHz,
> 200KHz and 100KHz)?
Yes. Some hardware is buggy/out of compliance with the spec.
- Chris.
--
C
This patch didn't point that..
Huang Changming-R66093 wrote:
> The required min frequency (f_min) is 400KHz during identify stage, is it
> necessary to use the frequency table (freqs[], including 300KHz, 200KHz and
> 100KHz)?
i known that some card needs lower than 400KHz..so this approach is
* Adrian Hunter [110506 02:11]:
> eMMC may have a hardware reset line connected to a gpio,
> so pass it to the driver.
>
> Signed-off-by: Adrian Hunter
This looks safe to merge via MMC list:
Acked-by: Tony Lindgren
> ---
> arch/arm/mach-omap2/hsmmc.c |5 +
> arch/arm/mach-
* Adrian Hunter [110506 02:13]:
> From: Andy Shevchenko
>
> There are 3 new platform data methods which should help us to do a clock
> switching when notification is happened or request is started.
>
> The purpose of the patch is to avoid high frequency of MMC controller on low
> OPPs due to an
On Thu, 12 May 2011, Guennadi Liakhovetski wrote:
> Hi Chris
>
> On Tue, 10 May 2011, Chris Ball wrote:
>
> > Hi Guennadi,
> >
> > On Fri, Apr 29 2011, Guennadi Liakhovetski wrote:
> > > DMA mode has to be re-enabled during a resume.
> > >
> > > Signed-off-by: Guennadi Liakhovetski
> > > ---
>
Hi all,
I just posted three patches to use get_cd to detect the card (somebody has saw
them, But I didn't receive them from Linux-mmc, I don't know why):
[PATCH 1/3] SDHCI: add sdhci_get_cd callback to detect the card
[PATCH 2/3] MMC/SD: add callback function to detect card
[PATCH 3/3] SDHC/MMC: a
On Thu, May 12, 2011 at 4:46 AM, Chris Ball wrote:
> Hi,
>
> On Wed, May 11 2011, Jaehoon Chung wrote:
>> Hi Chris..
>>
>> I think you're confused something because my explanation.
>>
>> My means..if we use the regulator, regulator is enabled when probing.
>> Then regulator is enabling until we do
The required min frequency (f_min) is 400KHz during identify stage, is it
necessary to use the frequency table (freqs[], including 300KHz, 200KHz and
100KHz)?
Thanks and Best Regards
Jerry Huang
> -Original Message-
> From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-
> ow...@vg
Hi Chris..
Chris Ball wrote:
> Hi Jaehoon,
>
> On Fri, May 06 2011, Jaehoon Chung wrote:
>> This patch added mmc_power_off after mmc_attach_sd()
>>
>> i found that didn't detect the second card insert.(using SDHCI)
>> you can see the below log.
>>
>> i want to know that somebody know this issue..
Hi Chris
On Tue, 10 May 2011, Chris Ball wrote:
> Hi Guennadi,
>
> On Fri, Apr 29 2011, Guennadi Liakhovetski wrote:
> > DMA mode has to be re-enabled during a resume.
> >
> > Signed-off-by: Guennadi Liakhovetski
> > ---
> > drivers/mmc/host/tmio_mmc_dma.c | 21 -
> > dri
when running mmc_rescan_try_freq(), try to init two times with last frequency.
For example, assume that host->f_min is 400KHz, we can find the below message.
mmc1: mmc_rescan_try_freq: trying to init card at 40 Hz
mmc1: mmc_rescan_try_freq: trying to init card at 40 Hz
i didn't find to me
26 matches
Mail list logo
