From: Ruslan Zalata <rz@fabmicro.ru>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.com>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev
Subject: Re: [PATCH v2] hwmon: (sun4i-lradc) Add driver for LRADC found on Allwinner A13/A20 SoC
Date: Tue, 03 May 2022 13:50:39 +0500 [thread overview]
Message-ID: <6009fbef45a8b77caa4fc137093a1e23@fabmicro.ru> (raw)
In-Reply-To: <20220502110010.q7vvdkdpaiz5acjl@houat>
Hi Maxime,
> I guess a better path forward would be to either register an hwmon
> device in the original driver, or convert that driver to iio and use
> iio-hwmon.
My first idea was to add hwmon to sun4i-lradc-keys.c driver. But soon as
I began hacking the driver I quickly realized that it would be a mess
since keyboard and hwmon belong to two different subsystems. Besides we
would need to invent a way to control which way the driver works (new
bindings?). So I decided that a new independent small driver would be a
better solution.
---
Regards,
Ruslan.
Fabmicro, LLC.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-03 8:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220428210906.29527-1-rz@fabmicro.ru>
2022-04-28 21:30 ` [PATCH v2] hwmon: (sun4i-lradc) Add driver for LRADC found on Allwinner A13/A20 SoC Guenter Roeck
2022-04-29 0:28 ` Ruslan Zalata
2022-04-29 5:32 ` Guenter Roeck
2022-04-29 6:03 ` Guenter Roeck
2022-05-02 23:47 ` Ruslan Zalata
2022-04-29 13:24 ` Jonathan Cameron
2022-05-02 23:20 ` Ruslan Zalata
2022-05-02 11:00 ` Maxime Ripard
2022-05-02 11:15 ` Icenowy Zheng
2022-05-02 11:21 ` Maxime Ripard
2022-05-03 2:02 ` Guenter Roeck
2022-05-03 15:26 ` Ruslan Zalata
2022-05-03 16:14 ` Maxime Ripard
2022-05-03 21:37 ` Ruslan Zalata
2022-05-04 14:12 ` Maxime Ripard
2022-05-02 13:31 ` Guenter Roeck
2022-05-02 13:39 ` Maxime Ripard
2022-05-02 16:21 ` Guenter Roeck
2022-05-03 8:50 ` Ruslan Zalata [this message]
2022-05-03 16:07 ` Maxime Ripard
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=6009fbef45a8b77caa4fc137093a1e23@fabmicro.ru \
--to=rz@fabmicro.ru \
--cc=jdelvare@suse.com \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux@roeck-us.net \
--cc=maxime@cerno.tech \
--cc=samuel@sholland.org \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).