From: Pawel Moll <pawel.moll@arm.com>
To: Dinh Nguyen <dinguyen@altera.com>
Cc: "dinh.linux@gmail.com" <dinh.linux@gmail.com>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Mark Rutland <Mark.Rutland@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ian.campbell@citrix.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: socfpga: dts: Add support for SD/MMC
Date: Fri, 26 Jul 2013 16:00:02 +0100 [thread overview]
Message-ID: <1374850802.3213.87.camel@hornet> (raw)
In-Reply-To: <1374850185.20685.12.camel@linux-builds1>
On Fri, 2013-07-26 at 15:49 +0100, Dinh Nguyen wrote:
> Dinh please...
Uh, accept my apologies. I know exactly how it feels ;-)
> > I've also noticed that Exynos defines almost identical bindings:
> >
> > > samsung,dw-mshc-ciu-div
> > > samsung,dw-mshc-sdr-timing
> > > samsung,dw-mshc-ddr-timing
>
> Yes, I agree.
> >
> > Aren't you both using the same "Synopsis Designware Mobile Storage Host
> > Controller" by any chance? Are you sharing a driver? And if not,
> > why? ;-) If the timings really must be parametrised, would it be
> > possible to come up with a common set of "synopsis" properties, instead
> > of "samsung" and "altr" ones?
>
> We are using the same driver. This is just a platform specifc entries
> for how the IP can be implemented. I also agree that we can come up with
> a shared set of properties for these.
>
> But since the platform-driver part has already been picked into the
> master tree, can I work on a common set after this patch? That way it
> enables SD/MMC to work on SocFPGA for the time being.
Ah, I see. You should have included the binding documentation in the
driver using the bindings, not in the patch adding the required nodes to
DTS files... Than no one would have any comments on this patch ;-)
So yes, if the driver part got merged I will shut up now, providing you
promise to work on "consolidating" the bindings for the next cycle. The
sooner, the better. Does it sound like a deal?
Pawel
next prev parent reply other threads:[~2013-07-26 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 22:04 [PATCH] ARM: socfpga: dts: Add support for SD/MMC dinguyen
2013-07-26 13:49 ` Pawel Moll
2013-07-26 14:49 ` Dinh Nguyen
2013-07-26 15:00 ` Pawel Moll [this message]
2013-07-26 15:27 ` Dinh Nguyen
2013-07-26 17:24 ` Stephen Warren
2013-07-26 19:33 ` Dinh Nguyen
2013-07-26 20:02 ` Stephen Warren
2013-07-26 20:44 ` Dinh Nguyen
2013-07-26 21:13 ` Stephen Warren
2013-07-26 21:22 ` Dinh Nguyen
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=1374850802.3213.87.camel@hornet \
--to=pawel.moll@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@altera.com \
--cc=dinh.linux@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.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