Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1441360pxb; Thu, 4 Mar 2021 11:19:39 -0800 (PST) X-Google-Smtp-Source: ABdhPJxJKMu7ov5S/Nw64qj7bVMW+HCbKjyp0/JD2M9RBUZBUUpJMmXkx4Qvwb8C4VlwkuvrcYLP X-Received: by 2002:a17:906:6487:: with SMTP id e7mr6011781ejm.181.1614885579546; Thu, 04 Mar 2021 11:19:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614885579; cv=none; d=google.com; s=arc-20160816; b=vziNn3DGkG9ojI5E6Ya4HZoCY6w9DHO8Y01E1dZ6GuyZ8SjLmupD7UQUFpeXmQmvRJ ucCPwfxCG+yVytzHavaHtOfZD/DofTsxB/dt3ZdFR1qpCUDYbrazWBbn4EMgX9oXT0V9 F+qeHYVZ5V8cHzyiq4OBJG7Fnqt1TA1BPtIlp7Jhx3pEAEzYRfP5ZhFwmjgEHb/DRwAu vZTcnz9YSs2csa56lHGj+ZVeHBYUVHVp9/XyxQ1okf0/i+pLRxmts67FPU21O8cIT0JH ghz3xLKW2baM8RS0kkE0YNo+XVTRM5rwSlF9q4Xq5stzAh+p+Lg/LdBT1cgd8l3ZN/zZ mQ6A== 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:subject:cc:to:from:date; bh=i5D6QfihbBYdXeS/26pumd44gLE4ceeU0PFreXZNXdI=; b=BYTHZUSONLZ5usfoTRCJnlRDHCplz2mazIFd6e7SamkIJVpwTahA2F7BDRsDedfldR 7HGhC5+cYmZ0PaCqsjUQAytJ+pEg+vVRh6VImfOpxqVd5AQTq83J4ACbxe2lsqQb4ATd ao2pPeWNy2Nn8VInDNyBc6y65UxN9ULznltU2mGb2GjnSQ/E+dJDC2wkduzHY8dSGZfT aJgxFzqZTeA9hRTBLqZID8w48klDaXOkLV7r9g6fdS6Rk50NBY+xWO7fOfI54OLqH1cm 2ZoQKWG8FJQnXpe+99jMedQI4Vh7d/EP3F4wKzIVyIb573kswoXdUp2loMfE81Vej+J0 EKfA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b1si302768edq.5.2021.03.04.11.19.16; Thu, 04 Mar 2021 11:19:39 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232049AbhCDTQD (ORCPT + 99 others); Thu, 4 Mar 2021 14:16:03 -0500 Received: from gecko.sbs.de ([194.138.37.40]:46849 "EHLO gecko.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230472AbhCDTP4 (ORCPT ); Thu, 4 Mar 2021 14:15:56 -0500 Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by gecko.sbs.de (8.15.2/8.15.2) with ESMTPS id 124JEm13026341 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 4 Mar 2021 20:14:48 +0100 Received: from md1za8fc.ad001.siemens.net ([167.87.11.66]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id 124JElDY004306; Thu, 4 Mar 2021 20:14:47 +0100 Date: Thu, 4 Mar 2021 20:14:46 +0100 From: Henning Schild To: Andy Shevchenko Cc: Linux Kernel Mailing List , Linux LED Subsystem , Platform Driver , linux-watchdog@vger.kernel.org, Srikanth Krishnakar , Jan Kiszka , Gerd Haeussler , Guenter Roeck , Wim Van Sebroeck , Mark Gross , Hans de Goede , Pavel Machek Subject: Re: [PATCH 0/4] add device drivers for Siemens Industrial PCs Message-ID: <20210304201446.6989f2a4@md1za8fc.ad001.siemens.net> In-Reply-To: References: <20210302163309.25528-1-henning.schild@siemens.com> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thanks Andy, Am Thu, 4 Mar 2021 12:19:44 +0200 schrieb Andy Shevchenko : > On Thu, Mar 4, 2021 at 9:29 AM Henning Schild > wrote: > > > This series adds support for watchdogs and leds of several x86 > > devices from Siemens. > > > > It is structured with a platform driver that mainly does > > identification of the machines. It might trigger loading of the > > actual device drivers by attaching devices to the platform bus. > > > > The identification is vendor specific, parsing a special binary DMI > > entry. The implementation of that platform identification is > > applied on pmc_atom clock quirks in the final patch. > > > > It is all structured in a way that we can easily add more devices > > and more platform drivers later. Internally we have some more code > > for hardware monitoring, more leds, watchdogs etc. This will follow > > some day. > > > > But the idea here is to share early, and hopefully not fail early. > > I have given a few comments here and there, so please check the entire > series and address them in _all_ similar locations. As I have noticed, > I have different approach about P2SB code, I have to give the series a > dust and see if you can utilize it. You did find some things that others found as well. SPDX vs blabla, header ordering, some other style. Some things are already done and will be in v2. Other findings are new, and we will look into them. The only thing that did stick out is P2SB, also was a point in internal pre-review. Let us see what you have, i can include a patch of yours into the q. But i am kind of afraid once it is there, several existing users should be touched with it, and this series would come later. Or this series comes first and you come later and clean up our "mess". Not sure i would want to take over all P2SB unhiders, but with you on board it will work. > I would like to be Cc'ed on the next version. Sure thing. regards, Henning >