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 C06A5C61DA4 for ; Thu, 16 Feb 2023 08:08:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229696AbjBPII6 (ORCPT ); Thu, 16 Feb 2023 03:08:58 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38618 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229523AbjBPII4 (ORCPT ); Thu, 16 Feb 2023 03:08:56 -0500 Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3E5CB2366B for ; Thu, 16 Feb 2023 00:08:55 -0800 (PST) Received: by mail-ed1-x52a.google.com with SMTP id fi26so1627514edb.7 for ; Thu, 16 Feb 2023 00:08:55 -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=FFWHYzQ47F08kHCRk+CWBqg2wpk6kOfepSZvlMuKJME=; b=WX0oYy9lfCJIEjq74PrXD62FgtWfmHosGgxgT0UvwifnLXr3CW1TkRnoxk/o5qk3wR jU/NNzBineBSw4YQ6E2XenNOHtdolgpARYITqqgwalb1OA6ujxwRmpiYnS3+XYFSuJJ2 OXY55ZyRLd41mTUQwpUS4PE6I5+MugD6zD+jALbWdneUmVB4Rj/MbA+jciXJx42HMzvP xFtknXmuqnwLHp/Wbr1RHpyMpt3HO3kJZnZS21oBkhujmpcBsfmViwscIF654Z2ebVYS 1VESqkMorWS7ui9XysezRNwTgrjH6c+Jk7m8lgBsn9K/I+PwgPEUAm2bHMV9K3Fc0Iqn obAA== 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=FFWHYzQ47F08kHCRk+CWBqg2wpk6kOfepSZvlMuKJME=; b=kM/48gY8XGQ4VJ23QiQuvzbblqwuayMGNY1J8I1TyP+7qgJsuUpBEmUXCNslXF+0yE yTaFp6vvI43rpMNaBmU4nOCGL9zz2uTepW2xrEgO5/OsIksb9mMtaB254bbdawBijlHj nEO4P0h90EmT/zqN2XSIs1G9ROv5B+X426pUeRUwx8olWcWyEdIn2L4g1oZ6AXxHptOW YIYT7S5AN6/ulbyI6BeOomXp9flyWDYwFQx9I1zamWriHCuqylsTcJeBm55v+Zq+4My4 0M1W1lbDoSxw7cFknSp2ubloKjFQoz0pWsWBMmIHdEnSpZUTRyABz85LY0DPWvVkBXjx SubQ== X-Gm-Message-State: AO0yUKUdog7vQ+ecVgIB8JAOnRFxT2zj2eA+qDnN9BvwiA8QFMoFlC08 CukZb8M5257BHHS02kHbLlCQjA== X-Google-Smtp-Source: AK7set8I2bHOqG2L4ep05Jnc+APlOvu9ihdXtivHE3MB/bdMnlmw01tngILrwwV+YpsHBAbsDyW1PQ== X-Received: by 2002:a05:6402:1f04:b0:4ad:66e8:ca9a with SMTP id b4-20020a0564021f0400b004ad66e8ca9amr109314edb.6.1676534933708; Thu, 16 Feb 2023 00:08:53 -0800 (PST) Received: from [192.168.1.109] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id x22-20020a1709064a9600b007bff9fb211fsm470600eju.57.2023.02.16.00.08.52 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 16 Feb 2023 00:08:53 -0800 (PST) Message-ID: <198c084e-66ff-1f3d-33cb-a1339b34336c@linaro.org> Date: Thu, 16 Feb 2023 09:08:51 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [PATCH v4 2/3] dt-bindings: i2c-ast2600: Add support for AST2600 i2C driver Content-Language: en-US To: Dhananjay Phadke , 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: <20230201103359.1742140-1-ryan_chen@aspeedtech.com> <20230201103359.1742140-3-ryan_chen@aspeedtech.com> 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 16/02/2023 05:17, Dhananjay Phadke wrote: > Hi Ryan, > > On 2/14/2023 9:43 PM, Ryan Chen wrote: >> It is not duplicated, as my description in cover " This series add AST2600 i2c new register set driver" >> So, this will be different driver compatible. >> The original compatible is >> - aspeed,ast2400-i2c-bus >> - aspeed,ast2500-i2c-bus >> - aspeed,ast2600-i2c-bus >> So the new register set compatible is "- aspeed,ast2600-i2c", remove "bus". > > Is it possible to keep existing driver drivers/i2c/busses/i2c-aspeed.c > for ast2400/ast2500, while move ast2600 support to new driver > altogether, say i2c-ast2600.c along with new register mode? By default > new driver can support legacy mode with same compatible "aspeed,ast2600- > i2c-bus", additionally driven by dt props, switch to new mode. So this is for the same hardware? Then the bindings are duplicated. Driver is actually duplicated as well - rework the old one, instead of adding this. Best regards, Krzysztof