From: Lee Jones <lee@kernel.org>
To: Manuel Fombuena <fombuena@outlook.com>
Cc: pavel@ucw.cz, corbet@lwn.net, linux-leds@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 3/5] leds: leds-st1202: spacing and proofreading editing
Date: Tue, 11 Feb 2025 13:34:00 +0000 [thread overview]
Message-ID: <20250211133400.GP1868108@google.com> (raw)
In-Reply-To: <CWLP123MB5473057725D7E085EF6091C2C5EB2@CWLP123MB5473.GBRP123.PROD.OUTLOOK.COM>
On Sat, 01 Feb 2025, Manuel Fombuena wrote:
> Minor edits regarding use of spacing and proofreading.
>
> Signed-off-by: Manuel Fombuena <fombuena@outlook.com>
> ---
> drivers/leds/leds-st1202.c | 48 +++++++++++++++++++-------------------
> 1 file changed, 24 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/leds/leds-st1202.c b/drivers/leds/leds-st1202.c
> index 927874f20839..cb4797ea8f3a 100644
> --- a/drivers/leds/leds-st1202.c
> +++ b/drivers/leds/leds-st1202.c
> @@ -16,27 +16,27 @@
> #include <linux/slab.h>
> #include <linux/string.h>
>
> -#define ST1202_CHAN_DISABLE_ALL 0x00
> -#define ST1202_CHAN_ENABLE_HIGH 0x03
> -#define ST1202_CHAN_ENABLE_LOW 0x02
> -#define ST1202_CONFIG_REG 0x04
> +#define ST1202_CHAN_DISABLE_ALL 0x00
> +#define ST1202_CHAN_ENABLE_HIGH 0x03
> +#define ST1202_CHAN_ENABLE_LOW 0x02
> +#define ST1202_CONFIG_REG 0x04
> /* PATS: Pattern sequence feature enable */
> -#define ST1202_CONFIG_REG_PATS BIT(7)
> +#define ST1202_CONFIG_REG_PATS BIT(7)
> /* PATSR: Pattern sequence runs (self-clear when sequence is finished) */
> -#define ST1202_CONFIG_REG_PATSR BIT(6)
> -#define ST1202_CONFIG_REG_SHFT BIT(3)
> -#define ST1202_DEV_ENABLE 0x01
> -#define ST1202_DEV_ENABLE_ON BIT(0)
> -#define ST1202_DEV_ENABLE_RESET BIT(7)
> -#define ST1202_DEVICE_ID 0x00
> -#define ST1202_ILED_REG0 0x09
> -#define ST1202_MAX_LEDS 12
> -#define ST1202_MAX_PATTERNS 8
> -#define ST1202_MILLIS_PATTERN_DUR_MAX 5660
> -#define ST1202_MILLIS_PATTERN_DUR_MIN 22
> -#define ST1202_PATTERN_DUR 0x16
> -#define ST1202_PATTERN_PWM 0x1E
> -#define ST1202_PATTERN_REP 0x15
> +#define ST1202_CONFIG_REG_PATSR BIT(6)
> +#define ST1202_CONFIG_REG_SHFT BIT(3)
> +#define ST1202_DEV_ENABLE 0x01
> +#define ST1202_DEV_ENABLE_ON BIT(0)
> +#define ST1202_DEV_ENABLE_RESET BIT(7)
> +#define ST1202_DEVICE_ID 0x00
> +#define ST1202_ILED_REG0 0x09
> +#define ST1202_MAX_LEDS 12
> +#define ST1202_MAX_PATTERNS 8
> +#define ST1202_MILLIS_PATTERN_DUR_MAX 5660
> +#define ST1202_MILLIS_PATTERN_DUR_MIN 22
> +#define ST1202_PATTERN_DUR 0x16
> +#define ST1202_PATTERN_PWM 0x1E
> +#define ST1202_PATTERN_REP 0x15
Why are you making this change?
The spacings went from being okay to too large.
> struct st1202_led {
> struct fwnode_handle *fwnode;
> @@ -99,9 +99,9 @@ static int st1202_pwm_pattern_write(struct st1202_chip *chip, int led_num,
> value_h = (u8)(value >> 8);
>
> /*
> - * Datasheet: Register address low = 1Eh + 2*(xh) + 18h*(yh),
> - * where x is the channel number (led number) in hexadecimal (x = 00h .. 0Bh)
> - * and y is the pattern number in hexadecimal (y = 00h .. 07h)
> + * Datasheet: Register address low = 1Eh + 2*(xh) + 18h*(yh),
> + * where x is the channel number (led number) in hexadecimal (x = 00h .. 0Bh)
> + * and y is the pattern number in hexadecimal (y = 00h .. 07h)
> */
> ret = st1202_write_reg(chip, (ST1202_PATTERN_PWM + (led_num * 2) + 0x18 * pattern),
> value_l);
> @@ -288,8 +288,8 @@ static int st1202_setup(struct st1202_chip *chip)
> guard(mutex)(&chip->lock);
>
> /*
> - * Once the supply voltage is applied, the LED1202 executes some internal checks,
> - * afterwords it stops the oscillator and puts the internal LDO in quiescent mode.
> + * Once the supply voltage is applied, the LED1202 executes some internal checks.
> + * Afterwards, it stops the oscillator and puts the internal LDO in quiescent mode.
> * To start the device, EN bit must be set inside the “Device Enable” register at
> * address 01h. As soon as EN is set, the LED1202 loads the adjustment parameters
> * from the internal non-volatile memory and performs an auto-calibration procedure
> --
> 2.48.1
>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-02-11 13:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-01 13:00 [PATCH RESEND 0/5] LED1202 / leds-st1202 fixes and improvements Manuel Fombuena
2025-02-01 13:02 ` [PATCH RESEND 1/5] leds: leds-st1202: fix NULL pointer access on race condition Manuel Fombuena
2025-02-11 13:31 ` Lee Jones
2025-02-12 16:28 ` Manuel Fombuena
2025-02-13 10:24 ` Lee Jones
2025-02-13 15:25 ` Manuel Fombuena
2025-02-20 15:01 ` Lee Jones
2025-02-11 13:34 ` Lee Jones
2025-02-12 13:16 ` Manuel Fombuena
2025-02-01 13:04 ` [PATCH RESEND 2/5] leds: leds-st1202: initialize hardware before DT node child operations Manuel Fombuena
2025-02-11 13:32 ` Lee Jones
2025-02-12 15:15 ` Manuel Fombuena
2025-02-01 13:04 ` [PATCH RESEND 3/5] leds: leds-st1202: spacing and proofreading editing Manuel Fombuena
2025-02-11 13:34 ` Lee Jones [this message]
2025-02-12 14:28 ` Manuel Fombuena
2025-02-01 13:05 ` [PATCH RESEND 4/5] leds: Kconfig: leds-st1202: add select for required LEDS_TRIGGER_PATTERN Manuel Fombuena
2025-02-01 13:07 ` [PATCH RESEND 5/5] Documentation: leds: remove .rst extension for leds-st1202 on index Manuel Fombuena
2025-02-13 10:41 ` [PATCH RESEND 0/5] LED1202 / leds-st1202 fixes and improvements Lee Jones
2025-02-13 15:54 ` Manuel Fombuena
2025-02-20 15:03 ` Lee Jones
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=20250211133400.GP1868108@google.com \
--to=lee@kernel.org \
--cc=corbet@lwn.net \
--cc=fombuena@outlook.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).