All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hung <hpeter@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: johan@kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	USB <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	tom_tsai@fintek.com.tw, peter_hong@fintek.com.tw,
	Peter Hung <hpeter+linux_kernel@gmail.com>
Subject: Re: [PATCH V6 1/1] usb:serial: Add Fintek F81532/534 driver
Date: Wed, 4 Nov 2015 16:41:54 +0800	[thread overview]
Message-ID: <5639C4D2.3060505@gmail.com> (raw)
In-Reply-To: <CAHp75VcKjZebwiV23yTq=ahzwh6Mqe58U_AOcOoC5Z9oLG-wWw@mail.gmail.com>

Hi

Andy Shevchenko 於 2015/11/3 下午 05:45 寫道:
> On Tue, Nov 3, 2015 at 5:51 AM, Peter Hung <hpeter@gmail.com> wrote:
>> + *    Please reference https://bitbucket.org/hpeter/fintek-general/src/
>> + *    with f81534/tools to get set_gpio.c & set_mode.c. Please use it
>> + *    carefully.
>
> Would it be good to have this under Documentation ?

I had some documents in source code. The link is the demo program to
implement switch UART/PIN funcion. I'll try to add for document with the
repository.

>> +static void f81534_dtr_rts(struct usb_serial_port *port, int on);
>> +
>> +static int f81534_set_port_mode(struct usb_serial_port *port,
>> +                                       enum uart_mode eMode);
>> +
>> +static int f81534_save_configure_data(struct usb_serial_port *port);
>> +
>> +static int f81534_switch_gpio_mode(struct usb_serial_port *port, u8 mode);
>> +
>> +static void f81534_wakeup_all_port(struct usb_serial *serial);
>> +
>> +static void f81534_compare_msr(struct usb_serial_port *port, u8 *msr,
>> +                                       bool is_port_open);
>> +
>> +static int f81534_prepare_write_buffer(struct usb_serial_port *port,
>> +                                       void *dest, size_t size);
>> +
>> +static int f81534_submit_writer(struct usb_serial_port *port, gfp_t mem_flags);
>
> Would it be possible to reshuffle code to reduce amount of forward declarations?
>

I'll try to reduce it.

>
>> +                       if ((size <= F81534_MAX_DATA_BLOCK) &&
>> +                                       (read_size == (count + 1))) {
>
> No need to have internal parens.
>

In my opinion, It makes more readable. Should I remove it?


>> +       if (baudrate <= 115200) {
>> +               value = 0x01;   /* 1.846m fixed */
>> +               divisor = f81534_calc_baud_divisor(baudrate, 115200, NULL);
>> +               port_priv->current_baud_base = 115200;
>> +       } else {
>> +               for (count = 0; count < ARRAY_SIZE(baudrate_table) ; ++count) {
>> +                       baud_base = baudrate_table[count];
>> +                       divisor = f81534_calc_baud_divisor(baudrate, baud_base,
>> +                                                               &rem);
>> +                       if (!rem) {
>> +                               dev_dbg(&port->dev, "%s: found clockbase %d\n",
>> +                                               __func__,
>> +                                               baudrate_table[count]);
>> +                               value = clock_table[count];
>> +                               port_priv->current_baud_base = baud_base;
>> +                               break;
>> +                       }
>> +               }
>
> Can you calculate baud rates more precisely? Any link to datasheet
> where it's described?
>

I'll try to comment it within source code.

>> +static int f81534_ioctl_get_rs485(struct usb_serial_port *port,
>> +                                       struct serial_rs485 __user *arg)
>> +{
>> +       int status;
>> +       struct serial_rs485 data;
>> +       struct f81534_port_private *port_priv = usb_get_serial_port_data(port);
>> +       struct f81534_serial_private *serial_priv =
>> +                       usb_get_serial_data(port->serial);
>
> One line?
>

It's over 80 character with a tab, It cant be one line.

I'll fix other issue that you mention.

Thanks for your advices.
-- 
With Best Regards,
Peter Hung

  reply	other threads:[~2015-11-04  8:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03  3:51 [PATCH V6 1/1] usb:serial: Add Fintek F81532/534 driver Peter Hung
2015-11-03  6:28 ` kbuild test robot
2015-11-03  7:06 ` kbuild test robot
2015-11-03  9:45 ` Andy Shevchenko
2015-11-04  8:41   ` Peter Hung [this message]
2015-11-03 10:03 ` Oliver Neukum
2015-11-04  8:19   ` Peter Hung
2015-11-04  8:38     ` Oliver Neukum
2015-11-05  2:48       ` Peter Hung
2015-11-05  2:55 ` Peter Hung

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=5639C4D2.3060505@gmail.com \
    --to=hpeter@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpeter+linux_kernel@gmail.com \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peter_hong@fintek.com.tw \
    --cc=tom_tsai@fintek.com.tw \
    /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.