From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH 3/4] ARM: dts: omap3: bulk convert compatible to be explicitly ti,omap3430 or ti,omap3630 or ti,am3517 Date: Sat, 7 Sep 2019 10:09:02 -0700 Message-ID: <20190907170902.GJ52127@atomide.com> References: <2c9eb085606de4a52d73a2461b1997265cdd2ea5.1567839375.git.hns@goldelico.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <2c9eb085606de4a52d73a2461b1997265cdd2ea5.1567839375.git.hns@goldelico.com> Sender: linux-kernel-owner@vger.kernel.org To: "H. Nikolaus Schaller" Cc: =?utf-8?Q?Beno=C3=AEt?= Cousson , Rob Herring , Adam Ford , =?utf-8?B?QW5kcsOp?= Roth , Mark Rutland , "Rafael J. Wysocki" , Viresh Kumar , Enric Balletbo i Serra , Javier Martinez Canillas , Roger Quadros , Teresa Remmet , linux-omap@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, letux-kernel@openphoenux.org, kernel@pyra-handheld.com, linux-arm-kernel@lists.infradead.org List-Id: devicetree@vger.kernel.org * H. Nikolaus Schaller [190907 06:57]: > For the ti-cpufreq driver we need a clear separation between omap34 and omap36 families > since they have different silicon revisions and efuses. > > So far ti,omap3630/ti,omap36xx is just an additional flag to ti,omap3 while omap34 has no > required entry. > > Therefore we can not match omap34 boards properly. > > This needs to add ti,omap3430 and ti,omap3630 where it is missing. > > We also clean up some instances of missing ti,am3517 so that we can rely on > seeing either one of: > > ti,am3517 > ti,omap3430 > ti,omap3630 > > in addition to ti,omap3. > > We leave ti,omap34xx and ti,omap36xx untouched for compatibility. Thanks for doing this: Acked-by: Tony Lindgren