From: Amitkumar Karwar <akarwar@marvell.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>, "Cathy Luo" <cluo@marvell.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nishant Sarmukadam <nishants@marvell.com>,
Ganapathi Bhat <gbhat@marvell.com>
Subject: RE: [PATCH v3] Bluetooth: hci_uart: Support firmware download for Marvell
Date: Wed, 2 Mar 2016 06:47:50 +0000 [thread overview]
Message-ID: <f04d2664b8c54469a64495cc44445b79@SC-EXCH04.marvell.com> (raw)
In-Reply-To: <20160301215924.6b884508@lxorguk.ukuu.org.uk>
Hi Alan,
> From: One Thousand Gnomes [mailto:gnomes@lxorguk.ukuu.org.uk]
> Sent: Wednesday, March 02, 2016 3:29 AM
> To: Amitkumar Karwar
> Cc: linux-bluetooth@vger.kernel.org; Cathy Luo; linux-
> kernel@vger.kernel.org; Nishant Sarmukadam; Ganapathi Bhat
> Subject: Re: [PATCH v3] Bluetooth: hci_uart: Support firmware download
> for Marvell
>
> O
> > +/* Get standard baud rate, given the speed */ static unsigned int
> > +get_baud_rate(unsigned int speed) {
> > + switch (speed) {
> > + case 9600:
> > + return B9600;
> > + case 19200:
> > + return B19200;
> > + case 38400:
> > + return B38400;
> > + case 57600:
> > + return B57600;
> > + case 115200:
> > + return B115200;
> > + case 230400:
> > + return B230400;
> > + case 460800:
> > + return B460800;
> > + case 921600:
> > + return B921600;
> > + case 2000000:
> > + return B2000000;
> > + case 3000000:
> > + return B3000000;
> > + default:
> > + return -1;
> > + }
> > +}
>
>
> NAK. Please use the existing kernel helpers for this
>
>
> +
> > +/* Set terminal properties */
> > +static int mrvl_set_term_baud(struct tty_struct *tty, unsigned int
> speed,
> > + unsigned char flow_ctl)
> > +{
> > + struct ktermios old_termios = tty->termios;
> > + int baud;
> > +
> > + tty->termios.c_cflag &= ~CBAUD;
> > + baud = get_baud_rate(speed);
> > +
> > + if (baud == -1) {
> > + BT_ERR("Baud rate not supported");
> > + return -1;
> > + }
> > +
> > + tty->termios.c_cflag |= baud;
> > +
>
> This isn't the correct way to do any of this, just do
>
> tty_termios_encode_baud_rate(&tty->termios, speed, speed)
>
>
> > + if (flow_ctl)
> > + tty->termios.c_cflag |= CRTSCTS;
> > + else
> > + tty->termios.c_cflag &= ~CRTSCTS;
> > +
> > + tty->ops->set_termios(tty, &old_termios);
>
> Call the provided kernel helpers that get the locking right.
>
> tty_set_termios(tty, &new_termios);
>
> You should also do your error checking here and see what baud rate was
> actually provided by the hardware (tty_get_baud_rate(tty)) by checking
> the value actually selected by the tty.
>
> > + /* restore uart settings */
> > + new_termios = tty->termios;
> > + tty->termios.c_cflag = old_termios.c_cflag;
> > + tty->ops->set_termios(tty, &new_termios);
> > + clear_bit(HCI_UART_DNLD_FW, &hu->flags);
>
> Again use the proper helpers
>
> > +
> > +set_baud:
> > + ret = mrvl_set_baud(hu);
> > + if (ret)
> > + goto fail;
> > +
> > + mdelay(MRVL_DNLD_DELAY);
>
> Why not msleep() ?
>
> > +
> > + return ret;
> > +fail:
> > + /* restore uart settings */
> > + new_termios = tty->termios;
> > + tty->termios.c_cflag = old_termios.c_cflag;
> > + tty->ops->set_termios(tty, &new_termios);
> > + clear_bit(HCI_UART_DNLD_FW, &hu->flags);
> > +
>
Thanks for review. We will work on these comments.
Regards,
Amitkumar
prev parent reply other threads:[~2016-03-02 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 17:08 Amitkumar Karwar
2016-03-01 17:08 ` [PATCH BlueZ v3] tools/btattach: add marvell support Amitkumar Karwar
2016-03-01 20:58 ` [PATCH v3] Bluetooth: hci_uart: Support firmware download for Marvell kbuild test robot
2016-03-01 21:59 ` One Thousand Gnomes
2016-03-02 6:47 ` Amitkumar Karwar [this message]
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=f04d2664b8c54469a64495cc44445b79@SC-EXCH04.marvell.com \
--to=akarwar@marvell.com \
--cc=cluo@marvell.com \
--cc=gbhat@marvell.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nishants@marvell.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
all inboxes | Powered by JetHome®