From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH/RFC v4] ARM: shmobile: armadillo800eva-reference: add SDHI and MMCIF interfaces
Date: Wed, 25 Sep 2013 09:05:41 +0000 [thread overview]
Message-ID: <2096875.5p7e9JmdtM@avalon> (raw)
In-Reply-To: <Pine.LNX.4.64.1309231651230.11505@axis700.grange>
Hi,
(CC'ing Linus Walleij)
On Wednesday 25 September 2013 14:36:36 Simon Horman wrote:
> On Mon, Sep 23, 2013 at 05:38:47PM +0200, Guennadi Liakhovetski wrote:
> > Add SDHI0, SDHI1 and MMCIF interfaces to armadillo800eva-reference with
> > regulators and pin configurations.
> >
> > Signed-off-by: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
> > ---
> >
> > v4:
> >
> > 1. now that PFC pinctrl is usable with DT, we can use proper regulators
> > and pin configurations on armadillo800eva
> >
> > 2. corrected SDHI compatibility strings
> >
> > 3. RFC because I don't know how to enable choosing between CON14 and CON8.
> > In .c version this is done by reading GPIO 6. To do the same in DT mode
> > we'd probably have to use some run-time DT patching, which isn't possible
> > yet, AFAICS.
>
> I agree with your reasoning there, though perhaps Laurent or Magnus
> have a more enlightened view of things.
I'm tempted to say this should be handled by the boot loader, which should
then patch the DT accordingly. This is probably just a poor attempt not to
solve the problem in Linux though :-)
Linus, do you have an opinion on this ? The board has two connectors (MMC/SD 1
and wifi module) that are not usable concurrently. The user can select which
connector to use through a hardware switch that existing board code reads at
init time to determine which platform devices to register and how to configure
pin muxing. Are you aware of a similar problem on other boards that would have
been solved already ?
> To my way of thinking it would be good to merge this change as is,
> which an appropriate disclaimer about functionality in the changelog
> above the scissors. But I do not feel strongly about this and I
> am happy to wait for fuller functionality.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-09-25 9:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 15:38 [PATCH/RFC v4] ARM: shmobile: armadillo800eva-reference: add SDHI and MMCIF interfaces Guennadi Liakhovetski
2013-09-25 5:36 ` Simon Horman
[not found] ` <20130925053636.GD1916-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2013-09-25 7:03 ` Simon Horman
2013-09-25 9:05 ` Laurent Pinchart [this message]
2013-09-26 7:46 ` Linus Walleij
2013-09-26 8:24 ` Guennadi Liakhovetski
2013-09-26 9:41 ` Magnus Damm
2013-09-26 9:57 ` Guennadi Liakhovetski
2013-09-26 10:17 ` Magnus Damm
2013-09-27 0:55 ` Laurent Pinchart
2013-09-27 14:08 ` Linus Walleij
2013-09-29 6:49 ` Laurent Pinchart
2013-09-29 23:20 ` Linus Walleij
2013-09-30 11:10 ` Laurent Pinchart
2013-10-08 11:19 ` Linus Walleij
2013-10-08 14:32 ` Laurent Pinchart
2013-09-30 13:15 ` Grant Likely
2013-09-30 14:38 ` Laurent Pinchart
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=2096875.5p7e9JmdtM@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.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