[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b682cf05-2d96-d7e4-6f86-b1776d16b132@linaro.org>
Date: Thu, 20 Oct 2022 08:00:28 -0400
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Mitja Špes <mitja@...av.com>
Cc: linux-iio@...r.kernel.org, Jonathan Cameron <jic23@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>,
Rob Herring <robh+dt@...nel.org>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Tomasz Duszynski <tduszyns@...il.com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] doc: iio: pressure: ms5611: added max SPI frequency
setting to the example
On 20/10/2022 01:40, Mitja Špes wrote:
> On Wed, Oct 19, 2022 at 5:49 PM Krzysztof Kozlowski
> <krzysztof.kozlowski@...aro.org> wrote:
>
>> Use subject prefixes matching the subsystem (git log --oneline -- ...).
>
> Will do.
>
>> Whether it is honored by driver it matters less. More important is how
>> hardware can handle it. This should be included in the bindings/properties.
>
> The hardware handles frequencies up to 20MHz. That constraint is already
> written in meas,ms5611.yaml.
> What my patch 2 does is allow the user to set a lower frequency and the patch
> 3 just emphasises that in the example.
Then I am not sure whether it is worth changing. This is just an
example. Old value is correct.
Best regards,
Krzysztof
Powered by blists - more mailing lists