From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Johnson CH Chen (陳昭勳)" <JohnsonCH.Chen@moxa.com>
Cc: "Jiri Slaby" <jirislaby@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"Jason Chen (陳兆先)" <Jason.Chen@moxa.com>,
"Victor Yu (游勝義)" <victor.yu@moxa.com>,
"Danny Lin (林政易)" <danny.lin@moxa.com>
Subject: Re: [PATCH] tty: Add MOXA NPort Real TTY Driver
Date: Fri, 7 Aug 2020 11:48:34 +0200 [thread overview]
Message-ID: <20200807094834.GA3069990@kroah.com> (raw)
In-Reply-To: <HK2PR01MB328115306D9656E2E95D85ECFA490@HK2PR01MB3281.apcprd01.prod.exchangelabs.com>
On Fri, Aug 07, 2020 at 09:18:57AM +0000, Johnson CH Chen (陳昭勳) wrote:
> > > + if (info->modem_control & UART_MCR_RTS)
> > > + nd->cmd_buffer[6] = 1;
> > > + else
> > > + nd->cmd_buffer[6] = 0;
> > > +
> > > + if (termio->c_cflag & CRTSCTS) {
> > > + nd->cmd_buffer[7] = 1;
> > > + nd->cmd_buffer[8] = 1;
> > > + } else {
> > > + nd->cmd_buffer[7] = 0;
> > > + nd->cmd_buffer[8] = 0;
> > > + }
> > > +
> > > + if (termio->c_iflag & IXON)
> > > + nd->cmd_buffer[9] = 1;
> > > + else
> > > + nd->cmd_buffer[9] = 0;
> > > +
> > > + if (termio->c_iflag & IXOFF)
> > > + nd->cmd_buffer[10] = 1;
> > > + else
> > > + nd->cmd_buffer[10] = 0;
> >
> > What is this cmd_buffer good for actually? Only to let the user know?
> > Then -- drop it.
>
> Because detailed iterations for cmd_buffer and cmd_rsp with Nport
> server device are regarded proprietary for our company, is it good to
> reveal value of cmd_buffer[] with macros only for upstream this
> driver?
There is nothing "proprietary" for Linux kernel code, sorry. Please
document this properly so we can understand, review, and maintain it
over time correctly.
thanks,
greg k-h
next prev parent reply other threads:[~2020-08-07 9:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 6:24 [PATCH] tty: Add MOXA NPort Real TTY Driver Johnson CH Chen (陳昭勳)
2020-07-14 7:11 ` Greg Kroah-Hartman
2020-07-23 10:54 ` Johnson CH Chen (陳昭勳)
2020-07-14 7:36 ` Greg Kroah-Hartman
2020-07-16 7:19 ` Johnson CH Chen (陳昭勳)
2020-07-16 7:23 ` Greg Kroah-Hartman
2020-07-22 7:04 ` Johnson CH Chen (陳昭勳)
2020-07-22 7:11 ` Greg Kroah-Hartman
2020-07-14 9:34 ` Jiri Slaby
2020-08-07 9:18 ` Johnson CH Chen (陳昭勳)
2020-08-07 9:48 ` Greg Kroah-Hartman [this message]
2020-07-15 8:27 ` kernel test robot
2020-07-15 8:27 ` kernel test robot
2020-07-24 5:32 ` kernel test robot
2020-07-24 5:32 ` kernel test robot
2020-07-28 20:40 ` Pavel Machek
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=20200807094834.GA3069990@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jason.Chen@moxa.com \
--cc=JohnsonCH.Chen@moxa.com \
--cc=danny.lin@moxa.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=victor.yu@moxa.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 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.