From mboxrd@z Thu Jan 1 00:00:00 1970 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 52412C61DA4 for ; Thu, 9 Mar 2023 08:52:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230296AbjCIIwJ (ORCPT ); Thu, 9 Mar 2023 03:52:09 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50986 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230380AbjCIIwE (ORCPT ); Thu, 9 Mar 2023 03:52:04 -0500 Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D4069DF26A for ; Thu, 9 Mar 2023 00:51:42 -0800 (PST) Received: by mail-ed1-x52e.google.com with SMTP id i34so4007220eda.7 for ; Thu, 09 Mar 2023 00:51:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1678351901; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=rmFJIRnf7lhyyhe5HRvTIuznCSOkKRhfqAX4FxLgYRA=; b=H3Tihc36/HIhfTDJZ3dYkddDKuaeSLksPAwq/9dhmsndrEQs+ViDL3vRtWs1caWfTG PqErMfFzfAzUYvmx/R0UG5Xn4IjPuoIXs3VEOuWP9MbWdLEkjADF94GiK3DRWQZaCu3D Lu0sINGzMapoXRdCO5cFOP0Drf2O/fs7P1y8LKNl2+TDxULwPq5Sj0IkwM11njHbUNPo ES4lcicuDAqfhv2n/6sc9qISxcvvvo3wltjP3QgLIA61MpJtIrKu/TCGgVboU9K/pnKN 04x+y81RewnWJg4qm8PpahDCqf0ZcdRi4kis+TNYYEGVpguzg/dgwFt7Lo3Sv4i851bL FGzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678351901; h=content-transfer-encoding:in-reply-to:from:references:cc: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=rmFJIRnf7lhyyhe5HRvTIuznCSOkKRhfqAX4FxLgYRA=; b=Gb8wN3QMjpPw15XR8IY0bimn8k4aebjPvGXHx2iCd6g0+dKqMqlXAagdQBgZEURfJo ZNFfLcFHYlItpFvaAfiM8vC1N6gjSRODRtVQOvcURFFcuS9VimFM/qEvV99VASrhsogK bzOVBjhu+nll4t52DSxqDFD73mVI+Zzo1UJV28+wPc4VerRmMrElamjWElCnj5isScu0 NMVni8ilZuWcGNeSCc92I0WIJJplTh4L1UrlMJGr3wawsJUuV2I61vD/iE7Wg2OsLQdN uRg5wWKzyG9ZpKz4nlMmjrQi1bhoR93QRgYUcsZ+ztF8BZBJWc4AupJy2b1sQzoY8mG9 Oyvw== X-Gm-Message-State: AO0yUKU4TB+n5cimyYUfX4OuiPd1Mi4paqMLnXOYZ6kZ+q43BXc4cCzN zIMOru4Om35Wu+aScRJHo9WUZw== X-Google-Smtp-Source: AK7set8P4LuLBe8BuDzP+8njsAdPqwic2GGX9ilJLhejchDRC2j40nO4EAjmm9ae6ixFJz/7FI/hKw== X-Received: by 2002:a17:906:551:b0:8b1:7f87:8174 with SMTP id k17-20020a170906055100b008b17f878174mr20050787eja.65.1678351901284; Thu, 09 Mar 2023 00:51:41 -0800 (PST) Received: from ?IPV6:2a02:810d:15c0:828:7ee2:e73e:802e:45c1? ([2a02:810d:15c0:828:7ee2:e73e:802e:45c1]) by smtp.gmail.com with ESMTPSA id e2-20020a170906504200b008f767c69421sm8573953ejk.44.2023.03.09.00.51.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 09 Mar 2023 00:51:40 -0800 (PST) Message-ID: Date: Thu, 9 Mar 2023 09:51:39 +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 v6 1/2] dt-bindings: i2c: aspeed: support for AST2600-i2cv2 Content-Language: en-US To: Ryan Chen , Wolfram Sang Cc: Joel Stanley , Brendan Higgins , Krzysztof Kozlowski , Andrew Jeffery , "devicetree@vger.kernel.org" , Philipp Zabel , Rob Herring , Benjamin Herrenschmidt , "linux-aspeed@lists.ozlabs.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "openbmc@lists.ozlabs.org" , "linux-i2c@vger.kernel.org" References: <20230226031321.3126756-1-ryan_chen@aspeedtech.com> <53090449-58c9-bc03-56df-aa8ae93c0c26@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: devicetree@vger.kernel.org On 07/03/2023 11:09, Ryan Chen wrote: >>>> 2. Why we do not have it for all controllers with SMBus v3? Why this >>>> one is special? >>> >>> Not all bus is connected with smbus. Most are i2c device connected in board. >>> That will be specific statement for each bus. >> >> That's not the answer to my question. Why other controllers which can be >> connected to I2C or SMBus devices do not need this property? > > For example following is the board specific connection. > > Board A Board B > ------------------------- ------------------------ > |i2c bus#1(master/slave) <===fingerprint ===> i2c bus#x (master/slave)| > |i2c bus#2(master)-> tmp i2c device | | | > |i2c bus#3(master)-> adc i2c device | | | > ------------------------- ------------------------ > > Bus#1 is mctp transfer for each BoardA/B. (Not smbus connected) > Bus#2 is i2c device connected. > Bus#3 is i2c device connected. You are repeating the same stuff for my question. Where do you see on this diagram here other I2C controller? How does it answer my question? You keep repeating same and same, so it won't work. Best regards, Krzysztof