From: Lee Jones <lee@kernel.org>
To: Anjelique Melendez <quic_amelende@quicinc.com>
Cc: pavel@ucw.cz, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, andersson@kernel.org,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_c_skakit@quicinc.com
Subject: Re: [PATCH 0/3] Add support for high resolution PWMs
Date: Thu, 30 Mar 2023 14:01:05 +0100 [thread overview]
Message-ID: <20230330130105.GO434339@google.com> (raw)
In-Reply-To: <20230316192134.26436-1-quic_amelende@quicinc.com>
On Thu, 16 Mar 2023, Anjelique Melendez wrote:
> Certain PMICs have a high reolution PWM module which can support from 8-bit
> to 15-bit PWM. This change series adds support for those PMICs. Thanks!
>
> Anjelique Melendez (3):
> dt-bindings: leds-qcom-lpg: Add qcom,pmk8550-pwm compatible string
> leds: rgb: leds-qcom-lpg: Add support for high resolution PWM
> leds: rgb: leds-qcom-lpg: Add support for PMK8550 PWM
>
> .../bindings/leds/leds-qcom-lpg.yaml | 1 +
> drivers/leds/rgb/leds-qcom-lpg.c | 151 +++++++++++++-----
> 2 files changed, 110 insertions(+), 42 deletions(-)
I guess you'll be fixing the build issues and resubmitting?
Please retrain the Acks you've collected.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2023-03-30 13:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 19:21 [PATCH 0/3] Add support for high resolution PWMs Anjelique Melendez
2023-03-16 19:21 ` [PATCH 1/3] dt-bindings: leds-qcom-lpg: Add qcom,pmk8550-pwm compatible string Anjelique Melendez
2023-03-17 16:04 ` Krzysztof Kozlowski
2023-03-16 19:21 ` [PATCH 2/3] leds: rgb: leds-qcom-lpg: Add support for high resolution PWM Anjelique Melendez
2023-03-17 11:18 ` kernel test robot
2023-03-17 15:54 ` kernel test robot
2023-03-23 19:49 ` Pavel Machek
2023-03-16 19:21 ` [PATCH 3/3] leds: rgb: leds-qcom-lpg: Add support for PMK8550 PWM Anjelique Melendez
2023-03-30 13:01 ` Lee Jones [this message]
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=20230330130105.GO434339@google.com \
--to=lee@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=quic_amelende@quicinc.com \
--cc=quic_c_skakit@quicinc.com \
--cc=robh+dt@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).