Received: by 2002:a05:6358:45e:b0:b5:b6eb:e1f9 with SMTP id 30csp2234211rwe; Sun, 28 Aug 2022 06:47:43 -0700 (PDT) X-Google-Smtp-Source: AA6agR7h6oxF3FNWR1YacNPkijYABBaCdm/veKtCrGxYc/xa4hG3hCZtCZPHz4WoZf7LZe8CBWcA X-Received: by 2002:a17:906:fd8d:b0:73a:7424:6c0d with SMTP id xa13-20020a170906fd8d00b0073a74246c0dmr10721042ejb.425.1661694462527; Sun, 28 Aug 2022 06:47:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1661694462; cv=none; d=google.com; s=arc-20160816; b=eRuHn0gAP48nKTBon1xrxv1EEgzPbGw1w3IXBMFM/jtP5eGnRNw9fMsqGtwYxMyYRG zrmqFVUd/Y/19xhQkweJrao8xhUuAL7964qLsVT69FEBj2je8ok94ZjCLhTLZY4qOkOG wWdIqJ50TSXJdt4S/6xrFE/qzrqL1ljLa6RNEI8WmboYDHnZRZ9BX+/fRXLlUWx0MkHa SR2ZkOOEoET55yAA7a/HIo6pFp5nLbyx66LsWV3HyDgfdPPlJL13yglZ3CGqoGKH1HR6 6fQUTe8z8FV05z2HvKQMu6Bt927pix1sBwn4GAUDA9LpLbzj4u8U8ntbIdjG1zfzO1yp YU/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=KylSzsCbG5Y50VeFVUq/wxId+S+oA2SdPnkKQYFuGQA=; b=Hfec0/PFrsPBpI7UthJHBSFFfoq5YDi4m7Fmm6p1TlzNximbODY0/bsMOlWqs/UaeD z/RsT9k3X4p1KVqPBM5E49732MAsfLLMoZbCa32xPGHjeQOJHAkrmPg1w8thx6D2KfsM ZYrKuybET7YmKHNvz2Z/kddS6oEw8bSpNeUMrh9d+gZiWSFWOkBHNSC/72WiTAo3GkbA sfIymZqndff0jGvy7oi3MXGjf2hVkVb0xeMnsSBsTBnGIQ30EFIN9SEA9Oaw9tMUd+h2 tuysFLyT1E0l3whaFoo6zgH11XWcIr6ZArgRJVG0S43Re21H1ZddmI9ngcvOCiQjofbb jiCg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@bgdev-pl.20210112.gappssmtp.com header.s=20210112 header.b="P/vZxCKI"; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id sh43-20020a1709076eab00b0073156b6fe0esi5382482ejc.742.2022.08.28.06.47.08; Sun, 28 Aug 2022 06:47:42 -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=@bgdev-pl.20210112.gappssmtp.com header.s=20210112 header.b="P/vZxCKI"; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229489AbiH1Ngn (ORCPT + 99 others); Sun, 28 Aug 2022 09:36:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39674 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229458AbiH1Ngl (ORCPT ); Sun, 28 Aug 2022 09:36:41 -0400 Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C109A27B19 for ; Sun, 28 Aug 2022 06:36:37 -0700 (PDT) Received: by mail-ej1-x632.google.com with SMTP id p16so7872569ejb.9 for ; Sun, 28 Aug 2022 06:36:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bgdev-pl.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=KylSzsCbG5Y50VeFVUq/wxId+S+oA2SdPnkKQYFuGQA=; b=P/vZxCKI8hi+Ou7qQesWiXfrPKXDGXulKznD2F7gAdudAVF0rTWq97o+ZF6o5Fh1AK ldFEp6h+zAwq2ojJSkIiSxsrz04mHlh/gtgpSuYJLhtLILCgyE5c9pb6T+cBdfIOxetU QT7F7mtO5++5RlIH1ee7AULcSrEBR6JoxPqy48Z8Rtnf9C3sx4RUZQ0eSOpunV+SW9rf FvCG4T5cs+MMOVj7G10CRNvMakhveXRvybM1ktbCgPByt+E0yjt9PpX6+95L/VM1vM6I 8Cr9Bpz5HlndC5CfTW1YRWyKYTB9ALzBTQBRSF4jXUppW9NeDf5tXxRZDQRwDWp/AOqw d5ww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=KylSzsCbG5Y50VeFVUq/wxId+S+oA2SdPnkKQYFuGQA=; b=J31sRiw0UoayxYl/gjim8WaXxBmZoRQ9nDnudoeqQCbQkpNmETKDdYjJIOXJaTat9A L+TwI/JR1Y2D9XKY7bMvMi0RuWbQxDmp2F+EZulZrWweS5DoMpRooxEu9PhygWy06lHf RHoiXLy7R59Pkvbg0gLGrhikfLt/eCUjr98tiXOaDZxMK2toLGOkjw44zMkUeQKN/njE p25OTund0DHPev/rzyG3So1s9qJdFiFOEDLFPauTSJMkZfV+ixD/1Swx5fs+wGIFPi50 76s3hwp3WiokhMLaiJWfOR3R2Lh5JSDbO9Gar6n/Z+HGgc/2jVvGEOEajuBz8RroZmU2 f9nQ== X-Gm-Message-State: ACgBeo2OQXScHZqX4tgMeFwtK5KZpQ5S92S4Ov8wIZAkXhhGdF1XbAlZ 0aEJeA0/i1Uql/OcxM1T60GgNpit4V32x3ic2UGNnA== X-Received: by 2002:a17:906:8a4e:b0:730:9fcd:d988 with SMTP id gx14-20020a1709068a4e00b007309fcdd988mr10664664ejc.636.1661693796309; Sun, 28 Aug 2022 06:36:36 -0700 (PDT) MIME-Version: 1.0 References: <20220825104422.14156-1-henning.schild@siemens.com> <34315356-f23e-34ff-98e6-a152b588f201@redhat.com> In-Reply-To: <34315356-f23e-34ff-98e6-a152b588f201@redhat.com> From: Bartosz Golaszewski Date: Sun, 28 Aug 2022 15:36:25 +0200 Message-ID: Subject: Re: [PATCH v6 0/7] add support for another simatic board To: Hans de Goede Cc: Henning Schild , Linus Walleij , Pavel Machek , Mark Gross , Andy Shevchenko , Lee Jones , "open list:GPIO SUBSYSTEM" , Linux Kernel Mailing List , Linux LED Subsystem , platform-driver-x86@vger.kernel.org, Sheng-Yuan Huang , Tasanakorn Phaipool , simon.guinot@sequanux.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE 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 On Thu, Aug 25, 2022 at 4:25 PM Hans de Goede wrote: > > Hi, > > On 8/25/22 12:44, Henning Schild wrote: > > changes since v5: > > - adding patch to convert to pr_fmt > > - adding patch to prefix macros with "f7188x_" > > - rebased p1v4 to be p3v5 and added tag > > > > changes since v4: > > - remove int case from a printk in p1 > > - include tags into commit messages > > > > changes since v3: > > - update Kconfig as well > > - drop chip names from comment in driver header > > - add manufacturer check for Fintek again, Nuvoton not possible > > - drop revision printing for Nuvoton > > - restructure defines again > > - add new model 427G > > > > changes since v2: (p1 only) > > - rename macros that change behavior > > - use chip type not device id in the macros > > - reorder defines a bit > > > > changes since v1: > > - remove unused define > > - fix bug where (base + 2) was used as second data bit > > - add macros for "inverted" and "single data bit" > > > > The first two patches apply some style refactorings before actual > > functional changes are made. > > > > Later, This series enables a SuperIO GPIO driver to support a chip from > > the vendor Nuvoton, the driver is for Fintek devices but those just are > > very similar. And in watchdog and hwmon subsystems these SuperIO drivers > > also share code and are sometimes called a family. > > > > In another step the individual banks receive a label to tell them apart, > > a step which potentially changes an interface to legacy users that might > > rely on all banks having the same label, or an exact label. But since a > > later patch wants to use GPIO_LOOKUP unique labels are needed and i > > decided to assign them for all supported chips. > > > > In a following patch the Simatic GPIO LED driver is extended to provide > > LEDs in case that SuperIO GPIO driver can be loaded. > > > > Last but not least the watchdog module of that same SuperIO gets loaded > > on a best effort basis. > > > > The very last patch enables a second model of that same board type. > > > > Henning Schild (7): > > gpio-f7188x: switch over to using pr_fmt > > gpio-f7188x: add a prefix to macros to keep gpio namespace clean > > gpio-f7188x: Add GPIO support for Nuvoton NCT6116 > > gpio-f7188x: use unique labels for banks/chips > > leds: simatic-ipc-leds-gpio: add new model 227G > > platform/x86: simatic-ipc: enable watchdog for 227G > > platform/x86: simatic-ipc: add new model 427G > > So it looks like all these patches are ready for merging now, > the only thing which is missing is an Ack from Pavel or > one of the other LED people for patch 5/7. > > Pavel can have your ack for merging this through another tree > please? > > So what is the plan for merging this? > > I see 2 options: > > Option a: > 1. Merge the GPIO changes (patches 1-4) through the GPIO tree; and > 2. Merge the leds + pdx86 changes through the pdx86 tree > > Option b: > Merge everything through the pdx86 tree, and I will then provide > an immutable branch + signed tag for other subsystems to pull > (if they want to). > Hey! Sorry for the delay, I've just come back from vacation. I'm fine with option b and to that end: Acked-by: Bartosz Golaszewski