Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp510121yba; Wed, 15 May 2019 05:23:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqyd2Z1f/PIwdWnWr9ubxeN36FDNpxy4UVuHeVEDXhYyOA21SdFZBvhwVypGk2qM5ZKQ2666 X-Received: by 2002:a65:5682:: with SMTP id v2mr44115955pgs.100.1557923007329; Wed, 15 May 2019 05:23:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557923007; cv=none; d=google.com; s=arc-20160816; b=qaAAdC1Y2x/9w63ooCnFgQRFKa/xAJF+BMy/cVbTI2SfvV1VTtf2SRtVMi0QTBNnek 6qk53CI6AB4eCB/Om9A4D8ncL2BKVuA2WGMnwkEH8MaVUCLXiPVy3PA+DeFZWqVxFmXc JMWvYH1qu4PiVHUd/9aAKDHDN5D+lSQhUFgypaps8YMb2YYkpy24NiftznEBAPyTC00C Us0x72dq8gGMTfLMDhDOAxFRmuxb//kT7kRX0rzeeI2ZE1PNVZYzionAKV1xA6MeCFs3 L7Qh4a82k2BmPptzJ5rz7Bp6aS4g5KMw+leXRZCWmXdvukAXpCnghqNhdzDv5GVNjXLw 0amw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=gtOJyi+mz4n0QHz1Zf7eAkIy/DBv93C1Nhj6XUDIlpE=; b=w9M62p740TAAZJvB1jqnfFIobsNa8jR76Kl5dImHkYGMPuxNB/jU0FKv5T/2OU+m6u yjXo3dFQmH2pWRHXZ94w5FCAVbMlFopSLrDAMu864HZcyQihhPsibp1zNmcvGrLk0zEf kgnlIicvURxYcqHzd3PZxugeP///ctzK9UwXIjY4A4Wy1Ay2Qm8cwdpRNQ7h9wWrBA45 ajNM0BGZYAegQW1torJZb5y/jlGDVCxdLLCPjSQc8Vc2hhRfDCzjiNp8q/c3bvewDdjF zs5CiZ86/YVsbW9PxT4oACk5yeVyT3XAVwlnphzEm6SVwuMKMPXEKzhQqGW102JPxBUl 1uFg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=YhZiPUFu; 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 z143si1828856pfc.38.2019.05.15.05.23.12; Wed, 15 May 2019 05:23:27 -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; dkim=pass header.i=@kernel.org header.s=default header.b=YhZiPUFu; 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 S1727108AbfEOK7Q (ORCPT + 99 others); Wed, 15 May 2019 06:59:16 -0400 Received: from mail.kernel.org ([198.145.29.99]:55744 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726296AbfEOK7P (ORCPT ); Wed, 15 May 2019 06:59:15 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5AE4321881; Wed, 15 May 2019 10:59:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1557917954; bh=/aWhPZJ6uNNDo2118noQh/BUYWHFCadlSsiybRkSSSk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=YhZiPUFun8clagBeewfbIMFXHr4id2494LPDUYdSYJcKRSVfE1TaeI84WKXTshmS+ VtgPoqytaxHE0ZJ3DzJ1nY68RczPHFMiP9dlNEGUEgvYNtTZ3Jj6PPg0FDkGtsRP4p BkEDcfc3HpDUcO3aA0NuWDUieHjPBRBvPp+37o8I= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Geert Uytterhoeven , Alexandre Belloni , Sasha Levin Subject: [PATCH 3.18 38/86] rtc: sh: Fix invalid alarm warning for non-enabled alarm Date: Wed, 15 May 2019 12:55:15 +0200 Message-Id: <20190515090650.236950353@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190515090642.339346723@linuxfoundation.org> References: <20190515090642.339346723@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [ Upstream commit 15d82d22498784966df8e4696174a16b02cc1052 ] When no alarm has been programmed on RSK-RZA1, an error message is printed during boot: rtc rtc0: invalid alarm value: 2019-03-14T255:255:255 sh_rtc_read_alarm_value() returns 0xff when querying a hardware alarm field that is not enabled. __rtc_read_alarm() validates the received alarm values, and fills in missing fields when needed. While 0xff is handled fine for the year, month, and day fields, and corrected as considered being out-of-range, this is not the case for the hour, minute, and second fields, where -1 is expected for missing fields. Fix this by returning -1 instead, as this value is handled fine for all fields. Signed-off-by: Geert Uytterhoeven Signed-off-by: Alexandre Belloni Signed-off-by: Sasha Levin --- drivers/rtc/rtc-sh.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/rtc/rtc-sh.c b/drivers/rtc/rtc-sh.c index d0d2b047658b..dcd5dcae7b3c 100644 --- a/drivers/rtc/rtc-sh.c +++ b/drivers/rtc/rtc-sh.c @@ -455,7 +455,7 @@ static int sh_rtc_set_time(struct device *dev, struct rtc_time *tm) static inline int sh_rtc_read_alarm_value(struct sh_rtc *rtc, int reg_off) { unsigned int byte; - int value = 0xff; /* return 0xff for ignored values */ + int value = -1; /* return -1 for ignored values */ byte = readb(rtc->regbase + reg_off); if (byte & AR_ENB) { -- 2.20.1