From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752564AbdLFQTm (ORCPT ); Wed, 6 Dec 2017 11:19:42 -0500 Received: from lelnx193.ext.ti.com ([198.47.27.77]:13457 "EHLO lelnx193.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752213AbdLFQTj (ORCPT ); Wed, 6 Dec 2017 11:19:39 -0500 Subject: Re: [PATCH v2 09/19] ASoC: tlv320aic31xx: Remove platform data To: Mark Brown CC: Liam Girdwood , Rob Herring , Mark Rutland , =?UTF-8?Q?Beno=c3=aet_Cousson?= , Tony Lindgren , , , References: <20171129213300.20021-1-afd@ti.com> <20171129213300.20021-10-afd@ti.com> <20171201132606.vyw7wthmql5trkwq@sirena.org.uk> <4fee76ef-e518-69b6-3bcc-f65b0a31cacc@ti.com> <20171206124540.GC1827@finisterre> From: "Andrew F. Davis" Message-ID: <10f1b19b-4a0a-e336-b757-933d46b5c8e9@ti.com> Date: Wed, 6 Dec 2017 10:19:28 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171206124540.GC1827@finisterre> Content-Type: text/plain; charset="windows-1252" Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/06/2017 06:45 AM, Mark Brown wrote: > On Tue, Dec 05, 2017 at 03:20:19PM -0600, Andrew F. Davis wrote: >> On 12/01/2017 07:26 AM, Mark Brown wrote: > >>> The advantage being...? Not all architectures use DT or ACPI so it's >>> not clear that this is a step forwards in itself. > >> Simplifies the code in several places, and you don't need to use DT or >> ACPI, it probes just fine anyway you normally add an I2C device. > >> All we are dropping here is the platform_data way of specifying mic-bias >> voltage, which if you are wanting to do that in an out-of-tree board >> file, then I'm sure you can locally modify this driver to use your >> wanted voltage setting by default. > > Then if you want to upstream the driver you'll have to add the platform > data support again. Like I say not all architectures have anything > other than board files. > Then they can try, but they will rightfully get nack'd and told to stop using board files and use DT/ACPI. Most upstream architectures don't use board files anymore anyway, so I doubt this will ever happen. Besides, if they haven't upstreamed their code then it is their problem if this patch breaks them, we shouldn't hold up upstream work for out-of-tree code, especially theoretical out-of-tree code that will never exist.