linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Charles Yeh <charlesyeh522@gmail.com>
Cc: "Johan Hovold" <johan@kernel.org>,
	"Greg KH" <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org,
	"Yeh.Charles [葉榮鑫]" <charles-yeh@prolific.com.tw>
Subject: Re: [PATCH] [PATCH v6] USB: serial: pl2303: Add new PID to support PL2303HXN (TYPE_HXN)
Date: Tue, 16 Jul 2019 10:33:12 +0200	[thread overview]
Message-ID: <20190716083312.GA10939@localhost> (raw)
In-Reply-To: <CAAZvQQ6JDgkC2SD4eYzBVYhq3ApMwWc_-gXQQVMBH+CaXZSK5A@mail.gmail.com>

[ Please do not top post, reply inline and trim irrelevant context.
  Specifically do not copy context to the top of the mail.

  Reordering your reply below. ]

On Wed, Jul 03, 2019 at 12:22:45AM +0800, Charles Yeh wrote:
> Johan Hovold <johan@kernel.org> 於 2019年7月1日 週一 下午11:29寫道:
> > On Mon, Jul 01, 2019 at 11:11:02PM +0800, Charles Yeh wrote:

> > > >         } else if (spriv->type == &pl2303_type_data[TYPE_HXN]) {
> > > > > +                     pl2303_vendor_write(serial, PL2303_HXN_RESET_CONTROL,
> > > > > +                             0);
> > > >
> > > > You again completely ignored my question about why you're wring 0
> > > > instead of 3 here.
> > > >
> > > > I'll ignore your patch until you explain.
> > >
> > > 3. In pl2303_open: Because TYPE_HXN is different from the instruction of reset
> > >    down/up stream used by TYPE_HX.
> > >    Therefore, we will also execute different instructions here.
> > >    The default of chip Reset Control is 0xFF(TYPE_HXN), therefore we will
> > >    write 0x00 to reset down/up stream(TYPE_HXN).
> >
> > I'm asking why you write the value 0 instead of 3 (or say, 0xfc)? Your
> > documentation said bit 0 and 1 are used to reset the up and downstream
> > pipes.
> >
> > To be more specific; what happens if I
> >
> >         1. set bit 0
> >         2. clear bit 0?
> >
> > and leave the other bits alone (write back the same value, e.g. 0xfe).

> You are right..
> set "1" is reset.
> set "0" is nothing.
> 
> I have used pl2303_update_reg instead pl2303_vendor_write which to reset
> the upstream and downstream pipe data

Ok, thanks for confirming. Note that I asked you about this back in
April (15 April).

In that very same mail thread I also pointed out that you must not
ignore review feedback. Even if for some reason disagree with it you
should at least explain why.

Johan

  reply	other threads:[~2019-07-16  8:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 12:21 [PATCH] [PATCH v6] USB: serial: pl2303: Add new PID to support PL2303HXN (TYPE_HXN) Charles Yeh
2019-07-01 13:32 ` Johan Hovold
2019-07-01 13:35   ` Johan Hovold
2019-07-01 15:11   ` Charles Yeh
2019-07-01 15:29     ` Johan Hovold
2019-07-02 16:22       ` Charles Yeh
2019-07-16  8:33         ` Johan Hovold [this message]
2019-07-16 10:42           ` Charles Yeh
2019-08-27  7:07           ` Charles Yeh

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=20190716083312.GA10939@localhost \
    --to=johan@kernel.org \
    --cc=charles-yeh@prolific.com.tw \
    --cc=charlesyeh522@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.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).