From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Johan Hovold <johan@kernel.org>
Cc: Pho Tran <photranvan0712@gmail.com>,
Hung.Nguyen@silabs.com, Tung.Pham@silabs.com,
USB <linux-usb@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] USB: serial: cp210x: provide gpio valid mask
Date: Fri, 9 Apr 2021 19:23:11 +0300 [thread overview]
Message-ID: <CAHp75Vds=yXk3yYMh1yyDb0o_YyVTh3-6iKh8rYKwYHORebdkQ@mail.gmail.com> (raw)
In-Reply-To: <20210409155216.31867-1-johan@kernel.org>
On Fri, Apr 9, 2021 at 6:52 PM Johan Hovold <johan@kernel.org> wrote:
>
> Use the new GPIO valid-mask feature to inform gpiolib which pins are
> available for use instead of handling that in a request callback.
>
> This also allows user space to figure out which pins are available
> through the chardev interface without having to request each pin in
> turn.
Thanks! I like the series.
Independently on reaction on my comments:
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> Johan
>
>
> Johan Hovold (2):
> USB: serial: cp210x: provide gpio valid mask
> USB: serial: cp210x: add gpio-configuration debug printk
>
> drivers/usb/serial/cp210x.c | 31 +++++++++++++++++++------------
> 1 file changed, 19 insertions(+), 12 deletions(-)
>
> --
> 2.26.3
>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-04-09 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 15:52 [PATCH 0/2] USB: serial: cp210x: provide gpio valid mask Johan Hovold
2021-04-09 15:52 ` [PATCH 1/2] " Johan Hovold
2021-04-09 15:52 ` [PATCH 2/2] USB: serial: cp210x: add gpio-configuration debug printk Johan Hovold
2021-04-09 16:22 ` Andy Shevchenko
2021-04-09 16:32 ` Johan Hovold
2021-04-09 16:23 ` Andy Shevchenko [this message]
2021-04-12 10:00 ` [PATCH 0/2] USB: serial: cp210x: provide gpio valid mask Johan Hovold
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='CAHp75Vds=yXk3yYMh1yyDb0o_YyVTh3-6iKh8rYKwYHORebdkQ@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=Hung.Nguyen@silabs.com \
--cc=Tung.Pham@silabs.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=photranvan0712@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).