From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161195AbeBNRZC (ORCPT ); Wed, 14 Feb 2018 12:25:02 -0500 Received: from muru.com ([72.249.23.125]:57090 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1033363AbeBNRZA (ORCPT ); Wed, 14 Feb 2018 12:25:00 -0500 Date: Wed, 14 Feb 2018 09:24:56 -0800 From: Tony Lindgren To: Ulf Hansson Cc: Kishon Vijay Abraham I , Adrian Hunter , Rob Herring , Mark Rutland , Russell King , "linux-mmc@vger.kernel.org" , devicetree@vger.kernel.org, Linux Kernel Mailing List , linux-omap , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 08/16] mmc: sdhci-omap: Add support to override f_max and iodelay from pdata Message-ID: <20180214172455.GO6364@atomide.com> References: <20180205125029.21570-1-kishon@ti.com> <20180205125029.21570-9-kishon@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.3 (2018-01-21) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Ulf Hansson [180214 09:53]: > On 5 February 2018 at 13:50, Kishon Vijay Abraham I 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