From: Andrew Lunn <andrew@lunn.ch>
To: "i.n.a" <quiet-daffodil@proton.me>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: Re: [RFC] Appropriate subsystem/UAPI for Semtech SX126x packet radio support
Date: Sun, 20 Sep 2026 23:38:16 +0200 [thread overview]
Message-ID: <425865f4-2eb5-4346-a7b4-be89ea7ff8bb@lunn.ch> (raw)
In-Reply-To: <HnbG4UMw_4eCU415RUgCB-SE6LmXjFLinorFY6rJXqP5bO7CJzyxEuuNVgDoA1oVs0c0AaqWcfAQdPRORxpRNmlD1iWUzhXqPtq2qByuJcw=@proton.me>
On Sun, Sep 20, 2026 at 09:15:16PM +0000, i.n.a wrote:
> Hi,
>
> I'm working on a general-purpose Linux driver for the Semtech SX126x family of sub-GHz radio transceivers, initially targeting the SX1262.
>
> Semtech provides a portable C driver for the radio, with the platform-specific interface abstracted behind read, write, reset and wakeup operations:
>
> https://github.com/Lora-net/sx126x_driver
>
> I'm currently implementing the Linux side using SPI, GPIO and IRQ infrastructure.
>
> The SX126x supports LoRa and (G)FSK packet modes, but isn't inherently tied to a particular higher-level protocol. My intention is therefore to keep protocols such as LoRaWAN, AX.25 and Reticulum outside the hardware driver and expose generic packet TX/RX, PHY configuration, radio state and receive metadata such as RSSI/SNR.
>
> I was considering exposing the radio as a character device, for example `/dev/sx126x0`, with a small userspace API for configuration and packet I/O.
One thing to keep in mind is that there are other vendors producing similar devices, e.g:
https://www.microchip.com/en-us/products/wireless-connectivity/sub-ghz/lora
https://www.st.com/en/microcontrollers-microprocessors/stm32wl-series.html
You want to make whatever API you design vendor independent.
Andrew
next prev parent reply other threads:[~2026-09-20 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 21:15 [RFC] Appropriate subsystem/UAPI for Semtech SX126x packet radio support i.n.a
2026-09-20 21:38 ` Andrew Lunn [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-20 21:50 i.n.a
2026-09-20 22:15 ` Andrew Lunn
2026-09-20 23:06 i.n.a
2026-09-24 1:32 ` Jakub Kicinski
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=425865f4-2eb5-4346-a7b4-be89ea7ff8bb@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=quiet-daffodil@proton.me \
/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