Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp1881687pxb; Mon, 12 Apr 2021 08:48:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyjLKyHZVxkQ0wfxRsO03pdYvdGwDFI290tnIPhIsAQEjFa9ty9K4h/fj+i1ZooFwQp7kwA X-Received: by 2002:a17:907:76c7:: with SMTP id kf7mr27465572ejc.470.1618242533874; Mon, 12 Apr 2021 08:48:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618242533; cv=none; d=google.com; s=arc-20160816; b=E7YSb67cf8qqllLujsTWN42vFuHUoVMsLGofqM9d/tzOzul3tfmXnleIr+EDi88Mul 8rVIxwaKusHLK3eGRM4EGgyiFblw2Rf/wl5Dl22+IP3S0ctMqPPDRHaWYS4CSeUuBk8p dXCSCSmlRDQvQcgmtS0ZGZvTkbv+F5HbBFsrO20bSvQ9rNEmFXisExE40qhABa042KVX 3/+clJHTl1twt5A7ltXRtHSQKBTDLgYpd//duhgKqRgoY6YcUOMSosZukuCLqA3cw7sQ qWmdtukUiSCYkQlpYnVxO7UbzIqnXvUQxGBm+ATXs4nvvR7cGlKTtJsACIbRUkIhOwYC MDtw== 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=C5yifgBCYwZlPKVIyE+QuEC/SZu8A/X0aWV6755nZTk=; b=e5ndEFD6rNVbQxRF91KHr0QwQfTuEAtVTGXk1DG6Ft0Fqi5pbAl/rqseW68mKuFw2M TP9h2rC7vfs/g86hGuBCUQon8QfTK5W2behxBl6qjjB9Tj5moXh3BlGFn8sf/vLLqsIc Gr1rswGp+Gt7L+55PD+EW4r3I0hyXwiIDVm+DHW7uQd9Sya4dEZ406CtBnk70pgZbCKK IsA7z2sPjlC9ngRyxthVpMVi7x4l1zhwK2Q1G8ILO3O3XY8oLahG5CCN60uPr23NW1HB hAHJDAsqC4cx9ZWy1D2yqn96p1bgtA9FlYXDaf6Q8s/eQOF0rMlEFnCOjKRYXIpRoMYA 5iVQ== 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 a23si7691304edy.94.2021.04.12.08.48.28; Mon, 12 Apr 2021 08:48:53 -0700 (PDT) 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 S243105AbhDLPrT (ORCPT + 99 others); Mon, 12 Apr 2021 11:47:19 -0400 Received: from lizzard.sbs.de ([194.138.37.39]:54248 "EHLO lizzard.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243040AbhDLPrQ (ORCPT ); Mon, 12 Apr 2021 11:47:16 -0400 Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id 13CFkQqf031101 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 12 Apr 2021 17:46:26 +0200 Received: from md1za8fc.ad001.siemens.net ([139.22.41.180]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 13CFZWJi006717; Mon, 12 Apr 2021 17:35:32 +0200 Date: Mon, 12 Apr 2021 17:35:31 +0200 From: Henning Schild To: "Enrico Weigelt, metux IT consult" , Andy Shevchenko Cc: , , , , Srikanth Krishnakar , Jan Kiszka , Gerd Haeussler , Guenter Roeck , Wim Van Sebroeck , Mark Gross , Hans de Goede , Pavel Machek Subject: Re: [PATCH v3 3/4] watchdog: simatic-ipc-wdt: add new driver for Siemens Industrial PCs Message-ID: <20210412173531.4140e461@md1za8fc.ad001.siemens.net> In-Reply-To: References: <20210329174928.18816-1-henning.schild@siemens.com> <20210329174928.18816-4-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 Am Thu, 1 Apr 2021 18:15:41 +0200 schrieb "Enrico Weigelt, metux IT consult" : > On 29.03.21 19:49, Henning Schild wrote: > > Hi, > > > This driver adds initial support for several devices from Siemens. > > It is based on a platform driver introduced in an earlier commit. > > Where does the wdt actually come from ? > > Is it in the SoC ? (which SoC exactly). SoC-builtin wdt is a pretty > usual case. > > Or some external chip ? > > The code smells a bit like two entirely different wdt's that just have > some similarities. If that's the case, I'd rather split it into two > separate drivers and let the parent driver (board file) instantiate > the correct one. In fact they are the same watchdog device. The only difference is the "secondary enable" which controls whether the watchdog causes a reboot or just raises an alarm. The alarm feature is not even implemented in the given driver, we just enable that secondary enable regardless. In one range of devices (227E) that second enable is part of a pio-based control register. On the other range (427E) it unfortunately is a P2SB gpio, which gets us right into the discussion we have around the LEDs. With that i have my doubts that two drivers would be the way to go, most likely not. Only that i have no clue which pinctrl driver should be used here. My guess is "sunrisepoint" because the CPUs are "SkyLake" i.e. i5-6442EQ, i3-6102E And "grep INT344B /sys/firmware/acpi/tables/DSDT" matches. I booted a kernel patched with the series from Andy but the "pinctrl-sunrisepoint" does not seem to even claim the memory. Still trying to understand how to make use of these pinctrl drivers they are in place but i lack example users (drivers). If they should be available in sysfs, i might be looking at the wrong place ... /sys/class/gpio/ does not list anything regards, Henning > > --mtx >