Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp795697pxx; Mon, 26 Oct 2020 23:58:34 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzTByoD5yFv4SmJtGSZpSrnRUnm/iaGCvVzvCgpfFC9Hc3+qIqiivE8my6y6niR6mZLMdqf X-Received: by 2002:a17:906:370e:: with SMTP id d14mr990960ejc.259.1603781914673; Mon, 26 Oct 2020 23:58:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603781914; cv=none; d=google.com; s=arc-20160816; b=p3pn8kZKHl+7Un3/VrogXqCpgbKdIiV1fDWUH4A04SiSM8+AqUEr1eYGHg8ZhjbYuR oFmB081gwk5XuyoaD5q9Iq5EBXZrUykdhGrJ6guK2LjIA37r7FpKVau/H8ETEys1mi/b 26GPv1kahhHcSSgluYCkcqkaPrcmbqZqGXfNWoti00mhT5i0dA8FWSTbxxceEg5S0VdR CwjLXmrRClru5BGeqEpyAqBrpybhVu+AErKwVexLe+ZM9Rw5Fl8RzeEZfR84uYovZhXt q8aDmuFm+ZH7skfQWsEdSn1wclYKoe7cUkqzoiIp/Gilv16AXBvUf1RG12GZX/Kf39LO 9AgQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=FBRRcpoJWmeZwNXRDAwlVDJWVyScKm5VnXdZ6vGJGGg=; b=gcu5d6sTQz/X3B9kFMDSA9k0lKfGi2ddz4ZmDC8VDA5NxX4tvq+qX+hrFJmdPGZzQS tKIvRyqqCN5bgSBQawaXdh0WoTCxsq7m2lZjxD2EWlQhshsF9JVhMzMpKm3qYOl3vwkm SkO5OwkIf+EjxED2jjFJsV3+TFfH0gf9i7uyD2x/4PNjE4UKHtMIt3cW+HSngeGek90w 6J0ekMTVoOe9bTH8jFJQ8sofoJYH6MAnWTB8aL55rOSyUxSfilyrn2lxrjbvQiDHcWhU +IZ1ylcMvNnJ6JGgW+giowIsprM1hGkuTRSI3RwHrJxNZlAZgL0zz+hF8B9wmK4byRAh TRlA== 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 g22si369290ejx.308.2020.10.26.23.58.12; Mon, 26 Oct 2020 23:58:34 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725923AbgJZUsQ (ORCPT + 99 others); Mon, 26 Oct 2020 16:48:16 -0400 Received: from relay9-d.mail.gandi.net ([217.70.183.199]:42565 "EHLO relay9-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725771AbgJZUsP (ORCPT ); Mon, 26 Oct 2020 16:48:15 -0400 X-Originating-IP: 90.65.88.165 Received: from localhost (lfbn-lyo-1-1908-165.w90-65.abo.wanadoo.fr [90.65.88.165]) (Authenticated sender: alexandre.belloni@bootlin.com) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id 32BDCFF808; Mon, 26 Oct 2020 20:48:12 +0000 (UTC) Date: Mon, 26 Oct 2020 21:48:11 +0100 From: Alexandre Belloni To: Qiang Zhao Cc: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= , Bruno Thomsen , "linux-rtc@vger.kernel.org" , "a.zummo@towertech.it" , "linux-watchdog@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "robh+dt@kernel.org" , "kernel@pengutronix.de" , Wim Van Sebroeck , Guenter Roeck Subject: Re: [PATCH 0/2] rtc: pcf2127: only use watchdog when explicitly available Message-ID: <20201026204811.GD75353@piout.net> References: <20200924074715.GT9675@piout.net> <20200924105256.18162-1-u.kleine-koenig@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 26/10/2020 07:23:26+0000, Qiang Zhao wrote: > Any update for this patchset? > The whole point would be to get the DT and the watchdog maintainers agree on the property name. Once done, the driver implementation is trivial and will get applied. > Best Regards > Qiang Zhao > > > -----Original Message----- > > From: Uwe Kleine-König > > Sent: 2020年9月24日 18:53 > > To: Alexandre Belloni ; Qiang Zhao > > ; Bruno Thomsen > > Cc: linux-rtc@vger.kernel.org; a.zummo@towertech.it; > > linux-watchdog@vger.kernel.org; devicetree@vger.kernel.org; > > linux-kernel@vger.kernel.org; robh+dt@kernel.org; kernel@pengutronix.de; > > Wim Van Sebroeck ; Guenter Roeck > > > > Subject: [PATCH 0/2] rtc: pcf2127: only use watchdog when explicitly available > > > > Hello, > > > > now that there are two people stumbling over the pcf2127 driver providing a > > non-functional watchdog device, here comes an RFC patch to address this. > > > > Note this is only compile tested and dt-documentation is still missing. > > Still send this series because the cleanup is nice independent of this discussion > > and to have something to argue about. > > > > Does someone can offer a better name than "has-watchdog", is there a scheme > > that could be used already that I'm not aware of? > > > > Best regards > > Uwe > > > > Uwe Kleine-König (2): > > rtc: pcf2127: move watchdog initialisation to a separate function > > [RFC] rtc: pcf2127: only use watchdog when explicitly available > > > > drivers/rtc/rtc-pcf2127.c | 57 ++++++++++++++++++++++----------------- > > 1 file changed, 32 insertions(+), 25 deletions(-) > > > > -- > > 2.28.0 > -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com