From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Johan Hovold <johan@kernel.org>, Rob Herring <robh+dt@kernel.org>,
David Heidelberg <david.heidelberg@collabora.com>,
Svyatoslav Ryhel <clamor95@gmail.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: gnss: Add Broacom BCM4751 family bindings
Date: Mon, 18 Apr 2022 14:19:52 +0300 [thread overview]
Message-ID: <f4deb182-ec18-6744-2c4c-adaed4ef7a33@collabora.com> (raw)
In-Reply-To: <20220414214337.311880-1-linus.walleij@linaro.org>
Hi Linus,
On 4/15/22 00:43, Linus Walleij wrote:
> The Broadcom BCM4751 family of (A-)GPS chips have been around for
> some years. The latest iteration BCM4753 is for example mounted
> on the Huawei HiKey970.
>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> .../bindings/gnss/brcm,bcm4751.yaml | 69 +++++++++++++++++++
> 1 file changed, 69 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/gnss/brcm,bcm4751.yaml
What are the chances of seeing the kernel driver for BCM4751+? There are
myriads of Android devices using that GPS chip. Previously the
proprietary firmware interface of BCM4751 was an obstacle for addition
of the driver to upstream kernel, did anything change?
next prev parent reply other threads:[~2022-04-18 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 21:43 Linus Walleij
2022-04-18 11:19 ` Dmitry Osipenko [this message]
2022-04-22 21:50 ` Linus Walleij
2022-04-23 14:12 ` Dmitry Osipenko
2022-04-23 15:09 ` Linus Walleij
2022-04-19 18:11 ` Rob Herring
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=f4deb182-ec18-6744-2c4c-adaed4ef7a33@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=clamor95@gmail.com \
--cc=david.heidelberg@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®