From: "Giuseppe Lippolis" <giu.lippolis@gmail.com>
To: <linux-kernel@vger.kernel.org>
Subject: adding si3210 driver
Date: Thu, 2 Feb 2017 19:05:55 +0100 [thread overview]
Message-ID: <009401d27d7f$00364180$00a2c480$@gmail.com> (raw)
Hi All,
I have a router running linux (LEDE distribution) with an embedded 3G modem
and a POTS telephone interface.
The telephone interface uses the si3210 device interfaced with the uP
through an spi IF.
The si3210 ProSLIC integrates a subscriber line interface circuit (SLIC) and
is commonly found in several router with telephone functions.
Because I was unable to find a driver for the si3210, I'm now using the
spidev interface to control the device from the userspace.
Now I'm thinking to add a spi protocol char driver for that device.
My first question is if make sense to do this; I see other similar tentative
never embedded in the mainstream:
https://github.com/stelhs/slic_tdm
https://github.com/opennetworklinux/linux-3.8.13/tree/master/drivers/tdm/lin
e_ctrl
Second question is: What class the driver belong to? (in which drivers/
subfolder shall I add the driver)?
Thanks for the support.
Bye.
reply other threads:[~2017-02-02 18:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='009401d27d7f$00364180$00a2c480$@gmail.com' \
--to=giu.lippolis@gmail.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).