From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 61093C388F9 for ; Mon, 23 Nov 2020 13:42:43 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 6887620658 for ; Mon, 23 Nov 2020 13:42:42 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="WpvOJnMW" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6887620658 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id BB18E167B; Mon, 23 Nov 2020 14:41:50 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz BB18E167B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1606138960; bh=AAyo0uglRvh4OQzIHgp3/Ij8r2J/oLhXU4lpep7LpbA=; h=Date:From:To:Subject:References:In-Reply-To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=WpvOJnMWvPBXPIM7zz43m+B6tVKfmaYcxKqCDPrPQ+VNdOlev6njEHQ//n2xuQhyT S3GX6PxmmFRObYMRrP3SOcpjl5c5rGzpXxIzZDI7oXU2LVtr1vLSy9XbJmitbsCe6m eu21HnaCic+XOhF8Xjp0kiBM0DcXxA6M+ch8hZZc= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 5A725F80269; Mon, 23 Nov 2020 14:41:38 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id B01BFF80255; Mon, 23 Nov 2020 14:41:37 +0100 (CET) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 7990FF80255 for ; Mon, 23 Nov 2020 14:41:28 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 7990FF80255 IronPort-SDR: NmH8sKbdLu/luuhJUZ/DZsgxemQVlbqi4kgKXpKiXBy4UKnuxJfFdPYuN4++i50HxBx0ZYyjnP TE1ARGAPVFJA== X-IronPort-AV: E=McAfee;i="6000,8403,9813"; a="151025449" X-IronPort-AV: E=Sophos;i="5.78,363,1599548400"; d="scan'208";a="151025449" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Nov 2020 05:41:25 -0800 IronPort-SDR: 54UAbvcIFwMBqmRQiln1zfuPud/opx+vgQoVASq3noCQFKIqxM80S+39jFwGrptkf5MMtMXMlA oKnGJDLfAXsA== X-IronPort-AV: E=Sophos;i="5.78,363,1599548400"; d="scan'208";a="432292518" Received: from smile.fi.intel.com (HELO smile) ([10.237.68.40]) by fmsmga001-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Nov 2020 05:41:23 -0800 Received: from andy by smile with local (Exim 4.94) (envelope-from ) id 1khC6r-009ASD-HD; Mon, 23 Nov 2020 15:42:25 +0200 Date: Mon, 23 Nov 2020 15:42:25 +0200 From: Andy Shevchenko To: Krzysztof Kozlowski Subject: Re: [PATCH 01/38] ASoC: ak5558: drop of_match_ptr from of_device_id table Message-ID: <20201123134225.GF4077@smile.fi.intel.com> References: <20201120161653.445521-1-krzk@kernel.org> <20201120165202.GG6751@sirena.org.uk> <20201120194245.GA2925@kozik-lap> <20201120200429.GJ6751@sirena.org.uk> <20201122105813.GA3780@kozik-lap> <20201123104832.GY4077@smile.fi.intel.com> <20201123123731.GA6322@sirena.org.uk> <20201123124129.GA170000@kozik-lap> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201123124129.GA170000@kozik-lap> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org, Shengjiu Wang , "Rafael J. Wysocki" , Liam Girdwood , Mark Brown , Takashi Iwai X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Mon, Nov 23, 2020 at 01:41:29PM +0100, Krzysztof Kozlowski wrote: > On Mon, Nov 23, 2020 at 12:37:31PM +0000, Mark Brown wrote: > > On Mon, Nov 23, 2020 at 12:48:32PM +0200, Andy Shevchenko wrote: > > > On Sun, Nov 22, 2020 at 11:59:20AM +0100, Krzysztof Kozlowski wrote: > > > > On Fri, Nov 20, 2020 at 08:04:29PM +0000, Mark Brown wrote: > > > > > > > Surely if that's the desired outcome the fix is to change the definition > > > > > of of_match_ptr() such that it leaves the reference with CONFIG_ACPI, > > > > > perhaps hidden behind a config option for PRP0001? That seems better > > > > > than going through the entire tree like this. > > > > > > That could be indeed an easier way to achieve this. > > > > > ...easier and wrong in my opinion. Not all drivers need that. > > > What the point to touch it in the driver which is OF-only? > > > (For IP which will quite unlikely to be present in ACPI world) > > > Or if the device will get the correct ACPI ID? > > > > That feels like something that should be done with Kconfig dependencies > > like a direct OF dependency (possibly a !PRP0001 dependency?) for the > > driver or possibly with having a variant of_match_ptr() for things that > > really don't want to support PRP0001. Just removing all the use of > > of_match_ptr() is both noisy and confusing in that it looks like it's > > creating issues to fix, it makes it hard to understand when and why one > > should use the macro. > > For the OF-only drivers (without other ID table), there is no point to > use the macro. Driver can bind only with DT, so what is the point of > of_match_ptr? To skip the OF table when building without OF? Driver > won't be usable at all in such case. So maybe for compile testing? > There is no need to remove OF table for simple build tests. I'm on the same page here. -- With Best Regards, Andy Shevchenko