Message ID | 20230321151642.461618-3-eajames@linux.ibm.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7300:1828:b0:ab:1fc6:e12a with SMTP id l40csp2419816dyk; Tue, 21 Mar 2023 08:49:47 -0700 (PDT) X-Google-Smtp-Source: AK7set9aIZDBA24Wg0UrYUHduXuFRLGiV6zv4LBbwNoxJIGU3L/AjqxsKAS2IoPJU4BHLWY6Wr7j X-Received: by 2002:a17:90b:4b92:b0:23d:3698:8ed3 with SMTP id lr18-20020a17090b4b9200b0023d36988ed3mr236207pjb.22.1679413786875; Tue, 21 Mar 2023 08:49:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1679413786; cv=none; d=google.com; s=arc-20160816; b=SB1sb0pZmdf59Ha9rZYT6G9fMpVBXJtjIdYmC9UddEc6seOTe/BlXXPBYpCCKfkyHB BMYl0z6dghltuJ5lFcCUoeWzahEggRGPk2MZpMIFnsSQUlCF9WNJl3c5rkNNUgaSa8jk 90p6OtqaXSDO6FfknfMORPYzf0Q8BzEqCvYyMjDJNTzOLXVQGBD8e+poQHaNQWNGvfy4 hAGt/gh6ophvnp782dR5CJTDz/R77QLU3GRiOiTbgQwgzrPGrfvRGL4S4GihflbDbiHu YS1ir0NBA/GPafPv7MrwvQE5e2JG3U64ETu6m/eqNX1ullWcRRur69I68DftKqwImPQf ctHg== 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 :dkim-signature; bh=CHCxWc3rbFcp6UZWpf/pCxYlaalqi6G6tNsTY1PMYM4=; b=dGqn2yeZj+7/iTxXST/cmWYWpbZer3yrcMt2AatyNI77s3X0HeO1FI56qCTlw5bQYm moJZlpc4jy027hXuWbgITEiNzG+xNemPAh0lPrYqUPlVMmNiJSSXEoSJHpBeotFGV33i zQQih4OQzN7SQ3i6dO8vsFgovjKVY6e1u2tb920hM3pkIn5Wb3te2McsQC/kYTmL7UFm M2zo5kO0+5Dii17oWwHMjTa7WU3vKqoakISHd9jJXTs/QAqveeJbiyZCu9m8Z4SZEmWM 8BHefkZE1w8jnwG7dPjAJk+IqJiDWuGAyEErSNVuQINmtq6ysTObJpS5v0+S2M8oG9wz CNvA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ibm.com header.s=pp1 header.b=iIaJFDFl; 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=pass (p=REJECT sp=NONE dis=NONE) header.from=ibm.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l8-20020a170903120800b001a05bb54963si14332704plh.176.2023.03.21.08.49.34; Tue, 21 Mar 2023 08:49:46 -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; dkim=pass header.i=@ibm.com header.s=pp1 header.b=iIaJFDFl; 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=pass (p=REJECT sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231625AbjCUPRV (ORCPT <rfc822;ezelljr.billy@gmail.com> + 99 others); Tue, 21 Mar 2023 11:17:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36742 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229934AbjCUPRR (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Tue, 21 Mar 2023 11:17:17 -0400 Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4F60A26CF3; Tue, 21 Mar 2023 08:17:15 -0700 (PDT) Received: from pps.filterd (m0098419.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 32LEh78R024839; Tue, 21 Mar 2023 15:16:56 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibm.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding; s=pp1; bh=CHCxWc3rbFcp6UZWpf/pCxYlaalqi6G6tNsTY1PMYM4=; b=iIaJFDFlcNCRPRB3mGP+5Q6NWvTt/7b4dV4LX4IfMH+yjWT8ykhluGWXXzCzuLiyKTjX HyBLuPib/tI5rNk2oqvgVzp7oM5K00TWeF5N+lTMqlAf2uMRoUfMPsWNEZ1sYZi+Y2/n W1A6YYn485TsjxPSe67iZp8qmOrNQ5RAXhRF0MOAa3K4JjZJfeo/VpzH2kMcJW3h1Q4C rDSGehGyagX+4f6JQ8XIYCt10qWUn/adOsPisTLIcoBj4brIKmi3yfWra/jNiQ8vsNgI UhUxCFkbWDe8TSMDD6lyzJ7bZo2BbBlFWodwvCexsHE1p1oTwg2GtunBYlGL3p2V+LPN rA== Received: from ppma03wdc.us.ibm.com (ba.79.3fa9.ip4.static.sl-reverse.com [169.63.121.186]) by mx0b-001b2d01.pphosted.com (PPS) with ESMTPS id 3pf7qnv3pk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 21 Mar 2023 15:16:56 +0000 Received: from pps.filterd (ppma03wdc.us.ibm.com [127.0.0.1]) by ppma03wdc.us.ibm.com (8.17.1.19/8.17.1.19) with ESMTP id 32LEE4lx030320; Tue, 21 Mar 2023 15:16:55 GMT Received: from smtprelay03.dal12v.mail.ibm.com ([9.208.130.98]) by ppma03wdc.us.ibm.com (PPS) with ESMTPS id 3pd4x6u7gu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 21 Mar 2023 15:16:55 +0000 Received: from smtpav01.wdc07v.mail.ibm.com (smtpav01.wdc07v.mail.ibm.com [10.39.53.228]) by smtprelay03.dal12v.mail.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 32LFGrFJ61800786 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 21 Mar 2023 15:16:54 GMT Received: from smtpav01.wdc07v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id CDFF55805B; Tue, 21 Mar 2023 15:16:53 +0000 (GMT) Received: from smtpav01.wdc07v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 521F958063; Tue, 21 Mar 2023 15:16:52 +0000 (GMT) Received: from slate16.aus.stglabs.ibm.com (unknown [9.160.111.39]) by smtpav01.wdc07v.mail.ibm.com (Postfix) with ESMTP; Tue, 21 Mar 2023 15:16:52 +0000 (GMT) From: Eddie James <eajames@linux.ibm.com> To: linux-kernel@vger.kernel.org Cc: linux-aspeed@lists.ozlabs.org, devicetree@vger.kernel.org, andrew@aj.id.au, joel@jms.id.au, krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org, arnd@arndb.de, gregkh@linuxfoundation.org, Eddie James <eajames@linux.ibm.com> Subject: [PATCH v2 2/4] doc: Add Atmel AT30TSE serial eeprom Date: Tue, 21 Mar 2023 10:16:40 -0500 Message-Id: <20230321151642.461618-3-eajames@linux.ibm.com> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20230321151642.461618-1-eajames@linux.ibm.com> References: <20230321151642.461618-1-eajames@linux.ibm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 X-Proofpoint-GUID: BDGxzua8XQlU3P1guiQT_48bq79xeThX X-Proofpoint-ORIG-GUID: BDGxzua8XQlU3P1guiQT_48bq79xeThX X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.942,Hydra:6.0.573,FMLib:17.11.170.22 definitions=2023-03-21_11,2023-03-21_01,2023-02-09_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 mlxscore=0 malwarescore=0 suspectscore=0 bulkscore=0 lowpriorityscore=0 mlxlogscore=999 priorityscore=1501 clxscore=1015 phishscore=0 impostorscore=0 spamscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2303150002 definitions=main-2303210118 X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1760991733671356083?= X-GMAIL-MSGID: =?utf-8?q?1760992990914442992?= |
Series | eeprom: ee1004: Enable devices on multiple busses | |
Commit Message
Eddie James
March 21, 2023, 3:16 p.m. UTC
The AT30TSE is compatible with the JEDEC EE1004 standard. Document it
as a trivial I2C device.
Signed-off-by: Eddie James <eajames@linux.ibm.com>
---
Documentation/devicetree/bindings/trivial-devices.yaml | 2 ++
1 file changed, 2 insertions(+)
Comments
On 3/21/23 10:19, Krzysztof Kozlowski wrote: > On 21/03/2023 16:16, Eddie James wrote: >> The AT30TSE is compatible with the JEDEC EE1004 standard. Document it >> as a trivial I2C device. >> >> Signed-off-by: Eddie James <eajames@linux.ibm.com> > Use subject prefixes matching the subsystem (which you can get for > example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory > your patch is touching). Oops, sorry, will fix. > >> --- >> Documentation/devicetree/bindings/trivial-devices.yaml | 2 ++ >> 1 file changed, 2 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml b/Documentation/devicetree/bindings/trivial-devices.yaml >> index 6f482a254a1d..43e26c73a95f 100644 >> --- a/Documentation/devicetree/bindings/trivial-devices.yaml >> +++ b/Documentation/devicetree/bindings/trivial-devices.yaml >> @@ -47,6 +47,8 @@ properties: >> - ams,iaq-core >> # i2c serial eeprom (24cxx) >> - at,24c08 >> + # i2c serial eeprom (EE1004 standard) > AT30TSE? > >> + - atmel,at30tse > Microchip does not find anything on AT30TSE. Are you sure this is the > model name? Yes: https://www.microchip.com/content/dam/mchp/documents/OTH/ProductDocuments/DataSheets/Atmel-8868-DTS-AT30TSE004A-Datasheet.pdf Maybe it's actually an 8868? Or should I include the 004A as well? Thanks, Eddie > > > Best regards, > Krzysztof >
On 3/21/23 10:46, Eddie James wrote: > > On 3/21/23 10:19, Krzysztof Kozlowski wrote: >> On 21/03/2023 16:16, Eddie James wrote: >>> The AT30TSE is compatible with the JEDEC EE1004 standard. Document it >>> as a trivial I2C device. >>> >>> Signed-off-by: Eddie James <eajames@linux.ibm.com> >> Use subject prefixes matching the subsystem (which you can get for >> example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory >> your patch is touching). > > > Oops, sorry, will fix. > > >> >>> --- >>> Documentation/devicetree/bindings/trivial-devices.yaml | 2 ++ >>> 1 file changed, 2 insertions(+) >>> >>> diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml >>> b/Documentation/devicetree/bindings/trivial-devices.yaml >>> index 6f482a254a1d..43e26c73a95f 100644 >>> --- a/Documentation/devicetree/bindings/trivial-devices.yaml >>> +++ b/Documentation/devicetree/bindings/trivial-devices.yaml >>> @@ -47,6 +47,8 @@ properties: >>> - ams,iaq-core >>> # i2c serial eeprom (24cxx) >>> - at,24c08 >>> + # i2c serial eeprom (EE1004 standard) >> AT30TSE? >> >>> + - atmel,at30tse >> Microchip does not find anything on AT30TSE. Are you sure this is the >> model name? > > > Yes: > https://www.microchip.com/content/dam/mchp/documents/OTH/ProductDocuments/DataSheets/Atmel-8868-DTS-AT30TSE004A-Datasheet.pdf > > > Maybe it's actually an 8868? Or should I include the 004A as well? I found some other AT30TSE (AT30TSE752A for example) devices that do not appear compatible with the EE1004 standard, so I will include the full model number. > > Thanks, > > Eddie > > >> >> >> Best regards, >> Krzysztof >>
On Tue, Mar 21, 2023 at 10:55:43AM -0500, Eddie James wrote: > > On 3/21/23 10:46, Eddie James wrote: > > > > On 3/21/23 10:19, Krzysztof Kozlowski wrote: > > > On 21/03/2023 16:16, Eddie James wrote: > > > > The AT30TSE is compatible with the JEDEC EE1004 standard. Document it > > > > as a trivial I2C device. > > > > > > > > Signed-off-by: Eddie James <eajames@linux.ibm.com> > > > Use subject prefixes matching the subsystem (which you can get for > > > example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory > > > your patch is touching). > > > > > > Oops, sorry, will fix. > > > > > > > > > > > --- > > > > Documentation/devicetree/bindings/trivial-devices.yaml | 2 ++ > > > > 1 file changed, 2 insertions(+) > > > > > > > > diff --git > > > > a/Documentation/devicetree/bindings/trivial-devices.yaml > > > > b/Documentation/devicetree/bindings/trivial-devices.yaml > > > > index 6f482a254a1d..43e26c73a95f 100644 > > > > --- a/Documentation/devicetree/bindings/trivial-devices.yaml > > > > +++ b/Documentation/devicetree/bindings/trivial-devices.yaml > > > > @@ -47,6 +47,8 @@ properties: > > > > - ams,iaq-core > > > > # i2c serial eeprom (24cxx) > > > > - at,24c08 > > > > + # i2c serial eeprom (EE1004 standard) > > > AT30TSE? > > > > > > > + - atmel,at30tse > > > Microchip does not find anything on AT30TSE. Are you sure this is the > > > model name? > > > > > > Yes: https://www.microchip.com/content/dam/mchp/documents/OTH/ProductDocuments/DataSheets/Atmel-8868-DTS-AT30TSE004A-Datasheet.pdf > > > > > > Maybe it's actually an 8868? Or should I include the 004A as well? > > > I found some other AT30TSE (AT30TSE752A for example) devices that do not > appear compatible with the EE1004 standard, so I will include the full model > number. If this standard is sufficiently complete, then you might want a EE1004 fallback compatible. Complete would mean power supply(ies) and any extra i/o are defined and the exact device model is discoverable. Rob
On 3/27/23 10:18, Rob Herring wrote: > On Tue, Mar 21, 2023 at 10:55:43AM -0500, Eddie James wrote: >> On 3/21/23 10:46, Eddie James wrote: >>> On 3/21/23 10:19, Krzysztof Kozlowski wrote: >>>> On 21/03/2023 16:16, Eddie James wrote: >>>>> The AT30TSE is compatible with the JEDEC EE1004 standard. Document it >>>>> as a trivial I2C device. >>>>> >>>>> Signed-off-by: Eddie James <eajames@linux.ibm.com> >>>> Use subject prefixes matching the subsystem (which you can get for >>>> example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory >>>> your patch is touching). >>> >>> Oops, sorry, will fix. >>> >>> >>>>> --- >>>>> Documentation/devicetree/bindings/trivial-devices.yaml | 2 ++ >>>>> 1 file changed, 2 insertions(+) >>>>> >>>>> diff --git >>>>> a/Documentation/devicetree/bindings/trivial-devices.yaml >>>>> b/Documentation/devicetree/bindings/trivial-devices.yaml >>>>> index 6f482a254a1d..43e26c73a95f 100644 >>>>> --- a/Documentation/devicetree/bindings/trivial-devices.yaml >>>>> +++ b/Documentation/devicetree/bindings/trivial-devices.yaml >>>>> @@ -47,6 +47,8 @@ properties: >>>>> - ams,iaq-core >>>>> # i2c serial eeprom (24cxx) >>>>> - at,24c08 >>>>> + # i2c serial eeprom (EE1004 standard) >>>> AT30TSE? >>>> >>>>> + - atmel,at30tse >>>> Microchip does not find anything on AT30TSE. Are you sure this is the >>>> model name? >>> >>> Yes: https://www.microchip.com/content/dam/mchp/documents/OTH/ProductDocuments/DataSheets/Atmel-8868-DTS-AT30TSE004A-Datasheet.pdf >>> >>> >>> Maybe it's actually an 8868? Or should I include the 004A as well? >> >> I found some other AT30TSE (AT30TSE752A for example) devices that do not >> appear compatible with the EE1004 standard, so I will include the full model >> number. > If this standard is sufficiently complete, then you might want a EE1004 > fallback compatible. Complete would mean power supply(ies) and any extra > i/o are defined and the exact device model is discoverable. I don't think this standard would meet those requirements unfortunately. Thanks for the suggestion! Eddie > > Rob
diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml b/Documentation/devicetree/bindings/trivial-devices.yaml index 6f482a254a1d..43e26c73a95f 100644 --- a/Documentation/devicetree/bindings/trivial-devices.yaml +++ b/Documentation/devicetree/bindings/trivial-devices.yaml @@ -47,6 +47,8 @@ properties: - ams,iaq-core # i2c serial eeprom (24cxx) - at,24c08 + # i2c serial eeprom (EE1004 standard) + - atmel,at30tse # i2c trusted platform module (TPM) - atmel,at97sc3204t # ATSHA204 - i2c h/w symmetric crypto module