Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp273652yba; Wed, 3 Apr 2019 08:30:13 -0700 (PDT) X-Google-Smtp-Source: APXvYqxKMLVbf3o2A9MjFEkB/3w0nVM0ZaPjvuEEcKETwKwKcR9PDZSGV3e2Q37IwVMez5x8AmMR X-Received: by 2002:a63:20f:: with SMTP id 15mr306342pgc.90.1554305413294; Wed, 03 Apr 2019 08:30:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554305413; cv=none; d=google.com; s=arc-20160816; b=z4fmTNwUI9w9p6hA03iKFoKIxDwq4BxkKSzU29kPV+7UMAf/8l+tSHgDtCRXGOf9rJ JjHLKvWCJ3taC7lY3G9+XzNxrz8upNml8wMUIHitzDTGL/NwONkd38jj6tv8tekSAe1U d1vv9ZRk2ArWUjykG8j8DXj4Wlqn9OkU2dSP9quNfiXpHumD9Zu389DucbH6GaEKM79o GVCgfSGidfLiYVeCkMRHgiDdbuT+jdG8qAJOG0SHEoDw7jdieJKWmIhTQ8/xSuOjCTu5 J8VN4vnZPvQfDoYxOYyGp4T97PDdhAoBv2t9oBtVNVRh6d0AVO0OuvM0n2M7YuhG9W87 rzHg== 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-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=uMpG735wXp4SaQVVpyQtd3Zd6Nrx6fm+0YM0f/xKTU8=; b=VrNWWS4J6BAh5RIy6v4+KqAbaprB/pMtQdW6olnKeBC6Ql/K28Qs60/U6hmZlYkG2D +nSU/01W5JrAGVe/2mBawPsO3scLyq6DFDW22zcDvgMGTNHnoiIwepfVAd3+FdUdJsw/ GBSntWCWer/1L04SAVlIM3HvwHSLQG64vhFW/YFOORuCjD3EvE8RNaoM110cBwkfCPe6 TAc/V2Ce8VMjRrZxa5522W2UpaJ38niCcw3gsnZYGaonVBwqGCFvZAEvlDwUh/efN3+U lXrtcV6KxOpfA32GYx4g/oApS9hfXvLs5Ug/D7elA2S7tItMQIBh03/E6TFmq+YC3lFa rSDg== 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 m8si13200515pgp.68.2019.04.03.08.29.57; Wed, 03 Apr 2019 08:30:13 -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 S1726584AbfDCP3B (ORCPT + 99 others); Wed, 3 Apr 2019 11:29:01 -0400 Received: from relay8-d.mail.gandi.net ([217.70.183.201]:56215 "EHLO relay8-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725990AbfDCP3B (ORCPT ); Wed, 3 Apr 2019 11:29:01 -0400 X-Originating-IP: 109.213.83.19 Received: from localhost (alyon-652-1-60-19.w109-213.abo.wanadoo.fr [109.213.83.19]) (Authenticated sender: alexandre.belloni@bootlin.com) by relay8-d.mail.gandi.net (Postfix) with ESMTPSA id 246621BF213; Wed, 3 Apr 2019 15:28:57 +0000 (UTC) Date: Wed, 3 Apr 2019 17:28:56 +0200 From: Alexandre Belloni To: Flavio Suligoi Cc: Alessandro Zummo , Rob Herring , Mark Rutland , "linux-rtc@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 1/2] dt-bindings: rtc: add battery-low-hw-alarm property Message-ID: <20190403152856.GP22216@piout.net> References: <1554303165-24813-1-git-send-email-f.suligoi@asem.it> <20190403145709.GN22216@piout.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.3 (2019-02-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/04/2019 15:06:17+0000, Flavio Suligoi wrote: > Hi Alexandre, > > > Hi, > > > > On 03/04/2019 16:52:44+0200, Flavio Suligoi wrote: > > > Some RTC devices have a battery-low automatic detection circuit. > > > The battery-low event is usually reported with: > > > > > > - a bit change in a RTC status register > > > - a hw signaling (generally using an interrupt generation), changing > > > the hw level of a specific pin; > > > > > > The new property "battery-low-hw-alarm" enable the RTC to generate the > > > hw signaling in case of battery-low event. > > > > > > Signed-off-by: Flavio Suligoi > > > --- > > > Documentation/devicetree/bindings/rtc/rtc.txt | 3 +++ > > > 1 file changed, 3 insertions(+) > > > > > > diff --git a/Documentation/devicetree/bindings/rtc/rtc.txt > > b/Documentation/devicetree/bindings/rtc/rtc.txt > > > index a97fc6a..f93a44d 100644 > > > --- a/Documentation/devicetree/bindings/rtc/rtc.txt > > > +++ b/Documentation/devicetree/bindings/rtc/rtc.txt > > > @@ -31,6 +31,9 @@ below. > > > expressed in femto Farad (fF). > > > The default value shall be listed (if > > optional), > > > and likewise all valid values. > > > +- battery-low-hw-alarm : Enable the "battery-low" output pin. This > > function > > > > I would name that voltage-low-alarm as not all the secondary voltages > > are batteries. > > You have right. So we can also name the property a: "voltage-low-hw-alarm". > I prefer to have the word "hw" in the property name, since the "sw" voltage > low alarm is already present is some RTC drivers. > In this way, with the word "hw", is more clear that we are speaking about > an hw pin signaling. > Well, the device tree always describes the hardware so there is no point in specifying hw. -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com