From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Tomas Borquez <tomasborquez13@gmail.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: iio: ad9832: remove platform_data support
Date: Thu, 4 Dec 2025 21:08:29 +0200 [thread overview]
Message-ID: <CAHp75Vd-qJwBAg-LuCa-iyDoHm5Tar46AV3tOYpR4dS9bZ6Grw@mail.gmail.com> (raw)
In-Reply-To: <20251204185434.4542-1-tomasborquez13@gmail.com>
On Thu, Dec 4, 2025 at 8:55 PM Tomas Borquez <tomasborquez13@gmail.com> wrote:
>
> Remove legacy platform_data support as there are no in tree users and
> this approach belongs to a long gone era. The policy decision on what
> to output is a userspace problem, not something that should be provided
> from firmware.
>
> The driver now initializes the device to a safe state (SLEEP|RESET|CLR)
> outputting nothing. Userspace can configure the desired frequencies and
> phases via the existing sysfs attributes once the device is ready to be
> used.
>
> Suggested-by: Jonathan Cameron <jic23@kernel.org>
> Signed-off-by: Tomas Borquez <tomasborquez13@gmail.com>
> ---
> Original discussion:
> https://lore.kernel.org/linux-iio/20250628161040.3d21e2c4@jic23-huawei/
This can be made as Link:
...
Original discussion started here [1].
Link: ... [1]
Suggested-by: ...
SoB: ...
...
Code wise I like and support this change, thanks!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-12-04 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 18:54 [PATCH] staging: iio: ad9832: remove platform_data support Tomas Borquez
2025-12-04 19:08 ` Andy Shevchenko [this message]
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=CAHp75Vd-qJwBAg-LuCa-iyDoHm5Tar46AV3tOYpR4dS9bZ6Grw@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nuno.sa@analog.com \
--cc=tomasborquez13@gmail.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;
as well as URLs for NNTP newsgroup(s).