From: Frederic Danis <frederic.danis@linux.intel.com>
To: Ilya Faenson <ifaenson@broadcom.com>,
Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>,
Arend Van Spriel <arend@broadcom.com>
Subject: Re: [PATCH v4 2/4] hci_uart: line discipline enhancements
Date: Thu, 18 Jun 2015 11:46:03 +0200 [thread overview]
Message-ID: <5582935B.1030100@linux.intel.com> (raw)
In-Reply-To: <E0D3336E15B58B4294723AC879BA5E94263438@IRVEXCHMB15.corp.ad.broadcom.com>
Hello Marcel and Ilya,
On 17/06/2015 23:53, Ilya Faenson wrote:
> Thanks a lot, Marcel.
>
> -----Original Message-----
> From: Marcel Holtmann [mailto:marcel@holtmann.org]
> Sent: Wednesday, June 17, 2015 5:51 PM
> To: Ilya Faenson
> Cc: BlueZ development; Arend Van Spriel
> Subject: Re: [PATCH v4 2/4] hci_uart: line discipline enhancements
>
> Hi Ilya,
<snip>
>> @@ -287,15 +366,28 @@ static int hci_uart_setup(struct hci_dev *hdev)
>> struct hci_uart *hu = hci_get_drvdata(hdev);
>> struct hci_rp_read_local_version *ver;
>> struct sk_buff *skb;
>> + unsigned int speed;
>> int err;
>>
>> + /* Init speed if any */
>> + speed = 0;
>> if (hu->proto->init_speed)
>> - hci_uart_set_baudrate(hu, hu->proto->init_speed);
>> -
>> - if (hu->proto->set_baudrate && hu->proto->oper_speed) {
>> - err = hu->proto->set_baudrate(hu, hu->proto->oper_speed);
>> + speed = hu->proto->init_speed;
>> + else if (hu->init_speed)
>> + speed = hu->init_speed;
>
> I added the speed assignment as else statement
>
> else
> speed = 0;
Afaiu, with this change hu->proto->*speed will always be used for all
bcm device.
I think hu->*speed should be used if exist or hu->proto->*speed, so the
test should be swapped.
The equivalent change is needed in bcm_setup() of hci_bcm.c.
Ilya, do you want to do it or should I send a patch ?
Regards
Fred
next prev parent reply other threads:[~2015-06-18 9:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 21:30 [PATCH v4 0/4] Broadcom Bluetooth UART device driver Ilya Faenson
2015-06-17 21:30 ` [PATCH v4 1/4] Broadcom Bluetooth UART Device Tree bindings Ilya Faenson
2015-06-17 21:33 ` Arend van Spriel
2015-06-17 23:11 ` FW: " Ilya Faenson
2015-06-18 15:02 ` Rob Herring
2015-06-18 18:54 ` Ilya Faenson
2015-06-18 19:41 ` Rob Herring
2015-06-18 20:37 ` Ilya Faenson
2015-06-19 15:47 ` Rob Herring
2015-06-19 17:06 ` Arend van Spriel
2015-06-19 18:49 ` Rob Herring
2015-06-19 19:20 ` Arend van Spriel
2015-06-29 18:36 ` Arend van Spriel
2015-07-02 18:26 ` Rob Herring
2015-06-19 20:37 ` Ilya Faenson
2015-06-19 19:23 ` Fabio Estevam
2015-06-19 20:40 ` Ilya Faenson
2015-06-17 21:30 ` [PATCH v4 2/4] hci_uart: line discipline enhancements Ilya Faenson
2015-06-17 21:50 ` Marcel Holtmann
2015-06-17 21:53 ` Ilya Faenson
2015-06-18 9:46 ` Frederic Danis [this message]
2015-06-18 10:17 ` Marcel Holtmann
2015-06-17 21:30 ` [PATCH v4 3/4] btbcm_uart: Broadcom UART Platform Driver Ilya Faenson
2015-06-17 21:30 ` [PATCH v4 4/4] hci_bcm: Broadcom UART protocol enhancements Ilya Faenson
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=5582935B.1030100@linux.intel.com \
--to=frederic.danis@linux.intel.com \
--cc=arend@broadcom.com \
--cc=ifaenson@broadcom.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).