From: kishore kadiyala <kishorek.kadiyala@gmail.com>
To: linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org
Cc: adrian.hunter@nokia.com, Madhusudhan <madhu.cr@ti.com>,
jarkko.lavinen@nokia.com
Subject: Re: [RFC] OMAP4-hsmmc: card-detect/regulator changes
Date: Wed, 31 Mar 2010 17:59:36 +0530 [thread overview]
Message-ID: <s2z7f9d1ffb1003310529j6ead4a39wc9acbe7f71ae5f54@mail.gmail.com> (raw)
In-Reply-To: <h2p7f9d1ffb1003310451t85fbbb6eo3e3d06617a5a8f00@mail.gmail.com>
Small correction below
On Wed, Mar 31, 2010 at 5:21 PM, kishore kadiyala
<kishorek.kadiyala@gmail.com> wrote:
> Hi,
> I am trying to implement card-detect and regulator changes for HSMMC
> driver on OMAP4.
>
> In OMAP4, hsmmc doesn't use any gpio line for card detect and instead
> uses interrupt line
> from TWL6030 which also provides a register for
> status[Inserted/removed] of the removable Card.
>
> Currently all the gpio related stuff moved from board file "hsmmc.c"
> to driver file "omap_hsmmc.c"
> [http://marc.info/?l=linux-mmc&m=126369200005981&w=2]and since the
> card-detect implementation
> for twl6030 uses I2c read/write it doesn't make sense to have the
card-detect implementation in driver file.
Does it make sense to have the gpio and non-gpio related stuff for
card detect
in board file?
Any suggestions appreciated.
>
> And the regulator changes can remain in driver file.
>
> Regards,
> Kishore
>
prev parent reply other threads:[~2010-03-31 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 11:51 [RFC] OMAP4-hsmmc: card-detect/regulator changes kishore kadiyala
2010-03-31 12:29 ` kishore kadiyala [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=s2z7f9d1ffb1003310529j6ead4a39wc9acbe7f71ae5f54@mail.gmail.com \
--to=kishorek.kadiyala@gmail.com \
--cc=adrian.hunter@nokia.com \
--cc=jarkko.lavinen@nokia.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).