Adrian,
Let me rephrase my question.
I don't see why both CAPS are needed and why the voltage is specified in the
CAPS. If my understanding is correct the voltage range supported by the host
controller is known in the MMC layer. If the voltage range is supported and
the MMC chip capabil
On 01/10/10 06:01, ext Philip Rakity wrote:
I was wondering if we could remove one of the CAPS for DDR voltage
(MMC_CAP_1_8V_DDR and MMC_CAP_1_2V_DDR). Both 1.2 and 1.8v are defined in the
JEDEC Standard No. 84-A441.
The sd 3.0 host controller only defines the option for 1.8v. I cannot see a
I was wondering if we could remove one of the CAPS for DDR voltage
(MMC_CAP_1_8V_DDR and MMC_CAP_1_2V_DDR). Both 1.2 and 1.8v are defined in the
JEDEC Standard No. 84-A441.
The sd 3.0 host controller only defines the option for 1.8v. I cannot see a
way to set 1.2v.
If this makes sense I can
Hi,
On Tue, Aug 24, 2010 at 01:30:45PM +0300, Adrian Hunter wrote:
> From: Adrian Hunter
> Date: Tue, 24 Aug 2010 13:20:26 +0300
> Subject: [PATCH] mmc: Fix Dual Data Rate (DDR) support
>
> The DDR support patch needs the following fixes:
>
> - The block driver does not need to know about DDR, an
On Fri, Jul 09, 2010 at 12:29:40PM +0530, Hanumath Prasad wrote:
> Add support for Dual Data Rate MMC cards as defined in the 4.4
> specification.
>
> Cc: linux-mmc@vger.kernel.org
> Acked-by: Linus Walleij
> Signed-off-by: Hanumath Prasad
Thanks very much, pushed to mmc-next along with Zhangfe
On Wed, Sep 22, 2010 at 10:20 AM, Chris Ball wrote:
> Hi,
>
> On Mon, Sep 20, 2010 at 10:04:39AM +0530, Ghorai, Sukumar wrote:
>> Chris and all,
>> Can we plan these patches for 2.6.37 release?
>> Also let me know if I can do anything!
>
> I would like to merge this for .37, and the quirk and merg
Hi,
On Mon, Sep 20, 2010 at 10:04:39AM +0530, Ghorai, Sukumar wrote:
> Chris and all,
> Can we plan these patches for 2.6.37 release?
> Also let me know if I can do anything!
I would like to merge this for .37, and the quirk and merge conflicts
are not a big deal. First, though, I'd like to see
st.st.com;
> Hanumath Prasad; Kyungmin Park
> Subject: RE: [PATCH] mmc: MMC 4.4 DDR support
>
>
> > -Original Message-
> > From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-
> > ow...@vger.kernel.org] On Behalf Of Chris Ball
> > Sent: Tuesday,
l.org;
> linux-ker...@vger.kernel.org; stericsson_nomadik_li...@list.st.com;
> Hanumath Prasad; Kyungmin Park
> Subject: Re: [PATCH] mmc: MMC 4.4 DDR support
>
> Hi Hanumath, Linus,
>
> On Tue, Aug 24, 2010 at 01:30:45PM +0300, Adrian Hunter wrote:
> > I am not able to t
Hi Hanumath, Linus,
On Tue, Aug 24, 2010 at 01:30:45PM +0300, Adrian Hunter wrote:
> I am not able to test DDR mode but it look to me that the patch
> should be changed. Here is a fix:
>
> From: Adrian Hunter
> Date: Tue, 24 Aug 2010 13:20:26 +0300
> Subject: [PATCH] mmc: Fix Dual Data Rate (DDR
On Tue, Sep 14, 2010 at 01:33:22AM +0100, Chris Ball wrote:
> Hi,
>
> On Mon, Aug 23, 2010 at 05:45:28PM -0400, Chris Ball wrote:
> > Sounds good -- if no-one objects, I'll send e-mail to ftpad...@k.o
> > tomorrow asking for linux-mmc@ to be added to patchwork.k.o.
>
> This is up now: https://pa
Hi,
On Mon, Aug 23, 2010 at 05:45:28PM -0400, Chris Ball wrote:
> Sounds good -- if no-one objects, I'll send e-mail to ftpad...@k.o
> tomorrow asking for linux-mmc@ to be added to patchwork.k.o.
This is up now: https://patchwork.kernel.org/project/linux-mmc/list/
J.H. kindly piped in the last
Andrew Morton wrote:
On Mon, 23 Aug 2010 21:48:29 +0100
Matt Fleming wrote:
On Sat, Aug 21, 2010 at 06:37:45PM -0400, Chris Ball wrote:
Hi,
> Hm is there some problem with this patch or has the processing of
> it simply stalled? When I read the thread I cannot see Hanumaths
> answer
On Mon, 23 Aug 2010 17:45:28 -0400
Chris Ball wrote:
> Hi,
>
>> It's possible Andrew has a reason that hasn't been picked up yet.
>>
>> Maybe what we really need is to get patchwork setup for the
>> linux-mmc list? Other subsystem maintainers swear by it. That
>> way, it'd b
Hi,
> It's possible Andrew has a reason that hasn't been picked up yet.
>
> Maybe what we really need is to get patchwork setup for the
> linux-mmc list? Other subsystem maintainers swear by it. That
> way, it'd be much harder for patches to go unnoticed.
Sounds good -- if no-one
On Mon, 23 Aug 2010 21:48:29 +0100
Matt Fleming wrote:
> On Sat, Aug 21, 2010 at 06:37:45PM -0400, Chris Ball wrote:
> > Hi,
> >
> >> Hm is there some problem with this patch or has the processing of
> >> it simply stalled? When I read the thread I cannot see Hanumaths
> >> answers o
On Sat, Aug 21, 2010 at 06:37:45PM -0400, Chris Ball wrote:
> Hi,
>
>> Hm is there some problem with this patch or has the processing of
>> it simply stalled? When I read the thread I cannot see Hanumaths
>> answers on the list but it looks mainly like the patch is OK and
>> there
2010/8/22 Chris Ball :
> I'd like to dedicate more time to mmc/. Do you think it'd be useful
> for me to catch all the patches sent to linux-mmc@ into a public Git
> tree, and periodically report on what went upstream via akpm and
> what's still waiting?
That sounds very close to getting it part
Hi,
> Hm is there some problem with this patch or has the processing of
> it simply stalled? When I read the thread I cannot see Hanumaths
> answers on the list but it looks mainly like the patch is OK and
> there is some chit-chat.
>
> Can it be picked up? Everyone is going to
2010/7/9 Hanumath Prasad :
> Add support for Dual Data Rate MMC cards as defined in the 4.4
> specification.
Hm is there some problem with this patch or has the processing
of it simply stalled? When I read the thread I cannot see Hanumaths
answers on the list but it looks mainly like the patch is
-Original Message-
> From: kyungmi...@gmail.com [mailto:kyungmi...@gmail.com] On Behalf Of
> Kyungmin Park
> Sent: Saturday, July 10, 2010 10:58 AM
> To: P.Hanumath PRASAD
> Cc: linux-ker...@vger.kernel.org; STEricsson_nomadik_linux; Linus WALLEIJ;
> linux-mmc@vger.kerne
On Sat, Jul 10, 2010 at 2:28 PM, Kyungmin Park wrote:
> Hi,
>
> Looks good to me except where's use the MMC_DDR_MODE. why do you set
> brq.data.flags |= MMC_DDR_MODE?
>
> Now my SDHCI host don't support eMMC 4.4 but the end of july I can test it.
Fixing eMMC 4.4 means DDR features at host.
>
> Tha
Hi,
Looks good to me except where's use the MMC_DDR_MODE. why do you set
brq.data.flags |= MMC_DDR_MODE?
Now my SDHCI host don't support eMMC 4.4 but the end of july I can test it.
Thank you,
Kyungmin Park
On Fri, Jul 9, 2010 at 3:59 PM, Hanumath Prasad
wrote:
> Add support for Dual Data Rate
23 matches
Mail list logo