[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180214172455.GO6364@atomide.com>
Date: Wed, 14 Feb 2018 09:24:56 -0800
From: Tony Lindgren <tony@...mide.com>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: Kishon Vijay Abraham I <kishon@...com>,
Adrian Hunter <adrian.hunter@...el.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Russell King <linux@...linux.org.uk>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
devicetree@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-omap <linux-omap@...r.kernel.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 08/16] mmc: sdhci-omap: Add support to override f_max
and iodelay from pdata
* Ulf Hansson <ulf.hansson@...aro.org> [180214 09:53]:
> On 5 February 2018 at 13:50, Kishon Vijay Abraham I <kishon@...com> wrote:
> > DRA74x EVM Rev H EVM comes with revision 2.0 silicon. However, earlier
> > versions of EVM can come with either revision 1.1 or revision 1.0 of
> > silicon.
> >
> > The device-tree file is written to support rev 2.0 of silicon.
> > pdata-quirks are used to then override the settings needed for
> > PG 1.1 silicon.
> >
> > PG 1.1 silicon has limitations w.r.t frequencies at which MMC1/2/3
> > can operate as well as different IOdelay numbers.
>
> I fail to understand the need for platform data. Why can't DT be used
> for the older revisions as well?
Maybe the silicon revision is not available via soc_device_match()?
Regards,
Tony
Powered by blists - more mailing lists