From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: William Sung <william.sung@advantech.com.tw>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio <linux-iio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
AceLan Kao <acelan.kao@canonical.com>,
Campion Kang <Campion.Kang@advantech.com.tw>
Subject: Re: [PATCH] iio: dac: ad5593r: Dynamically set AD5593R channel modes
Date: Sun, 30 Aug 2020 20:07:09 +0300 [thread overview]
Message-ID: <CAHp75VeZLPR02xB2XRzec5mSBvq93XYZg56OOODxpFTPva6cXw@mail.gmail.com> (raw)
In-Reply-To: <20200824054347.3805-1-william.sung@advantech.com.tw>
On Mon, Aug 24, 2020 at 8:54 AM William Sung
<william.sung@advantech.com.tw> wrote:
>
> To use ad5593r more flexibly, we use the module parameter to setting the
> channel modes dynamically whenever the module probe up.
> Users can pass
> the channel modes to the module parameter for allocating the
> functionality of channels as desired.
NAK. We have a sysfs interface.
> For example:
> * Use in the kernel command line:
> Users can add the module parameter in the kernel command line such as
>
> "ad5593r.ch_mode_cmdline=88001122"
>
> "88001122" means the channel mode setting for each channel. The most
> left side indicates the mode of channel 7, and the most right side
> indicates the mode of channel 0.
>
> * Use when manually probe the module:
> Similar to the kernel command line usage, users can enter
>
> "modprobe ad5593r ch_mode_probe=88001122"
>
> to start the ad5593r module with the desired channel mode setting.
Again NAK, this basically should come from Device Tree or ACPI.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-08-30 17:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 5:43 [PATCH] iio: dac: ad5593r: Dynamically set AD5593R channel modes William Sung
2020-08-25 4:15 ` AceLan Kao
2020-08-30 17:07 ` Andy Shevchenko [this message]
2020-08-31 11:28 ` AceLan Kao
2020-08-31 12:45 ` Andy Shevchenko
2020-08-31 12:47 ` Andy Shevchenko
2020-09-03 7:37 ` AceLan Kao
2020-09-03 10:42 ` Andy Shevchenko
2020-09-03 10:54 ` Andy Shevchenko
2020-09-04 2:25 ` AceLan Kao
2020-09-04 7:40 ` Andy Shevchenko
[not found] ` <b1581dc61d584cffa2588f72b888ffa0@taipei09.ADVANTECH.CORP>
2020-09-04 7:48 ` Andy Shevchenko
[not found] ` <705b481901d64d30830689f0aa541cb9@taipei09.ADVANTECH.CORP>
2020-09-04 11:38 ` Andy Shevchenko
2020-09-04 11:43 ` Andy Shevchenko
2020-09-02 8:09 ` Hennerich, Michael
2020-09-02 8:52 ` Andy Shevchenko
2020-09-02 9:11 ` Hennerich, Michael
2020-09-02 9:28 ` Andy Shevchenko
2020-09-02 13:23 ` 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=CAHp75VeZLPR02xB2XRzec5mSBvq93XYZg56OOODxpFTPva6cXw@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=Campion.Kang@advantech.com.tw \
--cc=Michael.Hennerich@analog.com \
--cc=acelan.kao@canonical.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=william.sung@advantech.com.tw \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.