Received: by 2002:a25:ca44:0:0:0:0:0 with SMTP id a65csp1096781ybg; Mon, 27 Jul 2020 07:51:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwpHcMWLx6hR9TrRc3QZaWvmZty+V7mQM/HlbnhybAjyUtiyO/34BN1O4MhviIHLyITYSnR X-Received: by 2002:a17:906:c08a:: with SMTP id f10mr11560109ejz.181.1595861467470; Mon, 27 Jul 2020 07:51:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595861467; cv=none; d=google.com; s=arc-20160816; b=wY9+c2bucXvF9k/KqIwutReslOk/M88B3QO1XRuP/BaHIyzRbIe3695aUq3jVxVLwD JCCSyyJ3ht7adm0OBIGu5UF86xzrb7kcAK0+30baCdCwMjw6KjFJPgxxIB4WCObx5fOV qL2Zrl97xckHsrArwwEhQJ7Z5bJoMoVStvqeUUQno2e5/u9hXnDs9nlNrvamBayXc4lz b6T+u0fuUmqJwQGjU8qAI30INsFyBxEx7LaXL4rNp1HOlzV9jnofJGuYXnO5dQbutqsY 02XyunCu8T9BSOHqK34mqQdtxiP4H5e+tT0hVhwpeJRiGNS5CkMNJgYdQyuI9v9X6lTB h6+A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=Ec71WM+sUQ5k/kErEm7BJx6XgiCan9aAFPHfcSD5XKA=; b=rzeRtqsuRQeFaRUdRMG+bTCv1LRQ1k0fwy59eGoeqTXwlnOqUo6LHo3vv90HibDlQo jvLYfey1XYFt6A/qAy/hVe1SETfvNYJ+PIQ2HzLL0Px8rRqs1wtPrsjrr11duyiTDzth Gx6XAI86TpuZM7N1LiELqWKkqnJaLeJ3FL6TF84KfDFmjsJ/0moJwajRoWqYvieHZNz6 O2zfCHoGDsX3KOztFpVT0r0YNGSw7DnI1GXtCq58bKp6GqQkL8FUbiNZLPLMmjgvksVr cFy6gG9FYJZfL32j6xSMmC+fhgbqpnqm8LnkHaBjU/IcALBMZyLZYas4asS9PbHLAG+x /cxg== 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 m10si2390353edb.371.2020.07.27.07.50.45; Mon, 27 Jul 2020 07:51:07 -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 S1729378AbgG0Oto (ORCPT + 99 others); Mon, 27 Jul 2020 10:49:44 -0400 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:57899 "EHLO relay4-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728314AbgG0Otn (ORCPT ); Mon, 27 Jul 2020 10:49:43 -0400 X-Originating-IP: 90.66.108.79 Received: from localhost (lfbn-lyo-1-1932-79.w90-66.abo.wanadoo.fr [90.66.108.79]) (Authenticated sender: alexandre.belloni@bootlin.com) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 50C81E0019; Mon, 27 Jul 2020 14:49:38 +0000 (UTC) Date: Mon, 27 Jul 2020 16:49:38 +0200 From: Alexandre Belloni To: Russell King - ARM Linux admin Cc: Rob Herring , miguelborgesdefreitas@gmail.com, a.zummo@towertech.it, baruch@tkos.co.il, shawnguo@kernel.org, s.hauer@pengutronix.de, kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/3] dt-bindings: rtc: pcf8523: add DSM pm option for battery switch-over Message-ID: <20200727144938.GC239143@piout.net> References: <20200719145028.3370-3-miguelborgesdefreitas@gmail.com> <20200720112401.4620-1-miguelborgesdefreitas@gmail.com> <20200720112401.4620-2-miguelborgesdefreitas@gmail.com> <20200723174905.GA596242@bogus> <20200723195755.GV3428@piout.net> <20200727094553.GH1551@shell.armlinux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200727094553.GH1551@shell.armlinux.org.uk> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 27/07/2020 10:45:53+0100, Russell King - ARM Linux admin wrote: > > This is but this shouldn't be a DT property as it has to be changed > > dynamically. I'm working on an ioctl interface to change this > > configuration. > > Why does it need to be changed dynamically? If the hardware components > are not fitted to allow the RTC to be safely used without DSM, then > why should userspace be able to disable DSM? For RTCs with a standby mode, you want to be able to return to standby mode. That would happen for example after factory flashing in that common use case: - the board is manufactured - Vbackup is installed, the RTC switches to standby mode - the board is then booted to flash a system, Vprimary is now present, the RTC switches to DSM. At this point, if the board is simply shut down, the RTC will start draining Vbackup before leaving the factory. Instead, we want to be able to return to standby mode until the final user switches the product on for the first time. -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com