Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1003475yba; Wed, 24 Apr 2019 13:16:49 -0700 (PDT) X-Google-Smtp-Source: APXvYqw/1UvW3p4GFid9jMMvqJpogXnojMw+6s0D4Or1+jxNDPj7ynjutBEvEONkteHeHAycc09q X-Received: by 2002:a63:4558:: with SMTP id u24mr31198185pgk.225.1556137009233; Wed, 24 Apr 2019 13:16:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556137009; cv=none; d=google.com; s=arc-20160816; b=pt77FIK/N1DMJ2LxpvY798WkCDkZ26T0pgujzngRHw0lffbbav9Q5/4eEX7WIRdS8C C1MJpsAIxHjgG2q+e/0zZGZI8Lrkx+Tbjfe4eA6R/5+kvanEW3aJhdxk0HwAZnT3LPCF tcYFp8REcnlLg8IwH9CGvQy+w878ZXD9E9mWdzIjKYUJIvs8P2B6bm6hjCatOLK80zqN Wasc7yM5K6WtktxRdmDno4JrhpZIH5W4JMa5hoHZ2U3JJoTgUzTXcTvUfvr4NoMpv9N+ dDR1g4dJSfzjt7OHTDOnc4ltx1+DHmnAQ2476vnTY7wnJyrNlSDgbrNFPJtO0y2UACRh l9kA== 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 :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=f++upxnFVwYNGoQza4rrfn5IDnsEnbAH3nZs4tNmbuU=; b=1J3//gK8fMWEpKehfBGRLYEW+sdgaCcChF5EfzRUnhXfzzc3UOEe/4I3SwiDYFKyTZ 5QKs5WGqn26gNmG0/i9B92Vuo0NP5RCXj3FjSGmmgnbJldNfpRPrK8FzKF9kBoRSIO1T /0/3vFYHRLUw1GjaUjRC08tzeND6ONDGs9zrXMHgB/wZmFUhKOaJoEBaVh9yTyspMEeK VfCAsBxzO/cLDvG6mHwJ7UwShTpqrXaVyssfuo5yALgPDb1REOJQ6dTf/tN3BsHQp8a1 2E+fqybTmUAh3ou+0aLK8Q6dG9SBff4Z+aiiudZdOCNnRnMRKraqXszBrYva8WQd2rry 5w3Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Lp6RUjgu; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l184si1910170pfl.43.2019.04.24.13.16.34; Wed, 24 Apr 2019 13:16:49 -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=Lp6RUjgu; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730780AbfDXOeA (ORCPT + 99 others); Wed, 24 Apr 2019 10:34:00 -0400 Received: from mail.kernel.org ([198.145.29.99]:37886 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730639AbfDXOd5 (ORCPT ); Wed, 24 Apr 2019 10:33:57 -0400 Received: from sasha-vm.mshome.net (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 0C7E1218FD; Wed, 24 Apr 2019 14:33:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1556116436; bh=K2kkRlrQwKuVZPagHmuVSa/rBWqwm+gpMlPD9DdRpCg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Lp6RUjguRcJUo3Q4wvssf4G4UG8rXfB3JhISxSLI2CgKwiy8ISW8rGO9EYPdrwFeA H57xgBZKEPXXksZLWMO5+Vwqsg1Ror1JhxqnBgG/pYm4HK20THFH5AIjnCpS1kPwJ9 9Cqgzm0Ja0xClej7bVzDg41wQ/4VXzjNpOU50an8= From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Geert Uytterhoeven , Alexandre Belloni , Sasha Levin , linux-rtc@vger.kernel.org Subject: [PATCH AUTOSEL 5.0 06/66] rtc: sh: Fix invalid alarm warning for non-enabled alarm Date: Wed, 24 Apr 2019 10:32:40 -0400 Message-Id: <20190424143341.27665-6-sashal@kernel.org> X-Mailer: git-send-email 2.19.1 In-Reply-To: <20190424143341.27665-1-sashal@kernel.org> References: <20190424143341.27665-1-sashal@kernel.org> MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Geert Uytterhoeven [ 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 (Microsoft) --- 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 d417b203cbc5..1d3de2a3d1a4 100644 --- a/drivers/rtc/rtc-sh.c +++ b/drivers/rtc/rtc-sh.c @@ -374,7 +374,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.19.1