From: Tung Pham <Tung.Pham@silabs.com>
To: Johan Hovold <johan@kernel.org>
Cc: Pho Tran <photranvan0712@gmail.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Hung Nguyen <Hung.Nguyen@silabs.com>,
Pho Tran <Pho.Tran@silabs.com>
Subject: RE: [PATCH v12] USB: serial: cp210x: Add support for GPIOs on CP2108
Date: Wed, 9 Jun 2021 03:06:16 +0000 [thread overview]
Message-ID: <CO1PR11MB488295663735895484C264CF81369@CO1PR11MB4882.namprd11.prod.outlook.com> (raw)
In-Reply-To: <YKdqKDj/Qbw4k5IA@hovoldconsulting.com>
> On Tue, May 18, 2021 at 03:18:06AM +0000, Tung Pham wrote:
> > Do you agree and approve with this path?.
>
> > I'm still waiting for you to confirm that you have tested the patch
> > with different pin configurations in eeprom.
> -> we have tested pass the GPIO of cp2108:
> Case1: all 16 GPIO are configured as GPIO function.
> Case2: all 16 GPIO are configured as alternative functions (not GPIO).
> Please see attached file for more detail.
> Excellent, thanks for confirming. I'll try to review the latest revision shortly.
> Johan
Thanks for your effort to reviewing our code.
What about status of this patch?.
Thanks.
next prev parent reply other threads:[~2021-06-09 3:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 3:18 [PATCH v12] USB: serial: cp210x: Add support for GPIOs on CP2108 Tung Pham
2021-05-18 7:04 ` Johan Hovold
2021-05-20 15:11 ` Tung Pham
2021-05-21 8:07 ` Johan Hovold
2021-06-09 3:06 ` Tung Pham [this message]
2021-06-09 7:33 ` Johan Hovold
-- strict thread matches above, loose matches on Subject: below --
2021-04-26 9:12 tu pham
2021-06-10 13:26 ` Johan Hovold
2021-06-13 9:45 ` Tung Pham
2021-06-16 14:38 ` 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=CO1PR11MB488295663735895484C264CF81369@CO1PR11MB4882.namprd11.prod.outlook.com \
--to=tung.pham@silabs.com \
--cc=Hung.Nguyen@silabs.com \
--cc=Pho.Tran@silabs.com \
--cc=gregkh@linuxfoundation.org \
--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).