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 B68C7C05027 for ; Mon, 20 Feb 2023 10:35:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230450AbjBTKfj (ORCPT ); Mon, 20 Feb 2023 05:35:39 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55426 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229913AbjBTKff (ORCPT ); Mon, 20 Feb 2023 05:35:35 -0500 Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1773018B22 for ; Mon, 20 Feb 2023 02:35:34 -0800 (PST) Received: by mail-ed1-x529.google.com with SMTP id eq27so7423015edb.5 for ; Mon, 20 Feb 2023 02:35:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=w4HZjaEfXhxPqqJJhqyI7tvXB4DOG6uqP5FwvH6q4eU=; b=Zs+dadc7Co8wjuK9wb8wBh+RJxOdxm2VM1QAdx8dk2R4i5UwJPfksduHDhHv5ItFZ1 aLptINgWArsWRUNJcmTGTY6ithb8Lzh9k+gEqoKz5MnHQ1YokbWVgxffQJNFW2qZeUiz 8RAbkrEgpXdRwSfCDXbn2wDCQ/7QARclpSGTRWV523vDeqr5iPyHVVcKRHuoRJrGnL8W wb/cSzvLYHY7+RNa2S83DpaiZrAhR4GBM41+CY9urz+VwQXifXCz49exQfV9B1UADNeH RKbc76FbmRsGOQI3LsRyRSTAdIime1dOUIu8n6f1Z6HGMU/ww+fbHFrNY81Xly64MYAJ 0r+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=w4HZjaEfXhxPqqJJhqyI7tvXB4DOG6uqP5FwvH6q4eU=; b=iLROQ3W3gueb3wy02GYczBVekLSXqT4VFo5WnOkItVbbe0/FolXXkOwzzDpN++oWlU d3QG3x4AX61aDwUkySQOoiHek3vd1VsGsFAlm1F2WUlUego6P7rryfwfXtjbxMP4B5+l 9Xo6/w5/6vhgGLrKifqVijdo5/wJxiJNgqJJZAU/+r4gvTEgr5w5Yn50MhS56f1grP96 g2RmriIXUTedkOd/hKj63GDcd7VQnGeIBpSgXRh62QWaDWwbA8KWGprSDqOP94LOpikL FEhECRRiDgQ3TPBRPcJ+f4EQUIQGyvsOMW+O4o318wIieaxTVXo0o7Hbgq6s5wwhqLke fpgQ== X-Gm-Message-State: AO0yUKXNYP0RxUu+vt+X5n7AbvmX/7jP6fq4vLbuPV8ANSuW9tmq/jYU 0rQmVmLd6lJQ+1TvGKZ+7ET2Sw== X-Google-Smtp-Source: AK7set9SOK81yO3nimO9NuGkdvcul+tD3RZ2vpuiPwLroUindDRTeJPJ+nruZibhYU2AZJydG+C29w== X-Received: by 2002:a17:906:c407:b0:8af:5154:ff8e with SMTP id u7-20020a170906c40700b008af5154ff8emr8474579ejz.15.1676889332553; Mon, 20 Feb 2023 02:35:32 -0800 (PST) Received: from [192.168.1.109] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id y21-20020a056402359500b004ab33d52d03sm1446406edc.22.2023.02.20.02.35.31 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 20 Feb 2023 02:35:32 -0800 (PST) Message-ID: Date: Mon, 20 Feb 2023 11:35:30 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH v5 0/2] Add ASPEED AST2600 I2Cv2 controller driver Content-Language: en-US To: Ryan Chen , Rob Herring , Krzysztof Kozlowski , Joel Stanley , Andrew Jeffery , Philipp Zabel , "openbmc@lists.ozlabs.org" , "linux-arm-kernel@lists.infradead.org" , "linux-aspeed@lists.ozlabs.org" , "linux-kernel@vger.kernel.org" References: <20230220061745.1973981-1-ryan_chen@aspeedtech.com> <54ef0dee-30dc-3ba9-d2f7-8270204b5505@linaro.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/02/2023 10:56, Ryan Chen wrote: >> >>> And also have separate i2c master and slave register set for control. >> >> Since several of my questions remained unanswered and quite frankly it's >> fruitless... so let me read the commit msg directly - it's the same device, just >> with different register layout. Having new compatible makes sense, but this >> should be part of old binding. >> > Sorry, I am confused, Do you mean I should base on original Documentation/devicetree/bindings/i2c/aspeed,i2c.yaml > Add new compatible? Not add another aspeed,i2cv2.yaml. Yes. New compatible and new syscon phandle (constrained to specific compatibles in allOf:if:then:) to the old binding. Best regards, Krzysztof