mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Tim Bird <tim.bird@am.sony.com>,
	linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: GPS driver for Linux - kernel or user-space driver?
Date: Wed, 3 Apr 2013 18:19:15 -0700	[thread overview]
Message-ID: <20130404011915.GA20339@kroah.com> (raw)
In-Reply-To: <52ACDBA8-BAEC-4687-94D7-586F494A7373@holtmann.org>

On Wed, Apr 03, 2013 at 06:12:42PM -0700, Marcel Holtmann wrote:
> Hi Greg,
> 
> >> I've been approached by a developer at Sony who wants to publish an
> >> open source driver for a Sony GPS receiver module.
> > 
> > What does the device look like?  USB device?  UART?  Something else?
> > 
> >> I've looked in the kernel source, and only see one standalone GPS
> >> driver, for Garmin.  It appears that most GPS support in Linux is done
> >> via user-space drivers.  Many GPS hardware modules appear to be
> >> accessed via a serial line, or USB/serial port.  The Sony
> >> module is pretty much the same, accepting commands and delivering
> >> data via a uart from the chip.
> >> 
> >> I planning to recommend writing a user-space driver (based on
> >> gpsd and/or the Android GPS HAL specification).  But I'm worried
> >> I'm missing something.  Is this the correct approach, or is there
> >> an established kernel API for GPS modules - such that I should
> >> recommend that this developer writes a kernel module instead
> >> of, or in addition to, the user-space support for the hardware?
> > 
> > If it's just a uart-like device, just write a serial driver and drive it
> > from gpsd.  That way seems to be the simplest and then the kernel just
> > becomes a dumb-pipe, which is fine.
> 
> the one thing that still bugs me is that detecting an UART with GPS
> functionality behind it is extremely bad experience. If we could get
> something like DEVTYPE=gps support for the TTY layer, that would be
> helpful.

I would love that, but there's tons of USB gps devices that we don't
know if they are a USB serial device, or a GPS device as the device id
is the same (companies just embed a usb to serial chip in their
devices.)

So, someone has to guess, right now it's userspace.

Unless you have a better idea?

thanks,

greg k-h

  reply	other threads:[~2013-04-04  1:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04  0:52 Tim Bird
2013-04-04  1:06 ` Greg KH
2013-04-04  1:12   ` Marcel Holtmann
2013-04-04  1:19     ` Greg KH [this message]
2013-04-04  1:44       ` Marcel Holtmann
2013-04-04  2:08         ` Greg KH
2013-04-04  7:33         ` Mika Westerberg

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=20130404011915.GA20339@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=tim.bird@am.sony.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome