linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rjliao@codeaurora.org
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Balakrishna Godavarthi <bgodavar@codeaurora.org>,
	marcel@holtmann.org, johan.hedberg@gmail.com,
	linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
	hemantg@codeaurora.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: hci_qca: Enable the ldisc for ROME for x86 platforms.
Date: Wed, 13 Mar 2019 17:43:14 +0800	[thread overview]
Message-ID: <a99bdc7679c9220a913dfa3e149757fa@codeaurora.org> (raw)
In-Reply-To: <20190312155241.GB200579@google.com>

在 2019-03-12 23:52,Matthias Kaehlcke 写道:
> Hi Rocky,
> 
> On Tue, Mar 12, 2019 at 05:01:59PM +0800, rjliao@codeaurora.org wrote:
>> 在 2019-03-09 02:52,Matthias Kaehlcke 写道:
>> > On Fri, Mar 08, 2019 at 10:43:14AM +0530, Balakrishna Godavarthi wrote:
>> > > Hi Matthias,
>> > >
>> > > On 2019-03-08 02:12, Matthias Kaehlcke wrote:
>> > > > Hi Balakrishna,
>> > > >
>> > > > On Thu, Mar 07, 2019 at 03:47:22PM +0530, Balakrishna Godavarthi wrote:
>> > > > > When using btattach to setup Rome over ldisc we observed a crash
>> > > > > in qca_setup as it will try to access the serdev which is not
>> > > > > available in the ldisc proto. This patch will fix the crash by
>> > > > > support both the ldisc and serdev way in the qca hci_uart driver.
>> > > > >
>> > > > > Signed-off-by: Balakrishna Godavarthi <bgodavar@codeaurora.org>
>> > > >
>> > > > Oh, I wasn't aware of the instantiation through ldisc and was actually
>> > > > considering to *remove* some of the seemingly unnecessary serdev
>> > > > checks.
>> > > >
>> > > > > ---
>> > > > >  drivers/bluetooth/hci_qca.c | 47
>> > > > > ++++++++++++++++++++++---------------
>> > > > >  1 file changed, 28 insertions(+), 19 deletions(-)
>> > > > >
>> > > > > diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
>> > > > > index 237aea34b69f..0a5c98d46864 100644
>> > > > > --- a/drivers/bluetooth/hci_qca.c
>> > > > > +++ b/drivers/bluetooth/hci_qca.c
>> > > > > @@ -963,7 +963,7 @@ static int qca_set_baudrate(struct hci_dev
>> > > > > *hdev, uint8_t baudrate)
>> > > > >  {
>> > > > >  	struct hci_uart *hu = hci_get_drvdata(hdev);
>> > > > >  	struct qca_data *qca = hu->priv;
>> > > > > -	struct qca_serdev *qcadev;
>> > > > > +	struct qca_serdev *qcadev = NULL;
>> > > >
>> > > > In many cases the only field that is accessed is qcadev->btsoc_type. I
>> > > > think something like 'qca_get_soc_type(struct hci_dev *hdev / struct
>> > > > hci_uart *hu)' would make things more readable.
>> > > >
>> > > [Bala]: sure will update this in other patch once this change is
>> > > landed as
>> > > this has to
>> > >         go in priority as we have crash coming.
>> >
>> > That's not how things should work, especially for fairly trivial
>> > changes. It requires reviewers to first spent time to review the patch
>> > that adds clutter and later spend more time to review the one that
>> > removes it. It's also easier to get a clean patch merged in the first
>> > place, rather than a noisy one.
>> >
>> > Anyway, here is my take at it:
>> > https://lore.kernel.org/patchwork/patch/1049014/
>> >
>> > Please help with testing for ROME, unless you disagree with the
>> > approach.
>> >
>> > Thanks
>> >
>> > Matthias
>> 
>> Hi Matthias,
>> 
>> I will test your patch and update to you, and you are correct that 
>> AR3002 is
>> not part of Rome family, you should use QCA_ROME as the default return 
>> of
>> qca_soc_type.
> 
> Thanks for the confirmation!
> 
>> Could you also loop me in
>> https://lore.kernel.org/patchwork/patch/1049014/?
> 
> This patch has been superseded by a newer version:
> 
> https://lore.kernel.org/patchwork/patch/1049696/
> 
> It already landed in bluetooth-next.
> 
> Testing with Rome and ldisc would still be appreciated, since I don't
> have such a configuration.
> 
> Thanks
> 
> Matthias

Hi Matthias,

I verified your change and found there is another deference to serdev in 
the qca_set_baudrate() function while running the ldisc proto, it will 
cause a crash and need to add a check as below. Could you help to add 
this change?

<       serdev_device_wait_until_sent(hu->serdev,
<                       msecs_to_jiffies(CMD_TRANS_TIMEOUT_MS));
---
>       if (hu->serdev)
>               serdev_device_wait_until_sent(hu->serdev,
>                               msecs_to_jiffies(CMD_TRANS_TIMEOUT_MS));

  reply	other threads:[~2019-03-13  9:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 10:17 [PATCH v1] Bluetooth: hci_qca: Enable the ldisc for ROME for x86 platforms Balakrishna Godavarthi
2019-03-07 20:42 ` Matthias Kaehlcke
2019-03-08  5:13   ` Balakrishna Godavarthi
2019-03-08 18:52     ` Matthias Kaehlcke
2019-03-12  9:01       ` rjliao
2019-03-12 15:52         ` Matthias Kaehlcke
2019-03-13  9:43           ` rjliao [this message]
2019-03-13 23:56             ` Matthias Kaehlcke

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=a99bdc7679c9220a913dfa3e149757fa@codeaurora.org \
    --to=rjliao@codeaurora.org \
    --cc=bgodavar@codeaurora.org \
    --cc=hemantg@codeaurora.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mka@chromium.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).