Devicetree
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Matti Vaittinen" <mazziesaccount@gmail.com>,
	"Javier Carrasco" <javier.carrasco.cruz@gmail.com>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Rishi Gupta" <gupt21@gmail.com>, "Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] iio: light: veml6030: fix channel type when pushing events
Date: Mon, 18 May 2026 16:22:55 +0100	[thread overview]
Message-ID: <20260518162255.107faee8@jic23-huawei> (raw)
In-Reply-To: <2a0c777d-05ef-4721-b8ed-88297630ea94@baylibre.com>

On Mon, 18 May 2026 09:48:39 -0500
David Lechner <dlechner@baylibre.com> wrote:

> On 5/18/26 8:12 AM, Matti Vaittinen wrote:
> > On 13/05/2026 07:49, Javier Carrasco wrote:  
> >> The events are registered for IIO_LIGHT and not for IIO_INTENSITY.
> >> Use the correct channel type.
> >> This bug was introduced in the first version of the driver.
> >>
> >> When at it, fix minor checkpatch code style warning (alignment).
> >>
> >> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> >> ---
> >>   drivers/iio/light/veml6030.c | 8 +++++---
> >>   1 file changed, 5 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/drivers/iio/light/veml6030.c b/drivers/iio/light/veml6030.c
> >> index 745cf3ad7092..855f052b60c2 100644
> >> --- a/drivers/iio/light/veml6030.c
> >> +++ b/drivers/iio/light/veml6030.c
> >> @@ -871,9 +871,11 @@ static irqreturn_t veml6030_event_handler(int irq, void *private)
> >>       else
> >>           evtdir = IIO_EV_DIR_FALLING;
> >>   -    iio_push_event(indio_dev, IIO_UNMOD_EVENT_CODE(IIO_INTENSITY,
> >> -                    0, IIO_EV_TYPE_THRESH, evtdir),
> >> -                    iio_get_time_ns(indio_dev));
> >> +    iio_push_event(indio_dev, IIO_UNMOD_EVENT_CODE(IIO_LIGHT,
> >> +                               0,
> >> +                               IIO_EV_TYPE_THRESH,
> >> +                               evtdir),
> >> +            iio_get_time_ns(indio_dev));
> >>         return IRQ_HANDLED;
> >>   }
> >>  
> > 
> > Is this change reflected to the user-space? If so, is it safe? We shouldn't break the ABI, right?  
> 
> On things like this, we will sometime risk breaking userspace in hopes
> that no one was actually depending on it. If no one notices that we
> broke it, did we really break it?

If it's a bug we often just break ABI compatibility anyway.  If we get a report
we'll make it spit out both events (and someone doesn't handle an extra one
we point them at the docs - that hopefully exist ;) - that say you must handle
ones you don't expect).

J
> 
> > 
> > 
> > Yours,
> >     -- Matti
> > 
> > ---
> > Matti Vaittinen
> > Linux kernel developer at ROHM Semiconductors
> > Oulu Finland
> > 
> > ~~ When things go utterly wrong vim users can always type :help! ~~  
> 


  reply	other threads:[~2026-05-18 15:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13  4:49 [PATCH v2 0/4] iio: light: add support for veml6031x00 ALS series Javier Carrasco
2026-05-13  4:49 ` [PATCH v2 1/4] iio: light: veml6030: remove unnecessary read of IT index Javier Carrasco
2026-05-13 16:59   ` Andy Shevchenko
2026-05-13 18:17     ` Javier Carrasco
2026-05-13 19:58       ` Andy Shevchenko
2026-05-16 13:04         ` Jonathan Cameron
2026-05-14  7:54   ` sashiko-bot
2026-05-13  4:49 ` [PATCH v2 2/4] iio: light: veml6030: fix channel type when pushing events Javier Carrasco
2026-05-13 17:48   ` Andy Shevchenko
2026-05-13 18:13     ` Javier Carrasco
2026-05-13 20:02       ` Andy Shevchenko
2026-05-13 20:44         ` Javier Carrasco
2026-05-13 20:56           ` Andy Shevchenko
2026-05-14  8:08   ` sashiko-bot
2026-05-18 13:12   ` Matti Vaittinen
2026-05-18 14:48     ` David Lechner
2026-05-18 15:22       ` Jonathan Cameron [this message]
2026-05-19  6:24         ` Matti Vaittinen
2026-05-13  4:49 ` [PATCH v2 3/4] dt-bindings: iio: light: veml6030: add veml6031x00 ALS series Javier Carrasco
2026-05-13  4:49 ` [PATCH v2 4/4] iio: light: add support for " Javier Carrasco
     [not found]   ` <690B63AD-4429-4045-B413-29911ED7DA3D@gmail.com>
2026-05-13 16:36     ` Andy Shevchenko
2026-05-13 16:37       ` Andy Shevchenko
2026-05-13 16:56   ` Andy Shevchenko
2026-05-13 18:23     ` Javier Carrasco
2026-05-13 20:08       ` Andy Shevchenko
2026-05-16 13:11     ` Jonathan Cameron
2026-05-14  9:29   ` sashiko-bot
2026-05-16 14:41   ` Jonathan Cameron
2026-05-18 13:32   ` Matti Vaittinen

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=20260518162255.107faee8@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=gupt21@gmail.com \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mazziesaccount@gmail.com \
    --cc=nuno.sa@analog.com \
    --cc=robh@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