Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp5752830ybp; Tue, 8 Oct 2019 07:48:47 -0700 (PDT) X-Google-Smtp-Source: APXvYqw8JHRb6+HDKOT1VkQ73/xp5HxMK59etnuYk0yP61FzzwV/yOkKh74i7i1nEtME7nXmV4TP X-Received: by 2002:a17:906:8308:: with SMTP id j8mr28298260ejx.142.1570546127160; Tue, 08 Oct 2019 07:48:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570546127; cv=none; d=google.com; s=arc-20160816; b=NLfkwdXIcF/fMmu0LOhYpP/6A28rMT3zzmMxb9TIgnXRV+s+uidcnigMmX1WvVSpNE vJJ7Qnzn9yD5v5rOSwG3OZxY/t/xctZGyQLYiop9Jd/ZWx1XiYJlUbJFJ/TLBJpk1+NI YyqnBXCsxNwv87kzsobMctzpclz0Wa0XgPeYxsR3GXrVwOYScfTNYIGbc3lBL73UCf9I NX52mEY4P8G+UqTT+mPUs/2PVglvk5nAWP5KjFQFePe94EOoQp9n7ZZ852miXtz4rHp0 sQe5MhJFgi9OXGWuzXXaW0yCAejd1haumaXKu9ifep6Hkr0sPw2yKlunjhXK0IhtVyDh 3Xfw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=+WdTHXuUixIUcyi6dAHim2vrdi6y6drkCwMYzOiC+Kw=; b=trCBm2+4DkrRPfAcVH3AmLB12jXmVO9SFh0/GwV8NVbH+FFZ5+gk4M2h17TvU1uObA N8z9Xe4IIqOVIXuY9S5rXz3zxiF90BU2ZyYH9GAh5t+MV+MBFkhhgArRyg1skNfaaUs1 F6AD8rzB6GQ1UGB+z7xN6bbAFkZcxMEflGyoEfbigbmFdJNlvjwyRzwhG/rh4tmKymGM O2uBZqVVCLrxQIW0+b8a787pOoR1KnJkVtav5U2RK1O02ik6yDANXP9S6PTobtTMyhUA 6jCDExQd22KaLHkRsF3tkAD0v1T19OoCEj7qPlfkEeZ/+Dn4s95IxDf7PbF//X/f1jkS ps1A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v25si11223864edb.286.2019.10.08.07.48.23; Tue, 08 Oct 2019 07:48:47 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727372AbfJHOpk (ORCPT + 99 others); Tue, 8 Oct 2019 10:45:40 -0400 Received: from metis.ext.pengutronix.de ([85.220.165.71]:54565 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726416AbfJHOpk (ORCPT ); Tue, 8 Oct 2019 10:45:40 -0400 Received: from pty.hi.pengutronix.de ([2001:67c:670:100:1d::c5]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iHqk0-0001Zs-Vp; Tue, 08 Oct 2019 16:45:32 +0200 Received: from ukl by pty.hi.pengutronix.de with local (Exim 4.89) (envelope-from ) id 1iHqjz-0001yc-As; Tue, 08 Oct 2019 16:45:31 +0200 Date: Tue, 8 Oct 2019 16:45:31 +0200 From: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= To: Fabrice Gasnier Cc: thierry.reding@gmail.com, alexandre.torgue@st.com, benjamin.gaignard@st.com, linux-pwm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com Subject: Re: [PATCH] pwm: stm32: add comment to better describe breakinput feature Message-ID: <20191008144531.pjt525xuz7n5a3hq@pengutronix.de> References: <1570534887-26181-1-git-send-email-fabrice.gasnier@st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1570534887-26181-1-git-send-email-fabrice.gasnier@st.com> User-Agent: NeoMutt/20170113 (1.7.2) X-SA-Exim-Connect-IP: 2001:67c:670:100:1d::c5 X-SA-Exim-Mail-From: ukl@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 08, 2019 at 01:41:27PM +0200, Fabrice Gasnier wrote: > Add a comment to better describe the purpose of breakinput feature that > can be found on some STM32 timer instances. Briefly comment on the > characteristics of this input for PWM, and pinmuxing as suggested in [1]. > > [1] https://lkml.org/lkml/2019/10/1/207 > > Signed-off-by: Fabrice Gasnier > --- > drivers/pwm/pwm-stm32.c | 8 +++++++- > 1 file changed, 7 insertions(+), 1 deletion(-) > > diff --git a/drivers/pwm/pwm-stm32.c b/drivers/pwm/pwm-stm32.c > index 359b085..6406ebb 100644 > --- a/drivers/pwm/pwm-stm32.c > +++ b/drivers/pwm/pwm-stm32.c > @@ -522,8 +522,14 @@ static int stm32_pwm_apply_breakinputs(struct stm32_pwm *priv, > sizeof(struct stm32_breakinput)); > > /* > + * Some timer instances can have BRK input pins (e.g. basically a fault > + * pin from the output power stage). The break feature allows a safe > + * shut-down of the PWM outputs to a predefined state. Further details > + * are available in application note AN4277, "Using STM32 device PWM > + * shut-down features..." Without having read the application note I don't understand the purpose. Not sure if this should be a show stopper though. > * Because "st,breakinput" parameter is optional do not make probe > - * failed if it doesn't exist. > + * failed if it doesn't exist. The pinctrl handle must hold the BRK > + * pin(s) when using "st,breakinput" property. Is this a comment that has a better place in the binding doc? Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |