Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp228499pxf; Wed, 10 Mar 2021 05:09:27 -0800 (PST) X-Google-Smtp-Source: ABdhPJy5FXc70+PPag16n7duHtmDyF1VslL7P7AQhK1xBxQwqE95aMjV2kgP5k1AMBOhu2v6Nw7i X-Received: by 2002:a17:906:5797:: with SMTP id k23mr3648710ejq.515.1615381767764; Wed, 10 Mar 2021 05:09:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1615381767; cv=none; d=google.com; s=arc-20160816; b=WSNcJT6KEDq2wiVWqYcRE3zbFPUqvik3mCo1Qryi2v3wIDQ9U+/3PjQJIo0QHy75WA +e2h/rdkiPS//Vh6iLDUGE2Zzbg98gk88DzQIjagmhv06COuqo+9cONpad+YqPS2xnM0 MJW9/chZ/tUlaap3DDV4KXmTct28ucirLBrz9ri843/fy4pKvbbwh4H6XxnkodpYKUas UD/lr/zgjZZCe78dRqd37s6qJdWDepX3YOHKDp9pdPSFI3h/LULMsTPtEWna+sthQn55 6pVchlXH5HJ8GcRULICUh2/b44GFzFyFD3OdAdvla61Yhsxl5uaJh+YZuQ74/nMmxNhh pQ7g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-disposition:mime-version:message-id :subject:cc:to:from:date; bh=qflibBTi6EIDGcd6mbBU0np69J0uiNd3JypeskB6oSs=; b=E4f511k+mXnydWJPY1r/PI0X47P26ZgsjXO8sX0B9i4M6dbmQ1OfEIJ29sL0FNuFYJ +ze03fa+PZMs62Ahy/wN8Rgx3x4Fi8gFPuc1oY+QslCvA+GoNzEs8kEnp9+0IHuh0VLL KBDUWZZUmuxlfzgCi+yoOC3FmUf1ihVbhAQ+dsNw0Dc9gvOkPrnggr1nSsPLqWfAHsds mYnCu8I+DArJ32vfSqPwVRUOCyPunHEWpfik9YNRrxc0GeMq6S1MbRf6XiRyX0EJS4Qg 7HE1PAezzsE0k5Uey4wUx2O43dy9/no2Z1sBbkjFoOVyvAS1JenIM5rkywJexhH1CC78 Jnnw== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v6si11376030ejk.379.2021.03.10.05.08.56; Wed, 10 Mar 2021 05:09:27 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232130AbhCJNH6 (ORCPT + 99 others); Wed, 10 Mar 2021 08:07:58 -0500 Received: from mail-lj1-f180.google.com ([209.85.208.180]:43543 "EHLO mail-lj1-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229948AbhCJNHv (ORCPT ); Wed, 10 Mar 2021 08:07:51 -0500 Received: by mail-lj1-f180.google.com with SMTP id m11so25445541lji.10; Wed, 10 Mar 2021 05:07:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition; bh=qflibBTi6EIDGcd6mbBU0np69J0uiNd3JypeskB6oSs=; b=tyB6AF6HvnWDL0nPIoLGYuxH6a6i/QQ6bx4r4KZkz5OhjmzR7SDXM13Lb5ocY3dCQ0 8smBVt5j8yr/2OdlL1XLcIlzY74YlW0YKPNqNsKTxUBaG5RguVvhxzIlejLMWEm+C/Xt qyIKp8rovn2eT4LnExUQMuCrdbNT6UOdMTBo2nEixFdGCClG74OXGJ2ck0wh/taw/baN FQZvcQOxMBxvaOsnVTnvSytsxtpW4f2J2FdAYBac1uKe5GmZCPYxF7V90YL8foYz964U CNa+mWbl9p9yIU9pTZVkeRxtTZVojhAOuuGUpnShzl1QRIf40ZiVHG5cA+E4acAGNrX7 OiVQ== X-Gm-Message-State: AOAM533seBe7KT/g5Pn2kTDbl9wjU5aD6LVYwW0HA5UgFjlemgCHa78o QCz+C2kP2KQa+3ho2R/fUuo= X-Received: by 2002:a2e:8002:: with SMTP id j2mr1860199ljg.31.1615381669749; Wed, 10 Mar 2021 05:07:49 -0800 (PST) Received: from localhost.localdomain (dc7vkhyyyyyyyyyyyyycy-3.rev.dnainternet.fi. [2001:14ba:16e2:8300::4]) by smtp.gmail.com with ESMTPSA id e18sm3151062ljl.92.2021.03.10.05.07.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 10 Mar 2021 05:07:49 -0800 (PST) Date: Wed, 10 Mar 2021 15:07:41 +0200 From: Matti Vaittinen To: mazziesaccount@gmail.com, matti.vaittinen@fi.rohmeurope.com Cc: Liam Girdwood , Mark Brown , Rob Herring , Matti Vaittinen , Andy Gross , Bjorn Andersson , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-power@fi.rohmeurope.com, linux-arm-msm@vger.kernel.org Subject: [RFC PATCH v2 0/7] Extend regulator notification support Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Extend regulator notification support This is an RFC series for getting feedback on extending the regulator notification and error flag support. This series is built on top of the The BD9576MUF support patch series v9 which is not yet in-tree Here: https://lore.kernel.org/lkml/cover.1615219345.git.matti.vaittinen@fi.rohmeurope.com/ (The series should apply without those patches but there is compile time dependency to definitions brought in at the last patch of the BD9576 series. This should be Ok though as there is a Kconfig dependency in BD9576 regulator driver) In a nutshell - the RFC adds: 1. WARNING level events/error flags. (Patch 2) Current regulator 'ERROR' event notifications for over/under voltage, over current and over temperature are used to indicate condition where monitored entity is so badly "off" that it actually indicates a hardware error which can not be recovered. The most typical hanling for that is believed to be a (graceful) system-shutdown. Here we add set of 'WARNING' level flags to allow sending notifications to consumers before things are 'that badly off' so that consumer drivers can implement recovery-actions. 2. Device-tree properties for specifying limit values. (Patches 1, 4) Add limits for above mentioned 'ERROR' and 'WARNING' levels (which send notifications to consumers) and also for a 'PROTECTION' level (which will be used to immediately shut-down the regulator(s) W/O informing consumer drivers. Typically implemented by hardware). Property parsing is implemented in regulator core which then calls callback operations for limit setting from the IC drivers. A warning is emitted if protection is requested by device tree but the underlying IC does not support configuring requested protection. 3. Helpers which can be registered by IC. (Patch 3) Target is to avoid implementing IRQ handling and IRQ storm protection in each IC driver. (Many of the ICs implementin these IRQs do not allow masking or acking the IRQ but keep the IRQ asserted for the whole duration of problem keeping the processor in IRQ handling loop). The helper was attempted to be done so it could be used to implement roughly same logic as is used in qcom-labibb regulator. This means amongst other things a safety shut-down if IC registers are not readable. Using these shut-down retry counters are optional. The idea is that the helper could be also used by simpler ICs which do not provide status register(s) which can be used to check if error is still active. ICs which do not have such status register can simply omit the 'renable' callback (and retry-counts etc) - and helper assumes the situation is Ok and re-enables IRQ after given time period. If problem persists the handler is ran again and another notification is sent - but at least the delay allows processor to avoid IRQ loop. Patch 6 takes this notification support in use at BD9576MUF. Changelog RFC v2: Generic: - rebase on v5.12-rc2 (+ BD9576 series) - Split devm variant of delayed wq to own series Regulator framework: - Provide non devm variant of IRQ notification helpers - shorten dt-property names as suggested by Rob - unconditionally call map_event in IRQ handling and require it to be populated BD9576 regulators: - change the FET resistance property to micro-ohms - fix voltage computation in OC limit setting RFC v1: https://lore.kernel.org/lkml/cover.1613042245.git.matti.vaittinen@fi.rohmeurope.com/ Pre RFC discussion: https://lore.kernel.org/lkml/6046836e22b8252983f08d5621c35ececb97820d.camel@fi.rohmeurope.com/ -- Matti Vaittinen (7): dt_bindings: Add protection limit properties regulator: add warning flags regulator: IRQ based event/error notification helpers regulator: add property parsing and callbacks to set protection limits dt-bindings: regulator: bd9576 add FET ON-resistance for OCW regulator: bd9576: Support error reporting regulator: bd9576: Fix the driver name in id table .../bindings/regulator/regulator.yaml | 82 ++ .../regulator/rohm,bd9576-regulator.yaml | 5 + drivers/regulator/Makefile | 2 +- drivers/regulator/bd9576-regulator.c | 1041 +++++++++++++++-- drivers/regulator/core.c | 146 ++- drivers/regulator/irq_helpers.c | 428 +++++++ drivers/regulator/of_regulator.c | 58 + drivers/regulator/qcom-labibb-regulator.c | 10 +- drivers/regulator/qcom_spmi-regulator.c | 6 +- drivers/regulator/stpmic1_regulator.c | 17 +- include/linux/regulator/consumer.h | 14 + include/linux/regulator/driver.h | 176 ++- include/linux/regulator/machine.h | 26 + 13 files changed, 1870 insertions(+), 141 deletions(-) create mode 100644 drivers/regulator/irq_helpers.c base-commit: a38fd8748464831584a19438cbb3082b5a2dab15 -- 2.25.4 -- Matti Vaittinen, Linux device drivers ROHM Semiconductors, Finland SWDC Kiviharjunlenkki 1E 90220 OULU FINLAND ~~~ "I don't think so," said Rene Descartes. Just then he vanished ~~~ Simon says - in Latin please. ~~~ "non cogito me" dixit Rene Descarte, deinde evanescavit ~~~ Thanks to Simon Glass for the translation =]