From: Lee Jones <lee@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: Anjelique Melendez <quic_amelende@quicinc.com>,
pavel@ucw.cz, robh@kernel.org, u.kleine-koenig@pengutronix.de,
marijn.suijten@somainline.org, kees@kernel.org,
morf3089@gmail.com, quic_gurus@quicinc.com,
quic_subbaram@quicinc.com, linux-arm-msm@vger.kernel.org,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] leds: rgb: leds-qcom-lpg: Fix line wrapping style issues
Date: Thu, 13 Jun 2024 17:53:29 +0100 [thread overview]
Message-ID: <20240613165329.GP2561462@google.com> (raw)
In-Reply-To: <mummt6hl5c4iih6dvc5qcg6uijkluareqmjbxcfyfyzvhadpcd@oswmwaecv5ic>
On Fri, 07 Jun 2024, Bjorn Andersson wrote:
> On Thu, Jun 06, 2024 at 05:52:52PM GMT, Anjelique Melendez wrote:
> > Fix line wrapping style issues introduced in previous patches.
>
> Bending the line length guidelines is okay when it results in easier to
> read code. I find the existing code easier to read...
Agree. This patch is not going to be accepted.
> > Signed-off-by: Anjelique Melendez <quic_amelende@quicinc.com>
> > ---
> > drivers/leds/rgb/leds-qcom-lpg.c | 19 +++++++++++++------
> > 1 file changed, 13 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/leds/rgb/leds-qcom-lpg.c b/drivers/leds/rgb/leds-qcom-lpg.c
> > index e74b2ceed1c2..7c35b3ba09a3 100644
> > --- a/drivers/leds/rgb/leds-qcom-lpg.c
> > +++ b/drivers/leds/rgb/leds-qcom-lpg.c
> > @@ -620,6 +620,7 @@ static void lpg_sdam_apply_lut_control(struct lpg_channel *chan)
> > u8 val = 0, conf = 0, lut_offset = 0;
> > unsigned int hi_pause, lo_pause;
> > struct lpg *lpg = chan->lpg;
> > + u16 addr;
> >
> > if (!chan->ramp_enabled || chan->pattern_lo_idx == chan->pattern_hi_idx)
> > return;
> > @@ -640,17 +641,23 @@ static void lpg_sdam_apply_lut_control(struct lpg_channel *chan)
> > lo_idx += lut_offset;
> > }
> >
> > - nvmem_device_write(lpg_chan_sdam, SDAM_PBS_SCRATCH_LUT_COUNTER_OFFSET + chan->sdam_offset, 1, &val);
> > - nvmem_device_write(lpg_chan_sdam, SDAM_PATTERN_CONFIG_OFFSET + chan->sdam_offset, 1, &conf);
> > - nvmem_device_write(lpg_chan_sdam, SDAM_END_INDEX_OFFSET + chan->sdam_offset, 1, &hi_idx);
> > - nvmem_device_write(lpg_chan_sdam, SDAM_START_INDEX_OFFSET + chan->sdam_offset, 1, &lo_idx);
> > + addr = SDAM_PBS_SCRATCH_LUT_COUNTER_OFFSET + chan->sdam_offset;
> > + nvmem_device_write(lpg_chan_sdam, addr, 1, &val);
> > + addr = SDAM_PATTERN_CONFIG_OFFSET + chan->sdam_offset;
> > + nvmem_device_write(lpg_chan_sdam, addr, 1, &conf);
> > + addr = SDAM_END_INDEX_OFFSET + chan->sdam_offset;
> > + nvmem_device_write(lpg_chan_sdam, addr, 1, &hi_idx);
> > + addr = SDAM_START_INDEX_OFFSET + chan->sdam_offset;
> > + nvmem_device_write(lpg_chan_sdam, addr, 1, &lo_idx);
> >
> > val = RAMP_STEP_DURATION(chan->ramp_tick_ms);
> > nvmem_device_write(lpg_chan_sdam, SDAM_REG_RAMP_STEP_DURATION, 1, &val);
> >
> > if (lpg->lut_sdam) {
> > - nvmem_device_write(lpg_chan_sdam, SDAM_PAUSE_HI_MULTIPLIER_OFFSET + chan->sdam_offset, 1, &hi_pause);
> > - nvmem_device_write(lpg_chan_sdam, SDAM_PAUSE_LO_MULTIPLIER_OFFSET + chan->sdam_offset, 1, &lo_pause);
> > + addr = SDAM_PAUSE_HI_MULTIPLIER_OFFSET + chan->sdam_offset;
> > + nvmem_device_write(lpg_chan_sdam, addr, 1, &hi_pause);
> > + addr = SDAM_PAUSE_LO_MULTIPLIER_OFFSET + chan->sdam_offset;
> > + nvmem_device_write(lpg_chan_sdam, addr, 1, &lo_pause);
> > }
> >
> > }
> > --
> > 2.34.1
> >
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-06-13 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 0:52 [PATCH 1/2] leds: rgb: leds-qcom-lpg: Add PPG check for setting/clearing PBS triggers Anjelique Melendez
2024-06-07 0:52 ` [PATCH 2/2] leds: rgb: leds-qcom-lpg: Fix line wrapping style issues Anjelique Melendez
2024-06-07 11:55 ` Dmitry Baryshkov
2024-06-07 18:56 ` Bjorn Andersson
2024-06-13 16:53 ` Lee Jones [this message]
2024-06-07 23:03 ` [PATCH 1/2] leds: rgb: leds-qcom-lpg: Add PPG check for setting/clearing PBS triggers Bjorn Andersson
2024-06-13 16:54 ` (subset) " 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=20240613165329.GP2561462@google.com \
--to=lee@kernel.org \
--cc=andersson@kernel.org \
--cc=kees@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=morf3089@gmail.com \
--cc=pavel@ucw.cz \
--cc=quic_amelende@quicinc.com \
--cc=quic_gurus@quicinc.com \
--cc=quic_subbaram@quicinc.com \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.