Received: by 2002:a05:6358:489b:b0:bb:da1:e618 with SMTP id x27csp6387643rwn; Tue, 13 Sep 2022 03:38:19 -0700 (PDT) X-Google-Smtp-Source: AA6agR6b4Dmyec0wZgBPil7OXkEDvIascjqt9GFtb0gqLlobhOrxEQnyH+pJkIO/glFZKwUmqH54 X-Received: by 2002:a17:907:984:b0:77f:4d95:9e2f with SMTP id bf4-20020a170907098400b0077f4d959e2fmr4093380ejc.176.1663065499613; Tue, 13 Sep 2022 03:38:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663065499; cv=none; d=google.com; s=arc-20160816; b=W003mtogt2c86moYMFgF04oU5HEwiO9y884OTOx+Dbaqc5ZB0TOqrixvqr5XL/usPA v6K+HFfes8csrwtpAbrwh3rLwOU+cccr9kSm+xnDuaIlxgcZZ6bVZFHMvmn4Yzx1MEcC mRSd7QS8XQln22fkjoc38kn901toVDK6bA5h328lNA/nCWPiUEqWbZPUX9nqdN4ivu/p ZFZkz9gJJNASiI7hR1Ti76TRO7MiDzkiy+UC08F5g5DObSHOHSC/9vkChUxLXuuX2FP/ k2RwxwcJRe3ZlCwsgityZsbvFfD4Sk+7p0A9O6j1ikeoni9z1TF7hTCJBhKqC9ZyXAde Sfxg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=9sfFtZZHmFhfrNmLc8l5Nt+nNbY97JKUGxHMFI9MKJs=; b=Mm1VsU4a7IbdM60cHAz5i5+bDBDuRYu3JURskhYWlicu9RbYDAvjAF/pGPRySycB2g yi/QSHfQWIftqROKbQjVnWTPYM8wRGJn/JEIYnGeTCiVIE6CWSZSSrDgdwUXe3QFIL8A 3cCgMF9V3ZexrU3eNw/KT5ntSC0kqkv4FhA0rnVgMKZ47C63TwixQdTaY/8HRurJBM5k n8iwOtcP6X7tkhbeVf+s0As3QVLx5jybKoGTpn4wb0q8Z6Kz/IKWRgs90tAPZphd6OGW T90jy8yD33BFPSbuc4+NIPnONVD+7tzlMay5XsM0OGVxjBnuSI50ECwbxZGtZzlOLO4v eG7Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=sntech.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id js1-20020a17090797c100b0077a0dad5475si11381842ejc.313.2022.09.13.03.37.53; Tue, 13 Sep 2022 03:38:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=sntech.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231575AbiIMKWs (ORCPT + 99 others); Tue, 13 Sep 2022 06:22:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48044 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231626AbiIMKWb (ORCPT ); Tue, 13 Sep 2022 06:22:31 -0400 Received: from gloria.sntech.de (gloria.sntech.de [185.11.138.130]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 538815C9FC; Tue, 13 Sep 2022 03:22:19 -0700 (PDT) Received: from [185.122.133.20] (helo=phil.localnet) by gloria.sntech.de with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1oY33V-00045I-Cl; Tue, 13 Sep 2022 12:22:13 +0200 From: Heiko Stuebner To: Rob Herring , Krzysztof Kozlowski , Tianling Shen , Tianling Shen Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4] arm64: dts: rockchip: add EEPROM node for NanoPi R4S Date: Tue, 13 Sep 2022 12:22:11 +0200 Message-ID: <7426763.EvYhyI6sBW@phil> In-Reply-To: <20220911040628.13774-1-cnsztl@gmail.com> References: <20220911040628.13774-1-cnsztl@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS, T_SCC_BODY_TEXT_LINE,T_SPF_HELO_TEMPERROR autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Am Sonntag, 11. September 2022, 06:06:28 CEST schrieb Tianling Shen: > NanoPi R4S has a EEPROM attached to the 2nd I2C bus (U92), which > stores the MAC address. > > FriendlyElec ship two versions of the R4S [1]: The standard as well > as the enterprise edition with only the enterprise edition including > the EEPROM chip that stores the unique MAC address. This needs to go differently. If the eeprom is only preset on the enterprise-version, you need a separate devicetree for it, that provides the eeprom node. Declaring the eeprom "in error" on a device that doesn't have it, isn't the way to go. Look for example at rockchip/rk3399-nanopi-m4b.dts for reference on how to do it - and also remember to add the new binding for that board. And can also again declare the correct mac-address cell. Heiko > > 1. https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R4S#Differences_Between_R4S_Standard_Version_.26_R4S_Enterprise_Version > > Changes in v4: > - Removed `mac-address` cell as it breaks the standard edition > > Changes in v3: > - Added address-cells and size-cells > > Changes in v2: > - Added the size of EEPROM > - Added `mac-address` cell to pass the MAC address to kernel > - Removed `read-only` property in EEPROM node > > Signed-off-by: Tianling Shen > --- > arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts b/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts > index fe5b52610010..42c99573ab27 100644 > --- a/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts > +++ b/arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts > @@ -68,6 +68,17 @@ &emmc_phy { > status = "disabled"; > }; > > +&i2c2 { > + eeprom@51 { > + compatible = "microchip,24c02", "atmel,24c02"; > + reg = <0x51>; > + pagesize = <16>; > + size = <256>; > + #address-cells = <1>; > + #size-cells = <1>; > + }; > +}; > + > &i2c4 { > status = "disabled"; > }; >