From: csd@broadcom.com (Christian Daudt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 2/3] ARM: mmc: bcm281xx SDHCI driver
Date: Fri, 31 May 2013 17:17:36 -0700 [thread overview]
Message-ID: <51A93DA0.3070909@broadcom.com> (raw)
In-Reply-To: <87d2s7ceh0.fsf@octavius.laptop.org>
Hi Chris,
On 13-05-31 09:15 AM, Chris Ball wrote:
>
> Could you investigate replacing this section of code with a call to
> mmc_of_parse(), please? It should be able to replace your parsing
> and handling of bus-width, cd-gpios, wp-gpios, and non-removable
> (other than the initialization quirks specific to your hardware).
>
> I'd like to avoid every driver having its own DT parsing.
> Thanks,
>
> - Chris.
I looked into it and it can replace just about everything that our own
dt parsing code is doing. The only problem is with cd_gpio. If I call
mmc_of_parse, then it will install its own irq handler for cd gpio, and
our driver needs a different handler. the mmc irq handler can call a
card_event callback, but that is already pointing to sdhci_card_event.
So the only way I can use mmc_of_parse that I can see is by adding a
flag to it to skip cd_gpio parsing which only this driver will then set
to true. Any other ideas ?
Thanks,
csd
next prev parent reply other threads:[~2013-06-01 0:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 20:50 [PATCH V4 1/3] mmc: sdhci: Add size for caller in init+register Christian Daudt
2013-05-29 20:50 ` [PATCH V4 2/3] ARM: mmc: bcm281xx SDHCI driver Christian Daudt
2013-05-31 16:15 ` Chris Ball
2013-06-01 0:17 ` Christian Daudt [this message]
2013-06-01 20:13 ` Arnd Bergmann
2013-06-04 14:19 ` Christian Daudt
2013-05-29 20:50 ` [PATCH V4 3/3] ARM: mmc: bcm281xx SDHCI driver (dt mods) Christian Daudt
2013-05-31 15:41 ` [PATCH V4 1/3] mmc: sdhci: Add size for caller in init+register Christian Daudt
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=51A93DA0.3070909@broadcom.com \
--to=csd@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).