Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1437281pxb; Thu, 28 Jan 2021 17:09:08 -0800 (PST) X-Google-Smtp-Source: ABdhPJxpJT9XPGqUQxkkWS17SNcAncqm7AmR/7U+AWyhRM41EOtKPbVlCkGYHVk7O78BzslPP7Te X-Received: by 2002:a05:6402:1701:: with SMTP id y1mr2477556edu.251.1611882547983; Thu, 28 Jan 2021 17:09:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611882547; cv=none; d=google.com; s=arc-20160816; b=HD7aebSQy6L8Y6wfcWSmkq1qtJAaiDUKvEDBaHKIyq5csJ3KYj+XgevSBG0YYMpdTv iiWSZkl2NzowQySd7LstnzLv7KDsjXIDduQoSnhUi4dJeYbvAp67Jr88Y8I2MNy9YTgD iibhewSCVUJlSTmVCpQZOjEXm1ev54rRqjGbdI8tqCd0YgwrWdulkohtCN1K3o1TPAz3 Ej4QjVHcR5zNJGFnynjS0DATxHrO+mvmc67qn4AYX9lG+/3BE6krU7uU4ND44rE5NpE2 P9MQm5EznYMfXNp72J+1kekFyy0unZtbT/WELID7/imILEtTJZFw3b0PfNFkKqanyMCm vVAw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:references :subject:cc:to:mime-version:user-agent:from:date:message-id; bh=8doytFJ8EIklHyJVrVq7SQWJCJn01bTQIW74nGaOKbk=; b=JZQGlcsfw6s5njKaAvNjH42sDRFnaS7OAMn2DSLhWVCd4fdDptt7HU+e8oWv/9oNq9 IEqUUXh3KnBnulNGsjTPcv3uGVaeGLpDWcQogR2GLtfBZDKV+UqNtGgE4S57e4epqM/Z p2mUk989uSU4RI8/wVg88E+flcIZ+yJXwjJPTVt2I3oAv+idT23v//pV0iko0+EfzXXZ yApm53r8xJvMWfHmhEYrltEhXCqXWHVVDBcw1B5/uE9Ure1+LPWfzkO/+H1M44JGiT7U UAG/yOo8tGc4PRhZ61j7CyaIC3YocwbuI9EclY0ygbizJEWjmenROVVUD//2H79ukmB4 h38g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z5si4302666edp.368.2021.01.28.17.08.43; Thu, 28 Jan 2021 17:09:07 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231421AbhA2BFj (ORCPT + 99 others); Thu, 28 Jan 2021 20:05:39 -0500 Received: from szxga04-in.huawei.com ([45.249.212.190]:11216 "EHLO szxga04-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229757AbhA2BDw (ORCPT ); Thu, 28 Jan 2021 20:03:52 -0500 Received: from DGGEMS403-HUB.china.huawei.com (unknown [172.30.72.60]) by szxga04-in.huawei.com (SkyGuard) with ESMTP id 4DRfDR6lLSzlCJB; Fri, 29 Jan 2021 09:01:27 +0800 (CST) Received: from [10.40.166.221] (10.40.166.221) by DGGEMS403-HUB.china.huawei.com (10.3.19.203) with Microsoft SMTP Server id 14.3.498.0; Fri, 29 Jan 2021 09:02:50 +0800 Message-ID: <60135EBA.5040803@hisilicon.com> Date: Fri, 29 Jan 2021 09:02:50 +0800 From: Wei Xu User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Arnd Bergmann CC: Zhen Lei , Philipp Zabel , Rob Herring , linux-arm-kernel , devicetree , linux-kernel , Zhangfei Gao , Chen Feng , Manivannan Sadhasivam Subject: Re: [PATCH v3 2/4] arm64: dts: correct vendor prefix hisi to hisilicon References: <20201208124641.1787-1-thunder.leizhen@huawei.com> <20201208124641.1787-3-thunder.leizhen@huawei.com> <6010B6DE.4060202@hisilicon.com> In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.40.166.221] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Arnd, On 2021/1/28 22:08, Arnd Bergmann wrote: > On Wed, Jan 27, 2021 at 1:42 AM Wei Xu wrote: >> On 2021/1/27 6:23, Arnd Bergmann wrote: >>> On Tue, Dec 8, 2020 at 1:46 PM Zhen Lei wrote: >>>> >>>> The vendor prefix of "Hisilicon Limited" is "hisilicon", it is clearly >>>> stated in "vendor-prefixes.yaml". >>>> >>>> Fixes: 35ca8168133c ("arm64: dts: Add dts files for Hisilicon Hi3660 SoC") >>>> Fixes: dd8c7b78c11b ("arm64: dts: Add devicetree for Hisilicon Hi3670 SoC") >>>> Signed-off-by: Zhen Lei >>>> Cc: Chen Feng >>>> Cc: Manivannan Sadhasivam >>> >>> I see this change in the pull request I got, but I'm a bit worried about the >>> incompatible binding change. Wouldn't the correct path forward be to >>> list both the correct and the incorrect properties, both in the dts file >>> and in the driver that interprets the properties? >> >> Thanks for the comment! >> The reset driver will look for "hisilicon" firstly and fall back to "hisi". >> And the DTS is shipped with the driver together. >> So I think there is no compatible issue here. >> Please let me know if missed anything. Thanks! > > There are three things that can go wrong here, and this is only addressing > one of them: Thanks for the detailed explanation! > > 1. Updating the kernel on a machine with a dtb provided by the firmware > is a problem if the new driver can not handle the old properties. This > is correctly handled by the driver's fallback as soon as both trees > are merged. Agreed and the driver has been merged into the v5.11-rc1. > > 2. Updating the dtb while running an older kernel is now broken since > the driver can no longer read the property. This is less critical, but > it does seem easy enough to work around here by leaving both > properties in place. Yes, it is. But if leaving both in place, the dtbs_check will report following warning again: 'hisi,rst-syscon' does not match any of the regexes That is why leizhen changed the dtb. Do you think it is OK to assume no one will use the new dtb with an older kernel? > > 3. Bisecting through the git history across an incompatible change > means you can run into broken commits. We try hard to avoid that > if we are aware of a problem in advance. In this case it could be > avoided by only merging the incompatible DT change in a following > merge window after the driver change, or (better) by making it > a backward-compatible change the same way as addressing 2. Yes, agreed. And The DT change pull request is sent after the driver has been merged into v5.11-rc1. Really appreciate the detail you went to! Best Regards, Wei > > Arnd > . >