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 DF805C64ED8 for ; Fri, 24 Feb 2023 08:25:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229718AbjBXIZQ (ORCPT ); Fri, 24 Feb 2023 03:25:16 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41804 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229516AbjBXIZO (ORCPT ); Fri, 24 Feb 2023 03:25:14 -0500 Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 43D9D1630B for ; Fri, 24 Feb 2023 00:25:12 -0800 (PST) Received: by mail-wr1-x436.google.com with SMTP id r7so12893558wrz.6 for ; Fri, 24 Feb 2023 00:25:12 -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:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=905wi/lKsrlDl7OSJlE8SBp+T9mWktWnoMsLMCtGb68=; b=l8hjhj8qsLGlchpSClCJJjrSLh3uBo30Cp+lBZDUbfAbcpomkIiJUAZ7VT9DVlTxKZ chJ+GDZDzfSV/lx1VRRUw5BClmjJt6uA84+KXYUAniE0EXtMnGWWb2BRcaPG9m6yB2v4 lO2561RKBFtN1O2JbYnAmnKSkbptEfeczt//quzkC9dIBvxHb7DWku+3hJv01J2vXk0r J4OsQ72YkSn//t3z3EHtvVCh0doR42tuZ6IxWMKMLyvAJXBaxW66+5KxStd6TCuug78z 8qm6wochtWKKbI9FWxugMXDxV9osB796CopRHlcUULKguXfpPh0AgidzXf2GnvdNfzik J2lg== 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:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=905wi/lKsrlDl7OSJlE8SBp+T9mWktWnoMsLMCtGb68=; b=DCensrxPXFO+0ng/PKwtCLMCJqawqfGmz/71LvKs4asynE81w+FBo4qEQhhoVSUAGR vlgaNgIR4lrwYDo8irEqfFbodAdSJTOTZ3qyK9ijdTcvE+rXrGG7jZJ9H4W+U2RwiPaO N+D5yJ9arCGow4SKS+L3SlJ11romIDj7Od6ikWzegYCGCqeN8jLTjw600AvjBIr5eSpL hNcV4Pao4wg99tSYK9Gf6YB8IVgQW+Bj0INx/sjL+bpojELGugcLd2gXPR+/vt4cEuDf wBCza4RMdmeoVdqUOxRlBDOfs3LNuLlORGBf4+aBwlE245N44I2cNCF3LEiD4Nla5CD2 eyFQ== X-Gm-Message-State: AO0yUKVuOXhuGHKi+4fBzTO3rRxX264P7o0dgigMxstD+U4jJbI5p/Q1 FzNgmm4L6xFU8Mt1eym73BdRbQ== X-Google-Smtp-Source: AK7set/T508aYOyceeyepwWS6ucFOkGUoXO+rb63rjJECxiAvJu/a2srSXKoC/J6pUbI9l3IC2FfYA== X-Received: by 2002:adf:f0c3:0:b0:2c7:144a:3ac1 with SMTP id x3-20020adff0c3000000b002c7144a3ac1mr3972950wro.14.1677227110808; Fri, 24 Feb 2023 00:25:10 -0800 (PST) Received: from [192.168.1.20] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id k2-20020adff282000000b002c6e8cb612fsm11204861wro.92.2023.02.24.00.25.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 24 Feb 2023 00:25:10 -0800 (PST) Message-ID: <3df61f49-4d0f-5d96-459d-acc33ff0fa3a@linaro.org> Date: Fri, 24 Feb 2023 09:25:08 +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 3/5] ARM: dts: hpe: Add I2C Topology To: "Hawkins, Nick" , "Verdun, Jean-Marie" , "robh+dt@kernel.org" , "krzysztof.kozlowski+dt@linaro.org" , "linux@armlinux.org.uk" , "linux-i2c@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "wsa@kernel.org" References: <20230217155054.99757-1-nick.hawkins@hpe.com> <20230217155054.99757-4-nick.hawkins@hpe.com> <66D4DB5E-46AA-4280-A073-E22262F7FD58@hpe.com> Content-Language: en-US From: Krzysztof Kozlowski In-Reply-To: <66D4DB5E-46AA-4280-A073-E22262F7FD58@hpe.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 23/02/2023 22:02, Hawkins, Nick wrote: >> clock-frequency is a property of the board. If it is fixed in the SoC, >> then make it fixed in the driver and there is no point for this property >> in DT. > > Greetings Krzysztof, > > It can be other values however Hm, are you sure? On the same SoC, same or different I2C controllers will have different frequency, entirely independent of board configuration? Best regards, Krzysztof