public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Johan Hovold <johan@kernel.org>
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/5] WIP: gnss: merge MTK driver into UBX driver
Date: Tue, 20 Jun 2023 12:21:40 +0200	[thread overview]
Message-ID: <ZJF9tJokpbFtaeLG@ninjato> (raw)
In-Reply-To: <ZJFRnIFUokVvV-pY@hovoldconsulting.com>

[-- Attachment #1: Type: text/plain, Size: 590 bytes --]


> First, some of these devices support vendor specific protocols which we
> may add driver support for at some point beyond currently just exporting
> this information to user space (e.g. to change line speed from the
> driver).

Speaking of proprietary protocols: did you ever get in contact with the
gpsd folks? I stumbled over this mail from February this year [1] where
nobody knew where this /dev/gnss0 device came from. I'd think we should
be in contact with them if we want to support e.g. line speed changes?

[1] https://lists.gnu.org/archive/html/gpsd-dev/2023-02/msg00017.html


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-06-20 10:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23  6:43 [RFC PATCH 0/5] gnss: updates to support the Renesas KingFisher board Wolfram Sang
2023-05-23  6:43 ` [RFC PATCH 1/5] WIP: gnss: merge MTK driver into UBX driver Wolfram Sang
2023-06-12 11:35   ` Wolfram Sang
2023-06-20  7:13     ` Johan Hovold
2023-06-20  9:00       ` Wolfram Sang
2023-06-20 10:21       ` Wolfram Sang [this message]
2023-06-20 14:50         ` Johan Hovold
2023-05-23  6:43 ` [RFC PATCH 2/5] gnss: ubx: use new helper to remove open coded regulator handling Wolfram Sang
2023-06-20  8:48   ` Johan Hovold
2023-06-20  9:04     ` Wolfram Sang
2023-06-20  9:08       ` Johan Hovold
2023-05-23  6:43 ` [RFC PATCH 3/5] gnss: ubx: 'vcc' can be optional Wolfram Sang
2023-06-20  7:15   ` Johan Hovold
2023-06-20  9:04     ` Wolfram Sang
2023-05-23  6:43 ` [RFC PATCH 4/5] gnss: ubx: add support for the reset gpio Wolfram Sang
2023-06-20  7:17   ` Johan Hovold
2023-06-20  9:06     ` Wolfram Sang
2023-06-20  9:12       ` Johan Hovold
2023-06-20  9:41         ` Wolfram Sang
2023-06-20 10:05           ` Johan Hovold
2023-06-20 10:14             ` Wolfram Sang
2023-05-23  6:43 ` [RFC PATCH 5/5] arm64: dts: renesas: ulcb-kf: add node for GPS Wolfram Sang

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=ZJF9tJokpbFtaeLG@ninjato \
    --to=wsa+renesas@sang-engineering.com \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.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