Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp2975144pxu; Mon, 14 Dec 2020 16:36:07 -0800 (PST) X-Google-Smtp-Source: ABdhPJyPAduB4IStM8bzjqqA2DniLqNIWCTedXnej5eTSF15/aClK9qWTtprj+Qrh//LIJVflTaB X-Received: by 2002:a05:6402:3074:: with SMTP id bs20mr27251593edb.365.1607992567468; Mon, 14 Dec 2020 16:36:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607992567; cv=none; d=google.com; s=arc-20160816; b=JurcRiP5EUFzXt3rasCcsmdFEQKPqX3ynB4E1rwwYOC2xrgVrbRv0n+TuVOAJgFEe6 9MKdVC8xE8O00I2YdpN8Yy3D09VLruv/YnNuClXP9s3Rdp4pgnrFeO4YWZhPC6DOv4jv 17qwIbSn//az0J3GanbdZ+sKXpftjYFTd39LE40OZbaQ9t5wBSXtImtwZde8aM1LYit2 chrkhbsru6kL6kYETGSLkitcByDmrQ8L08Qojdkec8mC3X0yfAAcLxiREQtqCk//t2UD qaymrn7MVSm/zPqf58i2c3O8IXo292Su5U62xIgF7mnk+CsE8hdLWpT/ijxYfy+5eeX6 UeNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:subject:cc:to:from:date:references:in-reply-to :message-id:mime-version:user-agent:dkim-signature:dkim-signature; bh=dllxipO8JT/5qcBD2+BfCaHxR11sVzkJmb++D51EVso=; b=sQSvvBg3tGTkzZHRn6HXqKqtMTup/ERgmpz/w7aK0TiuixKjHSb4RgOrYztcrjCBoO UdG87LLPvmf3cytVn8zaGBOrFKmncxFPbCoeoEoQ1ZJrDW0Qzj6xSmgPE1iCYnq8xBrb lf25JsPkFYTdHGKev6DBvX38zJaHIyQXiRqt9SVvi/YISsKpEeBxVsDgnHWlbf/2GBx0 OQjXPxeBc1SoOSoBa/sNgRruxB5y+YrxJY3MfAU8OZk+L8Ldy8wiqh/xzZz50IHoISPk Dqj39iBRLAu+qpPq49ydFuFyVQH/EzvsVEzsjtkKVAbUwvcrswiqTvKbGm9ix9Yaj6Sb PNzA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@aj.id.au header.s=fm1 header.b=ewcTi76y; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=civb3tWt; 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 a14si14287eds.103.2020.12.14.16.35.44; Mon, 14 Dec 2020 16:36: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; dkim=pass header.i=@aj.id.au header.s=fm1 header.b=ewcTi76y; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=civb3tWt; 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 S1729124AbgLOANc (ORCPT + 99 others); Mon, 14 Dec 2020 19:13:32 -0500 Received: from new1-smtp.messagingengine.com ([66.111.4.221]:33169 "EHLO new1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727393AbgLOANb (ORCPT ); Mon, 14 Dec 2020 19:13:31 -0500 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id 7131F5801AF; Mon, 14 Dec 2020 19:12:24 -0500 (EST) Received: from imap2 ([10.202.2.52]) by compute3.internal (MEProxy); Mon, 14 Dec 2020 19:12:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aj.id.au; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type; s=fm1; bh=dllxipO8JT/5qcBD2+BfCaHxR11sVzk Jmb++D51EVso=; b=ewcTi76yr6ufVEf4Ui1plZqNsQbXiKjNqfw4fez/Oa5YN69 WtH9wxbpHdswK24M2QyXtAHt0UtbYVGHomcel9r1oZtEQa9ZDJLgf+uZYdGtASjC Ia7wdzCur6+F3zWpJQHlEuOaP6oJA6dASZR48CL/aZtY1AOwohDBkPHHhnI4JfmQ dc/bhZaAoYrkGZ5tJ0YUrURweXivm7+/xAd1nwYkpFOknXClJ4YwqA8HeCyWIe6S mFW84IQmQLt395E4qoHVIQZ9Pl3CUnof6DYcjBUI8bHUH7I/6R6Spt6Y7ALFy6iX Qco9z2VRlJQse+Xq5+t9uVXr8m0CmOQpCUxUn7A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=dllxip O8JT/5qcBD2+BfCaHxR11sVzkJmb++D51EVso=; b=civb3tWtoCoCXcgxgHpr76 QO3YQHdQqdhQsajmuqMzNrKJE3BJuPgOs2g/5KgtMy0gYvNdZvRCvNQtmtpvegq3 AE3kE1pHskTxXiQqo7C7SRATC1MqXQ0t1WHX1/y285yvtElfqZvVRnJpgcg/JdjP Llwdjg37/3gZuf6rqPvP9slN+d+D88tZ/ieJLcyL4Gj2+qkd16XALX76Ic6KeNR5 7IGmo/qvfVcAI5YXthK+NUgqTG6+uZmJ8gRBe/eMfTcCfB96tgEGE65HI+69/DAt WDFZ88HlDn72cwJmtLJ4HHpBRvfBBtY2eo3949kdUg1kVhqzgvelrnYY92eC6n8g == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudekledgvddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdetnhgu rhgvficulfgvfhhfvghrhidfuceorghnughrvgifsegrjhdrihgurdgruheqnecuggftrf grthhtvghrnhephefhfeekgfekudevheffheeihedujeefjeevjeefudfgfeeutdeuvdeh hfevueffnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh eprghnughrvgifsegrjhdrihgurdgruh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 2A6C0E010E; Mon, 14 Dec 2020 19:12:20 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.3.1-61-gb52c239-fm-20201210.001-gb52c2396 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <20201005082806.28899-1-chiawei_wang@aspeedtech.com> <20201005082806.28899-6-chiawei_wang@aspeedtech.com> <2e2d3a02-6677-4b0e-b538-d3130a3b20d1@www.fastmail.com> Date: Tue, 15 Dec 2020 10:42:01 +1030 From: "Andrew Jeffery" To: "Chia-Wei, Wang" , "Rob Herring" , "Joel Stanley" Cc: "Ryan Chen" , "Lee Jones" , "Corey Minyard" , "Arnd Bergmann" , "Greg Kroah-Hartman" , "Linus Walleij" , "Haiyue Wang" , "linux-arm-kernel@lists.infradead.org" , "linux-aspeed@lists.ozlabs.org" , "linux-kernel@vger.kernel.org" , "openbmc@lists.ozlabs.org" , "linux-gpio@vger.kernel.org" Subject: Re: [PATCH v2 5/5] dt-bindings: aspeed-lpc: Remove LPC partitioning Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Chiawei, On Mon, 14 Dec 2020, at 13:14, ChiaWei Wang wrote: > Hi Andrew & Rob, > > Do you have any suggestion on this patch? Rob hasn't responded, but I think it will be easier to get an Ack out of him if we do a v2 of the binding so we're not breaking backwards-compatibility with the current definition. Concretely: - compatible: One of: "aspeed,ast2400-lpc", "simple-mfd" "aspeed,ast2500-lpc", "simple-mfd" Becomes something like: - compatible: One of: "aspeed,ast2400-lpc-v2", "simple-mfd" "aspeed,ast2500-lpc-v2", "simple-mfd" We can convert the in-tree devicetrees, immediately drop support for the current binding in the drivers, and _only_ support v2 of the binding going forward. That way your patches stay largely the same, the binding isn't hamstrung as it is currently, and we're not trying to maintain code to support the current binding definition - but we're also not pretending that old devicetrees will work with newer kernels that only support the new binding definition (which is the problem with your current patch series). How does that sound? As to how to implement this, I think we'll need to add some of_device_is_compatible() checks in the relevant drivers to make sure that they're using the new LPC binding, such as in drivers/pinctrl/aspeed/pinctrl-aspeed-g5.c before we fetch the regmap on line 2657. Sorry that this is dragging out a bit (and for the mess I made). Cheers, Andrew