All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Interface between LTE devices and Linux
Date: Thu, 8 Feb 2018 18:18:28 +0100	[thread overview]
Message-ID: <20180208171828.GA11601@kroah.com> (raw)
In-Reply-To: <CAOhBGduK6iq+FQ527+JG9BHwziCjBzkeP-3MjivCuVAFE0P7XA@mail.gmail.com>

On Thu, Feb 08, 2018 at 06:10:59PM +0100, jjDaNiMoTh wrote:
> Hello everyone,
> 
> There is an example of LTE netdevice in the Linux source tree?
> 
> In particular, I would like to know if there is any device driver that
> implements the layers required by the 3GPP standard. I imagine that it
> should exist something since Android is communicating over LTE, but I can't
> find any reference.

That communication happens usually through a "dumb" serial-like
connection to the LTE modem.  All of the modem commands are handled in
userspace, the kernel doesn't care about anything relating to this at
all (and it really shouldn't).

> What I fear more is that everything related to LTE is inside the
> closed device firmware, and data is sent from the TC layer into this
> black-box firmware through a sort of API. In this case, it would be
> wonderful to know where, exactly, this API is used, to try to
> understand what the firmware is doing.

Look at the Android AOSP images for the location for most of this logic,
there should be a Telephony HAL somewhere in there that handles the
heavy-lifting of all of this logic.

Good luck!

greg k-h

  reply	other threads:[~2018-02-08 17:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 17:10 Interface between LTE devices and Linux jjDaNiMoTh
2018-02-08 17:18 ` Greg KH [this message]
2018-02-13  7:59   ` Nuno Sá
2018-02-13 13:21 ` Jeffrey Walton
2018-02-13 15:30   ` Bjørn Mork
2018-02-13 16:07     ` Jeffrey Walton

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=20180208171828.GA11601@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 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.