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 60AB2C7EE26 for ; Tue, 23 May 2023 08:48:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235924AbjEWIsq (ORCPT ); Tue, 23 May 2023 04:48:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55912 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235984AbjEWIso (ORCPT ); Tue, 23 May 2023 04:48:44 -0400 Received: from mail-vk1-xa2f.google.com (mail-vk1-xa2f.google.com [IPv6:2607:f8b0:4864:20::a2f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7F844119 for ; Tue, 23 May 2023 01:48:42 -0700 (PDT) Received: by mail-vk1-xa2f.google.com with SMTP id 71dfb90a1353d-456f7ea8694so1548562e0c.0 for ; Tue, 23 May 2023 01:48:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bgdev-pl.20221208.gappssmtp.com; s=20221208; t=1684831721; x=1687423721; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=nsCD0of1x6zAZe4E8ewHElcvWX4G+68HMU5ECsDupIE=; b=1MkyHwpRBLggLehbgS6eNfVckrrq+fSGe5Ml3QKm23i2ADWDBXeDmBN5mQpLixA1L7 /STGoEzvvRpB9YR2lAH38LNK5EPoPYKR0USAiTHsMkH6PTlH/4pBmYOjfPYy2J/Y2FcC W0SzIJp0LCOnczI45DnIN/FEU25qCLA55krEq3uZR/TWW0lkWemQI6q2sZ56sLldQeO4 d/eXHJjaLnm4UoLa2As4aYZOgyoAXDh3WFoT3NduC98nzH9ryrxihWhELLMp37MvEnu9 wTZIKhJ5nO1lXo+qss4xvuc4vmH3GlFD9n7BGgxhyQbeV/BjRa2SUxLokggVFcHHaH+a DmOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684831721; x=1687423721; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=nsCD0of1x6zAZe4E8ewHElcvWX4G+68HMU5ECsDupIE=; b=CG/tgYV75QwwHqUju54G7eRB56mKa+dwBFPgNmQ1xuZG3g2XpkhTDvlJMgMM+HkiRo 432IPWH5qXInio0m2B2iqJVPRKtdDljditPpLpGSyPXYkFyiI6LDr3kJlokg44Qp/vLs JdtxWraBMRqQyB+xuFABvBnanrAs7eZY+TcrR47jWJsIjdmHR0DeRJ7Nw6ZSZ7yeHQ+9 wkFJMG0kYu0HMcXzNQCYsSCkCJ2EZB/lwuv8Wy1ja1aFoX0FdFn+3ayLDHhzaiI9PjJE IYczrd14uOYN/jXTbSO1+mB8TmzR2iumo+E2WNVEmQdm0W1UprPRGa9WNHf5R5giJPFT poOg== X-Gm-Message-State: AC+VfDyNQVxRcbKHNFlH4BUdeObdZfcdWGexhi7a3f79Enw2I7uEXHT/ I4EPPiUgwAfghj5IUqnIFe46aqQ1P+h2d+g9UlnUlwic1+J4uGal X-Google-Smtp-Source: ACHHUZ4g3A8Ho/5ndNryXQpmLu1vYMnDo3U7OPTUNTtRkDJDs/TtPHk0tvFU6g2UWK2DN5PGxRYri4rRpoeNl2oXti8= X-Received: by 2002:a1f:4113:0:b0:44f:d1f5:6bec with SMTP id o19-20020a1f4113000000b0044fd1f56becmr4252400vka.4.1684831721544; Tue, 23 May 2023 01:48:41 -0700 (PDT) MIME-Version: 1.0 References: <20230427152055.18380-1-henning.schild@siemens.com> <20230427152055.18380-2-henning.schild@siemens.com> <759b2df004e2445e850a01b33e748972@siemens.com> <20230428113332.3a7b9a18@md1za8fc.ad001.siemens.net> <20230513115326.0a9f669e@md1za8fc.ad001.siemens.net> In-Reply-To: <20230513115326.0a9f669e@md1za8fc.ad001.siemens.net> From: Bartosz Golaszewski Date: Tue, 23 May 2023 10:48:30 +0200 Message-ID: Subject: Re: [PATCH v2 1/1] gpio-f7188x: fix chip name and pin count on Nuvoton chip To: Henning Schild Cc: "Wu, Xing Tong (DI FA CTR IPC CN PRC4)" , Simon Guinot , Linus Walleij , "linux-gpio@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Hans de Goede , Andy Shevchenko Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Sat, May 13, 2023 at 11:53=E2=80=AFAM Henning Schild wrote: > > Am Thu, 11 May 2023 14:52:17 +0200 > schrieb Bartosz Golaszewski : > > > On Fri, Apr 28, 2023 at 11:33=E2=80=AFAM Henning Schild > > wrote: > > > > > > Am Fri, 28 Apr 2023 10:26:18 +0200 > > > schrieb "Wu, Xing Tong (DI FA CTR IPC CN PRC4)" > > > : > > > > > > > Hi all > > > > > > > > The chip id of NCT6116D is 0XD281, you can refer to > > > > NCT6116D_Datasheet_V1_0.pdf, Page 291 > > > > > > Thanks Xing Tong. I think we have come to agree that for now > > > NCT6116D 0xD281 will not be supported in the kernel. Maybe until > > > someone has access to that very chip and a use-case. > > > > > > But you managed to somehow get these datasheets, which are still not > > > publicly available. Maybe you can use your contacts at Nuvoton to > > > kindly ask them to publish those specs on their website for future > > > reference. Some specs are there, but not all. That would help > > > people to add more chips and avoid mistakes like they happened to > > > me. > > > > > > Henning > > > > > > > Henning, do you plan to respin this with the ID corrected? > > Bart, no this one fixes the name of the chip i have at hand, and fixes > the size of its last bank. So it is valid on its own and should IMHO be > merged as is. > > Since i do not have a NCT6116D (0xD281) i could basically just guess > (not too hard) but not test. And i do not really feel like contributing > untested code for which there is no known user/tester. > > Henning > > > Bart > Fair enough, applied. Bart