From: Balaji T K <balajitk@ti.com>
To: balbi@ti.com
Cc: chris@printf.net, ulf.hansson@linaro.org,
linux-mmc@vger.kernel.org,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] mmc: host: omap_hsmmc: a few improvements
Date: Tue, 22 Apr 2014 21:00:12 +0530 [thread overview]
Message-ID: <53568B04.4050703@ti.com> (raw)
In-Reply-To: <20140421173203.GH22794@saruman.home>
On Monday 21 April 2014 11:02 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Mar 26, 2014 at 07:04:45PM -0500, Felipe Balbi wrote:
>> this series lets us access the newer registers introduced
>> back in OMAP4 which give us some valid information about
>> the OMAP HSMMC IP like max block size, support for ADMA,
>> support for Retention.
>>
>> Right now, only setting max_blk_size correctly as supporting
>> ADMA and Retention will take a lot of work.
>>
>> Tested on OMAP5 uEVM.
>>
>> Felipe Balbi (5):
>> mmc: host: omap_hsmmc: pass host as an argument
>> mmc: host: omap_hsmmc: add reg_offset field
>> mmc: host: omap_hsmmc: introduce new accessor functions
>> mmc: host: omap_hsmmc: switch over to new accessors
>> mmc: host: omap_hsmmc: set max_blk_size correctly
Got mislead by your reply to this series, about the alternative way of
reading memory size from CAPA register
>
> this has been here for almost a month, any comments ?
>
Do you see any performance impact with this series ?
WARNING: multiple messages have this Message-ID (diff)
From: Balaji T K <balajitk@ti.com>
To: <balbi@ti.com>
Cc: <chris@printf.net>, <ulf.hansson@linaro.org>,
<linux-mmc@vger.kernel.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] mmc: host: omap_hsmmc: a few improvements
Date: Tue, 22 Apr 2014 21:00:12 +0530 [thread overview]
Message-ID: <53568B04.4050703@ti.com> (raw)
In-Reply-To: <20140421173203.GH22794@saruman.home>
On Monday 21 April 2014 11:02 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Mar 26, 2014 at 07:04:45PM -0500, Felipe Balbi wrote:
>> this series lets us access the newer registers introduced
>> back in OMAP4 which give us some valid information about
>> the OMAP HSMMC IP like max block size, support for ADMA,
>> support for Retention.
>>
>> Right now, only setting max_blk_size correctly as supporting
>> ADMA and Retention will take a lot of work.
>>
>> Tested on OMAP5 uEVM.
>>
>> Felipe Balbi (5):
>> mmc: host: omap_hsmmc: pass host as an argument
>> mmc: host: omap_hsmmc: add reg_offset field
>> mmc: host: omap_hsmmc: introduce new accessor functions
>> mmc: host: omap_hsmmc: switch over to new accessors
>> mmc: host: omap_hsmmc: set max_blk_size correctly
Got mislead by your reply to this series, about the alternative way of
reading memory size from CAPA register
>
> this has been here for almost a month, any comments ?
>
Do you see any performance impact with this series ?
next prev parent reply other threads:[~2014-04-22 15:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 0:04 [PATCH 0/5] mmc: host: omap_hsmmc: a few improvements Felipe Balbi
2014-03-27 0:04 ` Felipe Balbi
2014-03-27 0:04 ` [PATCH 1/5] mmc: host: omap_hsmmc: pass host as an argument Felipe Balbi
2014-03-27 0:04 ` Felipe Balbi
2014-03-27 0:04 ` [PATCH 2/5] mmc: host: omap_hsmmc: add reg_offset field Felipe Balbi
2014-03-27 0:04 ` Felipe Balbi
2014-03-27 0:04 ` [PATCH 3/5] mmc: host: omap_hsmmc: introduce new accessor functions Felipe Balbi
2014-03-27 0:04 ` Felipe Balbi
2014-04-24 15:17 ` Balaji T K
2014-04-24 15:17 ` Balaji T K
2014-03-27 0:04 ` [PATCH 4/5] mmc: host: omap_hsmmc: switch over to new accessors Felipe Balbi
2014-03-27 0:04 ` Felipe Balbi
2014-03-27 0:04 ` [PATCH 5/5] mmc: host: omap_hsmmc: set max_blk_size correctly Felipe Balbi
2014-03-27 0:04 ` Felipe Balbi
2014-03-27 0:12 ` Felipe Balbi
2014-03-27 0:12 ` Felipe Balbi
2014-04-21 17:32 ` [PATCH 0/5] mmc: host: omap_hsmmc: a few improvements Felipe Balbi
2014-04-21 17:32 ` Felipe Balbi
2014-04-22 15:30 ` Balaji T K [this message]
2014-04-22 15:30 ` Balaji T K
2014-04-22 15:48 ` Felipe Balbi
2014-04-22 15:48 ` Felipe Balbi
2014-04-23 16:26 ` Felipe Balbi
2014-04-23 16:26 ` Felipe Balbi
2014-04-24 15:21 ` Balaji T K
2014-04-24 15:21 ` Balaji T K
2014-04-24 15:26 ` Felipe Balbi
2014-04-24 15:26 ` Felipe Balbi
2014-04-24 14:31 ` Balaji T K
2014-04-24 14:31 ` Balaji T K
2014-04-24 14:39 ` Felipe Balbi
2014-04-24 14:39 ` Felipe Balbi
2014-04-24 14:43 ` Balaji T K
2014-04-24 14:43 ` Balaji T K
2014-04-24 14:48 ` Felipe Balbi
2014-04-24 14:48 ` Felipe Balbi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53568B04.4050703@ti.com \
--to=balajitk@ti.com \
--cc=balbi@ti.com \
--cc=chris@printf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.