From: Shreeya Patel <shreeya.patel@collabora.com>
To: jic23@kernel.org, lars@metafoo.de, robh+dt@kernel.org,
Zhigang.Shi@liteon.com, krisman@collabora.com
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@collabora.com,
alvaro.soliverez@collabora.com,
Shreeya Patel <shreeya.patel@collabora.com>
Subject: [PATCH 0/3] Add LTRF216A Driver
Date: Fri, 25 Mar 2022 16:00:11 +0530 [thread overview]
Message-ID: <20220325103014.6597-1-shreeya.patel@collabora.com> (raw)
This patchset adds support for ltrf216a Ambient Light Sensor
and documents the DT bindings for the same.
Shreeya Patel (3):
dt-bindings: vendor-prefixes: Add 'ltr' as deprecated vendor prefix
dt-bindings: Document ltrf216a light sensor bindings
iio: light: Add support for ltrf216a sensor
.../bindings/iio/light/liteon,ltrf216a.yaml | 42 +++
.../devicetree/bindings/vendor-prefixes.yaml | 3 +
drivers/iio/light/Kconfig | 10 +
drivers/iio/light/Makefile | 1 +
drivers/iio/light/ltrf216a.c | 334 ++++++++++++++++++
5 files changed, 390 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/light/liteon,ltrf216a.yaml
create mode 100644 drivers/iio/light/ltrf216a.c
--
2.30.2
next reply other threads:[~2022-03-25 10:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 10:30 Shreeya Patel [this message]
2022-03-25 10:30 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add 'ltr' as deprecated vendor prefix Shreeya Patel
2022-03-25 12:21 ` Krzysztof Kozlowski
2022-03-25 10:30 ` [PATCH 2/3] dt-bindings: Document ltrf216a light sensor bindings Shreeya Patel
2022-03-25 12:23 ` Krzysztof Kozlowski
2022-03-27 13:55 ` Jonathan Cameron
2022-03-28 2:49 ` Gabriel Krisman Bertazi
2022-03-25 10:30 ` [PATCH 3/3] iio: light: Add support for ltrf216a sensor Shreeya Patel
2022-03-25 12:25 ` Krzysztof Kozlowski
2022-03-27 14:30 ` Jonathan Cameron
2022-03-29 20:03 ` Shreeya Patel
2022-04-02 16:49 ` Jonathan Cameron
2022-04-11 17:06 ` Shreeya Patel
2022-04-12 14:06 ` Gabriel Krisman Bertazi
2022-04-12 14:53 ` Jonathan Cameron
2022-03-28 3:59 ` Gabriel Krisman Bertazi
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=20220325103014.6597-1-shreeya.patel@collabora.com \
--to=shreeya.patel@collabora.com \
--cc=Zhigang.Shi@liteon.com \
--cc=alvaro.soliverez@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).