public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Balaji T K <balajitk@ti.com>
Cc: balbi@ti.com, 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: Thu, 24 Apr 2014 09:48:22 -0500	[thread overview]
Message-ID: <20140424144822.GJ26661@saruman.home> (raw)
In-Reply-To: <53592304.3070105@ti.com>

[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]

On Thu, Apr 24, 2014 at 08:13:16PM +0530, Balaji T K wrote:
> On Thursday 24 April 2014 08:09 PM, Felipe Balbi wrote:
> >On Thu, Apr 24, 2014 at 08:01:19PM +0530, Balaji T K wrote:
> >>On Thursday 27 March 2014 05:34 AM, Felipe Balbi wrote:
> >>>Hi,
> >>>
> >>>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.
> >>
> >>"Support for Retention" looks interesting, can you shed more lights on
> >>it
> >
> >HWINFO has a bit (bit 6) which tells you whether retention is supported,
> >it's in all TRMs since OMAP3630 or so.
> >
> >"6	RERETMODE		Retention mode generic parameter
> >				This bit field indicates whether the
> >				retention mode is supported using the
> >				pin PIRFFRET.
> >
> >				0x0: Retention mode disabled
> >				0x1: Retention mode enabled"
> >
> 
> I have seen that but just wondering how the driver can make use of it
> :-)

oh, perhaps you can use to conditionally save context. The difficulty is
knowing if we're going to RET or OFF, but that could be extrapolated
from pm_qos, perhaps ?!?

just a thought.

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2014-04-24 14:48 UTC|newest]

Thread overview: 18+ 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 ` [PATCH 1/5] mmc: host: omap_hsmmc: pass host as an argument 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 ` [PATCH 3/5] mmc: host: omap_hsmmc: introduce new accessor functions Felipe Balbi
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 ` [PATCH 5/5] mmc: host: omap_hsmmc: set max_blk_size correctly 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-22 15:30   ` Balaji T K
2014-04-22 15:48     ` Felipe Balbi
2014-04-23 16:26       ` Felipe Balbi
2014-04-24 15:21       ` Balaji T K
2014-04-24 15:26         ` Felipe Balbi
2014-04-24 14:31 ` Balaji T K
2014-04-24 14:39   ` Felipe Balbi
2014-04-24 14:43     ` Balaji T K
2014-04-24 14:48       ` Felipe Balbi [this message]

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=20140424144822.GJ26661@saruman.home \
    --to=balbi@ti.com \
    --cc=balajitk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox