From: Rahul Tanwar <rahul.tanwar@linux.intel.com>
To: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
hpa@zytor.com, tony.luck@intel.com, x86@kernel.org,
a.zummo@towertech.it, alexandre.belloni@bootlin.com,
robh+dt@kernel.org, mark.rutland@arm.com
Cc: linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
andriy.shevchenko@intel.com, alan@linux.intel.com,
linux-kernel@vger.kernel.org, qi-ming.wu@intel.com,
cheol.yong.kim@intel.com, rahul.tanwar@intel.com,
Rahul Tanwar <rahul.tanwar@linux.intel.com>
Subject: [PATCH v1 2/2] dt-bindings: rtc: Add optional status property
Date: Thu, 22 Aug 2019 15:44:04 +0800 [thread overview]
Message-ID: <1b01287241d49638c43222d32f3ece5a38c95ddf.1566458029.git.rahul.tanwar@linux.intel.com> (raw)
In-Reply-To: <cover.1566456205.git.rahul.tanwar@linux.intel.com>
In-Reply-To: <cover.1566458029.git.rahul.tanwar@linux.intel.com>
Some products may not support MC146818 RTC CMOS device. Introduce a optional
'status' standard property for RTC-CMOS to indicate if the MC146818 RTC device
is available (status="okay") or not (status="disabled")
Signed-off-by: Rahul Tanwar <rahul.tanwar@linux.intel.com>
---
Documentation/devicetree/bindings/rtc/rtc-cmos.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/rtc/rtc-cmos.txt b/Documentation/devicetree/bindings/rtc/rtc-cmos.txt
index b94b35f3600b..fea4fe0ed4b9 100644
--- a/Documentation/devicetree/bindings/rtc/rtc-cmos.txt
+++ b/Documentation/devicetree/bindings/rtc/rtc-cmos.txt
@@ -11,6 +11,9 @@ Optional properties:
called "Register B".
- freq-reg : Contains the initial value of the frequency register also
called "Regsiter A".
+ - status: indicates the operational status of the device.
+ Value must be either "disabled" or "okay".
+
"Register A" and "B" are usually initialized by the firmware (BIOS for
instance). If this is not done, it can be performed by the driver.
@@ -24,4 +27,5 @@ ISA Example:
ctrl-reg = <2>;
freq-reg = <0x26>;
reg = <1 0x70 2>;
+ status = "okay";
};
--
2.11.0
next prev parent reply other threads:[~2019-08-22 7:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 7:44 [PATCH v1 0/2] x86/rtc: Add option to skip using RTC Rahul Tanwar
[not found] ` <cover.1566458029.git.rahul.tanwar@linux.intel.com>
2019-08-22 7:44 ` [PATCH v1 1/2] " Rahul Tanwar
2019-08-22 9:02 ` Andy Shevchenko
2019-08-22 9:26 ` Tanwar, Rahul
2019-08-22 13:04 ` Andy Shevchenko
2019-08-23 3:37 ` Tanwar, Rahul
2019-08-23 12:56 ` Andy Shevchenko
2019-08-26 9:01 ` Tanwar, Rahul
2019-08-22 7:44 ` Rahul Tanwar [this message]
2019-08-22 8:56 ` [PATCH v1 2/2] dt-bindings: rtc: Add optional status property Andy Shevchenko
2019-08-22 9:09 ` Alexandre Belloni
2019-08-22 9:38 ` Tanwar, Rahul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1b01287241d49638c43222d32f3ece5a38c95ddf.1566458029.git.rahul.tanwar@linux.intel.com \
--to=rahul.tanwar@linux.intel.com \
--cc=a.zummo@towertech.it \
--cc=alan@linux.intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andriy.shevchenko@intel.com \
--cc=bp@alien8.de \
--cc=cheol.yong.kim@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=qi-ming.wu@intel.com \
--cc=rahul.tanwar@intel.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).