From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jinseob Kim <kimjinseob88@gmail.com>
Cc: jic23@kernel.org, linux-iio@vger.kernel.org,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
linux-kernel@vger.kernel.org, rdunlap@infradead.org,
joshua.crofts1@gmail.com, u.kleine-koenig@baylibre.com,
julianbraha@gmail.com
Subject: Re: [PATCH v9 5/5] iio: osf: add UART IIO driver
Date: Thu, 10 Sep 2026 11:02:53 +0300 [thread overview]
Message-ID: <aqJkLfhV7-tjMeHw@ashevche-desk.local> (raw)
In-Reply-To: <CALMSewLVTiFww7hTBBw8jK+YL0ZC-E7wLx1TrBWUW5Ziutw8ww@mail.gmail.com>
On Wed, Sep 09, 2026 at 10:06:58AM -0500, Jinseob Kim wrote:
> Add the Open Sensor Fusion serdev transport and runtime IIO registration
> from capability reports. Configure UART before enabling vcc, and retain
> early capabilities until the remaining probe setup succeeds.
>
> Use initialized aligned scan storage, pack active channels, and quiesce
> pushes before buffer reconfiguration. Only accepted samples update the
> latest-sample cache used by direct reads.
>
> Include KUnit coverage for cache integrity, scan bytes and timestamps,
> buffer lifetime, and early capability ownership.
Too big to review, should be split to at least 3 patches (rule of thumb:
each patch rarely should go above ~750 LoC).
...
> + baudrate = serdev_device_set_baudrate(serdev, OSF_SERDEV_BAUD);
> + if (baudrate != OSF_SERDEV_BAUD)
> + dev_warn(dev, "requested %u baud, controller set %u\n",
> + OSF_SERDEV_BAUD, baudrate);
dev_warn_probe()
> + serdev_device_set_flow_control(serdev, false);
> +
> + ret = regulator_enable(vcc);
> + if (ret) {
> + dev_err_probe(dev, ret, "failed to enable vcc regulator\n");
> + goto err_close;
> + }
> +
> + ret = devm_add_action_or_reset(dev, osf_serdev_disable_vcc, vcc);
> + if (ret)
> + goto err_close;
Something went wrong. It's supposed to be no goto:s after devm_*().
> +
> + /* No fallible probe steps remain when IIO children become visible. */
> + scoped_guard(mutex, &osf_uart->rx_lock)
> + osf_core_start(&osf_uart->osf);
> +
> + return 0;
> +
> +err_close:
> + serdev_device_close(serdev);
> + osf_stream_reset(&osf_uart->stream);
> + osf_core_unregister_iio(&osf_uart->osf);
> +
> + return ret;
> +}
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-09-10 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 15:03 [PATCH v9 0/5] iio: add Open Sensor Fusion UART support Jinseob Kim
2026-09-09 15:04 ` [PATCH v9 1/5] dt-bindings: iio: add Open Sensor Fusion device Jinseob Kim
2026-09-09 15:05 ` [PATCH v9 2/5] Documentation: iio: add Open Sensor Fusion driver overview Jinseob Kim
2026-09-09 16:02 ` Randy Dunlap
2026-09-09 18:57 ` Kim Jinseob
2026-09-09 15:05 ` [PATCH v9 3/5] iio: osf: add protocol decoding Jinseob Kim
2026-09-09 15:06 ` [PATCH v9 4/5] iio: osf: add authenticated stream parser Jinseob Kim
2026-09-09 15:06 ` [PATCH v9 5/5] iio: osf: add UART IIO driver Jinseob Kim
2026-09-10 8:02 ` Andy Shevchenko [this message]
2026-09-13 21:35 ` [PATCH v9 0/5] iio: add Open Sensor Fusion UART support 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=aqJkLfhV7-tjMeHw@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=julianbraha@gmail.com \
--cc=kimjinseob88@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=rdunlap@infradead.org \
--cc=u.kleine-koenig@baylibre.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
all inboxes | Powered by JetHome®