From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Thierry Escande <thierry.escande@linaro.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Rob Herring <robh+dt@kernel.org>,
Andy Gross <andy.gross@linaro.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
David Brown <david.brown@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Loic Poulain <loic.poulain@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-bluetooth@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree <devicetree@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/3] dt-bindings: net: bluetooth: Add qualcomm-bluetooth
Date: Tue, 27 Mar 2018 11:47:22 -0700 [thread overview]
Message-ID: <20180327184722.GB18510@minitux> (raw)
In-Reply-To: <2e0db4b4-80cc-9a5b-9e0a-812f1bc9fbcf@linaro.org>
On Tue 27 Mar 08:56 PDT 2018, Thierry Escande wrote:
> Hi Bjorn,
>
> On 27/03/2018 00:51, Bjorn Andersson wrote:
> > On Tue 20 Mar 23:58 HKT 2018, Marcel Holtmann wrote:
> > > > Signed-off-by: Thierry Escande <thierry.escande@linaro.org>
> > [..]
> > > > + - clocks: clock phandle for SUSCLK_32KHZ
> > >
> > > if I compare this with broadcom-bluetooth.txt or ti-bluetooth.txt then
> > > besides compatible, everything else is optional. The
> > > nokia-bluetooth.txt has everything required, but that is also a really
> > > specific platform.
> > >
> > > Can we be less restrictive for a QCA general purpose chip?
> > >
> >
> > The way we deal with this in other bindings is that we tie such
> > requirements to the compatible; i.e. we would say that qcom,qca6174-bt
> > requires a clock and we would have something like qcom,qca-bt that makes
> > it optional.
> >
> > The beauty of this is that the driver will tell you if you forgot to
> > specify the clock when it actually is required, which saves you
> > considerable amount of debugging time.
> >
> >
> > NB. The way the bcm driver handles this is insufficient, as it treats
> > any error from clk_get as "there's no clock specified". The driver
> > should accept a clock not being specified, but should fail properly when
> > a clock is specified but can't be acquired (e.g. due to clk_get()
> > returning EPROBE_DEFER).
> >
> > > > +
> > > > +Example:
> > > > +
> > > > +serial@7570000 {
> > > > + pinctrl-names = "default", "sleep";
> > > > + pinctrl-0 = <&blsp1_uart1_default>;
> > > > + pinctrl-1 = <&blsp1_uart1_sleep>;
> > > > +
> > > > + bluetooth {
> > > > + compatible = "qcom,qca6174-bt";
> > > > +
> > > > + enable-gpios = <&pm8994_gpios 19 GPIO_ACTIVE_HIGH>;
> > > > +
> > > > + pinctrl-names = "default";
> > > > + pinctrl-0 = <&bt_en_pin_a>;
> > >
> > > This one I do not understand and you might want to shed some light
> > > into why this is done that way.
> > >
> >
> > This is completely generic and only relates to getting the electrical
> > properties of the gpio pin set up correctly. So I would recommend that
> > we omit this from the binding and example (including the pinctrl
> > properties for the serial above).
>
> If I remove the pinctrl entry in the bluetooth node, the gpio19 is then
> marked as unclaimed. The drive strength also defaults to low but that
> doesn't seem to be an issue and the the chip can still be enabled through
> gpio19. Is it ok to have it unclaimed? If so I can remove it from the
> binding and the doc then.
>
> Regarding the blsp1_uart1_default of the serial node, I can still enable the
> chip if I remove it but the hci commands all end in timeout. It seems that
> the function for these pins has to be explicitly set to blsp_uart2. So at
> least, the default pinctrl seems mandatory.
>
Our board needs these properties to get the uart and gpio in the right
state, but this is unrelated to BT - that's why I suggested that you
omit these properties from the BT binding.
Regards,
Bjorn
next prev parent reply other threads:[~2018-03-27 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 3:23 [PATCH v5 0/3] Bluetooth: hci_qca: Add serdev support Thierry Escande
2018-03-20 3:23 ` [PATCH v5 1/3] arm64: dts: apq8096-db820c: enable bluetooth node Thierry Escande
2018-03-20 3:23 ` [PATCH v5 2/3] dt-bindings: net: bluetooth: Add qualcomm-bluetooth Thierry Escande
2018-03-20 15:58 ` Marcel Holtmann
2018-03-26 16:45 ` Thierry Escande
2018-03-26 22:51 ` Bjorn Andersson
2018-03-27 15:56 ` Thierry Escande
2018-03-27 18:47 ` Bjorn Andersson [this message]
2018-03-26 22:23 ` Rob Herring
2018-03-20 3:23 ` [PATCH v5 3/3] Bluetooth: hci_qca: Add serdev support Thierry Escande
2018-03-20 10:54 ` Andy Shevchenko
2018-03-20 15:49 ` Marcel Holtmann
2018-03-26 16:44 ` Thierry Escande
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=20180327184722.GB18510@minitux \
--to=bjorn.andersson@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.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=loic.poulain@linaro.org \
--cc=marcel@holtmann.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=thierry.escande@linaro.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).