Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1185425yba; Sat, 6 Apr 2019 05:58:52 -0700 (PDT) X-Google-Smtp-Source: APXvYqwLj8OHQSgPRQYhHz08OG2xAm56VoMNajEZSMD0KFwvn8FphE2PNd0VzT9BKHk8bNjfpPOH X-Received: by 2002:a63:3185:: with SMTP id x127mr17842033pgx.299.1554555531968; Sat, 06 Apr 2019 05:58:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554555531; cv=none; d=google.com; s=arc-20160816; b=B3XcI0rt8OfTNO1rJXPnlPwq1e2ChDHdLtcV9QKhIYiB1MPPv7KP7rxy+CbEd22LUX GMDzulmpgCxHWqtN3I90oTzBfm6HXuDPBczkOjxIE2jiPSKSMdK4s0cK8N2TwPXYuKX1 5JsUS0S9ZDeHPdbbwHrVVE5+uWzXIkIlnhc0+KzVMvswgYRFI6laCblmcdUWfFlCWeyy AyXfp9pYuJYkz6erXiWqV6P8/r9cJKB/jHFEff19P4obNQeoIGNsRiipRNvTOYAV97Lg VwXZX4LVoqG4HhwKeUS8xBjF2xOX3lBwdGyZppCz5mMo+RaRE6u44TlodRIsyLSas0RH oLjg== 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=ZD15ce0bv/uKm9JCrAJQnZTZVzevKPNOX+tJJJCw/qY=; b=pXrbUaEWpsJ9d40HA0mGbM/f7yEP6eQ/DLhnsMdP73IBOWLNJqsZEmpk7UtgO8PXZk T9mCIaayVEFEHjFYhr7RKAwgkaRO4c+djgQ5pP9ZfMtB5aNAO5/rbp26gdiQzXxx4wDS El+RB9QbVK+1BZ5TipF00BfGIw422CfPu8+DO0WlLiiotAikOsFft3rdtuQAYQqq0kPQ XYCXzbUSD2+GaqIbzGznxGuQYnPuZiVvhEZv9chEwwvxlutsX8oaeo9i1obvNCprky6Y hLCDM3+4hG3htA1vk/qy0s+klR6MXvtNTmg6fCTz/ZtTGv8a/vja4H7yaBRIImyUIjfO y7Kg== 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 a2si965380pgt.564.2019.04.06.05.58.23; Sat, 06 Apr 2019 05:58:51 -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 S1726467AbfDFMzy (ORCPT + 99 others); Sat, 6 Apr 2019 08:55:54 -0400 Received: from relay1-d.mail.gandi.net ([217.70.183.193]:41747 "EHLO relay1-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726316AbfDFMzx (ORCPT ); Sat, 6 Apr 2019 08:55:53 -0400 X-Originating-IP: 86.202.231.219 Received: from localhost (lfbn-lyo-1-149-219.w86-202.abo.wanadoo.fr [86.202.231.219]) (Authenticated sender: alexandre.belloni@bootlin.com) by relay1-d.mail.gandi.net (Postfix) with ESMTPSA id 63466240003; Sat, 6 Apr 2019 12:55:50 +0000 (UTC) Date: Sat, 6 Apr 2019 14:55:50 +0200 From: Alexandre Belloni To: Rob Herring Cc: Flavio Suligoi , Alessandro Zummo , 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: <20190406125550.GA7480@piout.net> References: <1554303165-24813-1-git-send-email-f.suligoi@asem.it> <5ca84214.1c69fb81.e3ace.21e5@mx.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5ca84214.1c69fb81.e3ace.21e5@mx.google.com> 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 06/04/2019 01:07:13-0500, Rob Herring wrote: > On Wed, Apr 03, 2019 at 04:52:44PM +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 > > + is available on the following devices: > > + - pcf2127 - pin used for alarm: INTn > > Boolean? If there's cases where which pin is selectable, then we'd need > this to take a value. Not sure how likely that is? > Indeed, there is at least the pcf85363 that has two possible pins for that interrupt. How would you select the pin then? a zero based index? a string? -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com