From: rishi gupta <gupt21@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: knaack.h@gmx.de, lars@metafoo.de,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
gregkh@linuxfoundation.org, tglx@linutronix.de,
allison@lohutok.net, alexios.zavras@intel.com, angus@akkea.ca,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
hslester96@gmail.com, wsa+renesas@sang-engineering.com
Subject: Re: [RESEND PATCH v2 0/3] Add driver for veml6030 ambient light sensor
Date: Mon, 21 Oct 2019 19:07:10 +0530 [thread overview]
Message-ID: <CALUj-gsKph=5V52=aV+dsgKaELinHGEPBe+E+QGZF+8-CnCPTw@mail.gmail.com> (raw)
In-Reply-To: <20191005150838.542b0219@archlinux>
My email server returned error so I was confused whether all patches
reached to mailing list intact or not, that is why I resent.
Regards,
Rishi
On Sat, Oct 5, 2019 at 7:38 PM Jonathan Cameron <jic23@kernel.org> wrote:
>
> On Tue, 24 Sep 2019 16:21:55 +0530
> Rishi Gupta <gupt21@gmail.com> wrote:
>
> When doing a RESEND as opposed to a new version, please say
> why.
>
> > The veml6030 is an ambient light sensor from vishay and
> > is a different hardware from an existing hardware for which
> > driver currently exist, therefore this driver submission.
> >
> > * All features; ALS, white channel & power management is
> > supported.
> >
> > * All configurable parameters are supported through standard
> > iio sysfs entries. User space can get valid values of any
> > parameter (xx_available) and then can write to appropriate
> > sysfs entry.
> >
> > * User space can get ALS & White channel readings through RAW
> > IIO interface.
> >
> > * IIO events are used to notify application whenever threshold
> > is crossed. This uses IRQ pin of veml6030.
> >
> > * Some registers in veml6030 are read only. For these registers
> > read callback returns error to user space.
> >
> > There are 3 patches for this submission:
> > [PATCH 1/3] iio: light: add driver for veml6030 ambient light sensor
> > [PATCH 2/3] dt-bindings: iio: light: add veml6030 ALS bindings
> > [PATCH 3/3] iio: documentation: light: Add veml6030 sysfs documentation
> >
> > Rishi Gupta (3):
> > iio: light: add driver for veml6030 ambient light sensor
> > dt-bindings: iio: light: add veml6030 ALS bindings
> > iio: documentation: light: Add veml6030 sysfs documentation
> >
> > .../ABI/testing/sysfs-bus-iio-light-veml6030 | 49 ++
> > .../devicetree/bindings/iio/light/veml6030.yaml | 62 ++
> > drivers/iio/light/Kconfig | 11 +
> > drivers/iio/light/Makefile | 1 +
> > drivers/iio/light/veml6030.c | 633 +++++++++++++++++++++
> > 5 files changed, 756 insertions(+)
> > create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-light-veml6030
> > create mode 100644 Documentation/devicetree/bindings/iio/light/veml6030.yaml
> > create mode 100644 drivers/iio/light/veml6030.c
> >
>
prev parent reply other threads:[~2019-10-21 13:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 10:51 [RESEND PATCH v2 0/3] Add driver for veml6030 ambient light sensor Rishi Gupta
2019-09-24 10:51 ` [RESEND PATCH v2 1/3] iio: light: add " Rishi Gupta
2019-10-05 14:08 ` Jonathan Cameron
2019-10-21 13:28 ` [PATCH v3 " Rishi Gupta
2019-10-22 3:57 ` [PATCH v4 " Rishi Gupta
2019-10-22 10:00 ` Jonathan Cameron
2019-10-22 12:32 ` rishi gupta
2019-10-27 9:26 ` Jonathan Cameron
2019-09-24 10:51 ` [RESEND PATCH v2 2/3] dt-bindings: iio: light: add veml6030 ALS bindings Rishi Gupta
2019-10-05 14:14 ` Jonathan Cameron
2019-10-21 13:31 ` [PATCH v3 " Rishi Gupta
2019-10-21 17:28 ` Rob Herring
2019-10-22 3:57 ` [PATCH v4 " Rishi Gupta
2019-09-24 10:51 ` [RESEND PATCH v2 3/3] iio: documentation: light: Add veml6030 sysfs documentation Rishi Gupta
2019-10-05 14:11 ` Jonathan Cameron
2019-10-21 13:31 ` [PATCH v3 " Rishi Gupta
2019-10-22 3:58 ` [PATCH v4 " Rishi Gupta
2019-10-22 9:48 ` Jonathan Cameron
2019-10-05 14:08 ` [RESEND PATCH v2 0/3] Add driver for veml6030 ambient light sensor Jonathan Cameron
2019-10-21 13:37 ` rishi gupta [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='CALUj-gsKph=5V52=aV+dsgKaELinHGEPBe+E+QGZF+8-CnCPTw@mail.gmail.com' \
--to=gupt21@gmail.com \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=angus@akkea.ca \
--cc=gregkh@linuxfoundation.org \
--cc=hslester96@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=tglx@linutronix.de \
--cc=wsa+renesas@sang-engineering.com \
/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).