devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Matti Vaittinen <mazziesaccount@gmail.com>,
	Alexander Stein <alexander.stein@ew.tq-group.com>,
	Andre Werner <andre.werner@systec-electronic.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Conor Dooley <conor+dt@kernel.org>,
	Fabio Estevam <festevam@denx.de>,
	Guenter Roeck <linux@roeck-us.net>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Luca Ceresoli <luca.ceresoli@bootlin.com>,
	Mark Brown <broonie@kernel.org>,
	Naresh Solanki <naresh.solanki@9elements.com>,
	Patrick Rudolph <patrick.rudolph@9elements.com>,
	Rob Herring <robh+dt@kernel.org>,
	Stefan Windfeldt-Prytz <stefan.windfeldt-prytz@axis.com>,
	Vincent Tremblay <vincent@vtremblay.dev>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v6 2/2] iio: light: isl76682: Add ISL76682 driver
Date: Thu, 7 Dec 2023 14:28:03 +0100	[thread overview]
Message-ID: <a59d6e31-5339-4e13-a5e5-f627206065a6@denx.de> (raw)
In-Reply-To: <20231206172049.3e0ce859@jic23-huawei>

On 12/6/23 18:20, Jonathan Cameron wrote:
> On Tue, 5 Dec 2023 02:24:51 +0100
> Marek Vasut <marex@denx.de> wrote:
> 
>> On 12/4/23 15:35, Jonathan Cameron wrote:
>>> On Mon, 4 Dec 2023 12:23:06 +0100
>>> Marek Vasut <marex@denx.de> wrote:
>>>    
>>>> On 12/4/23 12:20, Jonathan Cameron wrote:
>>>>> On Mon, 27 Nov 2023 22:26:53 +0100
>>>>> Marek Vasut <marex@denx.de> wrote:
>>>>>       
>>>>>> The ISL76682 is very basic ALS which only supports ALS or IR mode
>>>>>> in four ranges, 1k/4k/16k/64k LUX. There is no IRQ support or any
>>>>>> other fancy functionality.
>>>>>>
>>>>>> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>>>>>> Reviewed-by: Matti Vaittinen <mazziesaccount@gmail.com>
>>>>>> Signed-off-by: Marek Vasut <marex@denx.de>
>>>>> Hi Marek,
>>>>>
>>>>> Discussion around available on v5 made me look closer at that aspect.
>>>>> You are providing all the available entries in the callback but they
>>>>> shouldn't be exposed to actually read unless the *_available bitmap
>>>>> bits corresponding to them are set.
>>>>>
>>>>> If you like I can just rip the unused code out whilst applying?
>>>>> Or if you'd prefer to send a v7 that's great too.
>>>>>
>>>>> Otherwise everything looks good to me.
>>>>
>>>> Maybe just do that while applying and I'll test it right after to see
>>>> whether something broke, that's probably fastest. Just let me know where
>>>> this got applied. I have the device on my desk .
>>>
>>> Diff is below.  Applied to the togreg
>>
>> I only found the commit in 'testing' branch , so I used that one .
> I messed up it seems and didn't actually push the updated version.
> Done so now along with squashing in the bracket tidy up.

Driver works just fine, still, thank you.

  reply	other threads:[~2023-12-07 13:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 21:26 [PATCH v6 1/2] dt-bindings: iio: light: isl76682: Document ISL76682 Marek Vasut
2023-11-27 21:26 ` [PATCH v6 2/2] iio: light: isl76682: Add ISL76682 driver Marek Vasut
2023-12-04 11:20   ` Jonathan Cameron
2023-12-04 11:23     ` Marek Vasut
2023-12-04 14:35       ` Jonathan Cameron
2023-12-05  1:24         ` Marek Vasut
2023-12-06 17:20           ` Jonathan Cameron
2023-12-07 13:28             ` Marek Vasut [this message]
2023-12-05  1:26     ` Marek Vasut
2023-12-04 11:29   ` Jonathan Cameron
2023-12-05  1:43     ` Marek Vasut
2023-12-05 15:54       ` Andy Shevchenko
2023-12-05 21:02         ` Marek Vasut
2023-12-05 21:57           ` Andy Shevchenko
2023-12-05 23:11             ` Marek Vasut
2023-12-06 17:23       ` Jonathan Cameron

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=a59d6e31-5339-4e13-a5e5-f627206065a6@denx.de \
    --to=marex@denx.de \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=andre.werner@systec-electronic.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@denx.de \
    --cc=jic23@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=luca.ceresoli@bootlin.com \
    --cc=mazziesaccount@gmail.com \
    --cc=naresh.solanki@9elements.com \
    --cc=patrick.rudolph@9elements.com \
    --cc=robh+dt@kernel.org \
    --cc=stefan.windfeldt-prytz@axis.com \
    --cc=vincent@vtremblay.dev \
    /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).