All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Johan Hovold <johan@kernel.org>,
	linux-spi@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: Linux gnss driver SPI support?
Date: Thu, 7 Jan 2021 10:03:49 +0100	[thread overview]
Message-ID: <X/bOdQMe80v4N3AF@hovoldconsulting.com> (raw)
In-Reply-To: <CAJ+vNU3WyXT5ozp1mc2EnxHrPGxzEGy8Tt1sNVLV+5WSfeAA+w@mail.gmail.com>

On Wed, Jan 06, 2021 at 12:17:01PM -0800, Tim Harvey wrote:
> On Wed, Jan 6, 2021 at 3:21 AM Johan Hovold <johan@kernel.org> wrote:

> > Correct, there are currently no drivers supporting SPI and hence no
> > shared implementation either like there is for UART interfaces.
> >
> > The driver for your device would need to handle the SPI bits itself for
> > now. What kind of device is it?

> It is the u-blox ZOE-M8Q which has a UART as well as SPI/I2C/SQI
> interface. The particular board design we are working on is
> unfortunately out of UART's which is why we were looking at connecting
> it via SPI.

So we'd need to add support for the SPI interface to the ublox driver,
which is currently UART only.

> I did come across a posting about this [1] which uses a userspace app
> that creates a spy to pty bridge but it seems like they ran into some
> performance/latency issues.

Yeah, that is one of the problems that the gnss subsystem is meant to
solve; to handle the transport interface in the kernel and provide a
generic interface to user space.

Johan

      reply	other threads:[~2021-01-07  9:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 18:23 Linux gnss driver SPI support? Tim Harvey
2021-01-06 11:21 ` Johan Hovold
2021-01-06 20:17   ` Tim Harvey
2021-01-07  9:03     ` Johan Hovold [this message]

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=X/bOdQMe80v4N3AF@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=tharvey@gateworks.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.