From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux MediaTek <linux-mediatek@lists.infradead.org>,
Linux LEDs <linux-leds@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
ChiaEn Wu <chiaen_wu@richtek.com>, Lee Jones <lee@kernel.org>,
ChiYuan Huang <cy_huang@richtek.com>,
kernel test robot <lkp@intel.com>
Subject: [PATCH 3/3] Documentation: leds: MT6370: Use bullet lists for timing variables
Date: Sun, 19 Mar 2023 14:49:03 +0700 [thread overview]
Message-ID: <20230319074903.13075-4-bagasdotme@gmail.com> (raw)
In-Reply-To: <20230319074903.13075-1-bagasdotme@gmail.com>
The timing description contains list of timing pattern variables, but it
uses code block without indentation instead. Switch to bullet list as it
is better fit for this purpose.
While at it, substitute "load" for "duty" because the variables control
timing for current load into the device.
Link: https://lore.kernel.org/oe-kbuild-all/202303182310.tB1mUzU7-lkp@intel.com/
Fixes: 4ba9df04b7ac66 ("docs: leds: Add MT6370 RGB LED pattern document")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/leds/leds-mt6370-rgb.rst | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/Documentation/leds/leds-mt6370-rgb.rst b/Documentation/leds/leds-mt6370-rgb.rst
index ea782797a06df0..152a2e5921724b 100644
--- a/Documentation/leds/leds-mt6370-rgb.rst
+++ b/Documentation/leds/leds-mt6370-rgb.rst
@@ -45,17 +45,17 @@ Pattern diagram::
+----------------------------------============------------> Time
< Tr1><Tr2>< Ton ><Tf1><Tf2 >< Toff >< Tr1><Tr2>
-Timing description::
+Timing description:
-Tr1: First rising time for duty 0 to 30%.
-Tr2: Second rising time for duty 31% to 100%.
-Ton: On time for duty 100%.
-Tf1: First falling time for duty 100% to 31%.
-Tf2: Second falling time for duty 30% to 0%.
-Toff: Off time for duty 0%.
+ * Tr1: First rising time for 0% - 30% load.
+ * Tr2: Second rising time for 31% - 100% load.
+ * Ton: On time for 100% load.
+ * Tf1: First falling time for 100% - 31% load.
+ * Tf2: Second falling time for 30% to 0% load.
+ * Toff: Off time for 0% load.
-Tr1/Tr2/Tf1/Tf2/Ton: 125ms to 3125ms, 200ms per step.
-Toff: 250ms to 6250ms, 400ms per step.
+ * Tr1/Tr2/Tf1/Tf2/Ton: 125ms to 3125ms, 200ms per step.
+ * Toff: 250ms to 6250ms, 400ms per step.
Pattern example::
--
An old man doll... just what I always wanted! - Clara
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-19 7:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 7:49 [PATCH 0/3] Documentation fixes for MT6370 RGB Bagas Sanjaya
2023-03-19 7:49 ` [PATCH 1/3] Documentation: leds: Add MT6370 doc to the toctree Bagas Sanjaya
2023-03-23 15:16 ` Lee Jones
2023-03-19 7:49 ` [PATCH 2/3] Documentation: leds: MT6370: Properly wrap hw_pattern chart Bagas Sanjaya
2023-03-23 15:17 ` Lee Jones
2023-03-19 7:49 ` Bagas Sanjaya [this message]
2023-03-23 15:18 ` [PATCH 3/3] Documentation: leds: MT6370: Use bullet lists for timing variables Lee Jones
2023-03-23 5:06 ` [PATCH 0/3] Documentation fixes for MT6370 RGB Bagas Sanjaya
2023-03-23 12:31 ` Lee Jones
2023-03-23 12:35 ` Bagas Sanjaya
2023-03-23 11:08 ` Pavel Machek
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=20230319074903.13075-4-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chiaen_wu@richtek.com \
--cc=corbet@lwn.net \
--cc=cy_huang@richtek.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lkp@intel.com \
--cc=matthias.bgg@gmail.com \
--cc=skhan@linuxfoundation.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).