From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v5 2/3] iio: adc: Support ROHM BD79112 ADC/GPIO
Date: Tue, 16 Sep 2025 11:04:16 +0300 [thread overview]
Message-ID: <b35bd683-27b9-4a82-8a57-ed5bb1758ece@gmail.com> (raw)
In-Reply-To: <CAHp75Vcwy47iqNYd4Q4A_X+BSLrFrHyqA2E2kcwbshm1badFqQ@mail.gmail.com>
On 16/09/2025 10:39, Andy Shevchenko wrote:
> On Tue, Sep 16, 2025 at 7:48 AM Matti Vaittinen
> <mazziesaccount@gmail.com> wrote:
>> On 15/09/2025 17:12, Andy Shevchenko wrote:
>>> On Mon, Sep 15, 2025 at 10:12:43AM +0300, Matti Vaittinen wrote:
> ...
>
>>>> + devm_spi_optimize_message(dev, spi, &data->read_msg);
>>>
>>> And if it fails?..
>>
>> I am not really sure under what conditions this would fail. Without
>> taking a further look at that - then we just use unoptimized SPI
>> transfers(?). Could warrant a warning print though.
>
> What is the point of having devm_ variant for it if it never fails, please?
I didn't say it never fails. I said that I don't know what can cause the
failure. Because I don't know this, I can't say if it is reasonable to
assume the SPI (or the system in general) are in unusable state making
the failure a show-stopper for this driver.
If the failure is indicating "only" a failure of "optimization" this
call does, then the driver should still be able to do it's job even if
the SPI performance was reduced. Hence aborting the probe might not be
necessary but the driver could proceed - although emitting a warning
should make sense.
Well, I presume failing of the devm_spi_optimize_message() is not likely
to happen if system is working correctly. Thus I'm not against
Jonathan's edit which aborts the probe.
Yours,
-- Matti
next prev parent reply other threads:[~2025-09-16 8:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 7:11 [PATCH v5 0/3] Support ROHM BD79112 ADC Matti Vaittinen
2025-09-15 7:12 ` [PATCH v5 1/3] dt-bindings: iio: adc: ROHM BD79112 ADC/GPIO Matti Vaittinen
2025-09-15 7:12 ` [PATCH v5 2/3] iio: adc: Support " Matti Vaittinen
2025-09-15 14:12 ` Andy Shevchenko
2025-09-15 20:13 ` Jonathan Cameron
2025-09-16 4:52 ` Matti Vaittinen
2025-09-16 7:41 ` Andy Shevchenko
2025-09-16 8:02 ` Jonathan Cameron
2025-09-16 8:14 ` Matti Vaittinen
2025-09-16 15:08 ` David Lechner
2025-09-16 7:32 ` Andy Shevchenko
2025-09-16 4:48 ` Matti Vaittinen
2025-09-16 7:39 ` Andy Shevchenko
2025-09-16 8:04 ` Matti Vaittinen [this message]
2025-09-15 7:12 ` [PATCH v5 3/3] MAINTAINERS: Support ROHM BD79112 ADC 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=b35bd683-27b9-4a82-8a57-ed5bb1758ece@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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