Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4C5EAC7EE36 for ; Thu, 2 Mar 2023 10:47:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230023AbjCBKrh (ORCPT ); Thu, 2 Mar 2023 05:47:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34118 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229983AbjCBKre (ORCPT ); Thu, 2 Mar 2023 05:47:34 -0500 Received: from sender4-op-o15.zoho.com (sender4-op-o15.zoho.com [136.143.188.15]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9A6E837731; Thu, 2 Mar 2023 02:47:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1677754035; cv=none; d=zohomail.com; s=zohoarc; b=c2ZehWxZUtp/cl4T5HNT9vLkzpL5ZwhAJLPiij4+5DTFylmtKpIj/tkT2gErnjGXFessHP1oP/FEub2sFkX6ELT0iu/R5yHXQYsUAQPOZM3jnpkgd4ELTVJwLDYUBw/kYN8i5OZi1jAT5bKwn061+neWje2ZCZAcfaeRZ3mrcOs= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1677754035; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To; bh=UUcOfchS4C2fgxhPjvGjSCiIN/7y7uTOoaWrQDYPRTM=; b=I54FU9r9Q+ybNILluTJpCNr5r7Y6HsASeCWFBbE4PjnMoVk8u3wwVumSQTBxNQCuD17z+BpQ6d2UUBje+2vLGxyExel+TbYrkDSHdrgc2YUqP0AVTRa5w6haDkghwCODghjto5CRefiUZm+T0tp2KbwNWRSZ/oSM2jxa9A+4C7g= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=arinc9.com; spf=pass smtp.mailfrom=arinc.unal@arinc9.com; dmarc=pass header.from= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1677754035; s=zmail; d=arinc9.com; i=arinc.unal@arinc9.com; h=Message-ID:Date:Date:MIME-Version:Subject:Subject:To:To:Cc:Cc:References:From:From:In-Reply-To:Content-Type:Content-Transfer-Encoding:Message-Id:Reply-To; bh=UUcOfchS4C2fgxhPjvGjSCiIN/7y7uTOoaWrQDYPRTM=; b=A0A3gKeO6HpQ6VZt5x+Be4cJ3ia0MXGxzuevNkr6FkDoh/8oj88j9epiI175TUDM kx2jOgtkNul1YxLnHPtWbDQqlqSOjjBVyb2/oRi9SGbhDuRPBSLsPF6VHERd64cyde7 NIwvdDHiCp/splvG6QbuE2OutO/DPpCer5zXQZ68= Received: from [10.10.10.3] (212.68.60.226 [212.68.60.226]) by mx.zohomail.com with SMTPS id 1677754033173751.0132443007599; Thu, 2 Mar 2023 02:47:13 -0800 (PST) Message-ID: Date: Thu, 2 Mar 2023 13:47:05 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [RFC PATCH 07/16] dt-bindings: pinctrl: ralink: add new compatible strings Content-Language: en-US To: Krzysztof Kozlowski , Rob Herring Cc: Sergio Paracuellos , Linus Walleij , Krzysztof Kozlowski , linux-mediatek@lists.infradead.org, linux-mips@vger.kernel.org, linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Matthias Brugger , Sean Wang , William Dean , Daniel Golle , Daniel Santos , Luiz Angelo Daros de Luca , Frank Wunderlich , Landen Chao , DENG Qingfang , Sean Wang , erkin.bozoglu@xeront.com References: <20230222183932.33267-1-arinc.unal@arinc9.com> <20230222183932.33267-8-arinc.unal@arinc9.com> <20230227173333.GA496999-robh@kernel.org> <20230301024431.GA251215-robh@kernel.org> <11d3c806-04b6-da54-65f1-c0bd154affbc@linaro.org> <1aae7ac9-c83d-71b4-4fce-325f02fcd722@linaro.org> <89588f69-9cf0-e7a4-b976-5ce87d42e296@arinc9.com> <2ccb573d-39f4-cb80-7a3e-63a60c2bc0a8@linaro.org> From: =?UTF-8?B?QXLEsW7DpyDDnE5BTA==?= In-Reply-To: <2ccb573d-39f4-cb80-7a3e-63a60c2bc0a8@linaro.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-ZohoMailClient: External Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2.03.2023 13:29, Krzysztof Kozlowski wrote: > On 02/03/2023 11:22, Arınç ÜNAL wrote: >>>> >>>> ## Incorrect naming >>>> >>>> MT7620, MT7621, MT7628, and MT7688 SoCs are incorrectly called Ralink, >>>> introduce new ralink->mediatek compatible strings to address it. >>> >>> So this part was addressed by Rob - we don't do it, because it does not >>> matter. Ralink is now Mediatek, thus there is no conflict and no issues >>> with different vendor used. >> >> I think Rob was rather addressing that updating compatible strings based >> on acquisition or marketing whims is not permitted. This condition does >> not apply here as these SoCs were never Ralink. >> >> I understand your point that Ralink is now MediaTek but still, calling >> these SoCs Ralink would be a bit misleading, don't you think? > > Misleading yes, but also does not matter. At least matter not enough to > justify ABI break, so you would need to deprecate old ones and keep > everything backwards compatible. You still would affect 3rd party users > of DTS, though... I intend to do just that. Introduce new mediatek strings, keep the old ones so it's backwards compatible, therefore don't break the ABI. Instead of deprecating old strings, I intend to introduce the checks I mentioned, on the schema, so the pin muxing bindings only apply if the DT has got a string that won't match multiple schemas. This way it shouldn't affect 3rd party DTs. Arınç