Hello,
this patch series add a sysfs file to let userspace know which mux
id has been used to create a qmimux network interface.
I'm aware that adding new sysfs files is not usually the right path,
but my understanding is that this piece of information can't be
retrieved in any other way and its absence restricts how
userspace application (e.g. like libqmi) can take advantage of the
qmimux implementation in qmi_wwan.
Thanks,
Daniele
v2: used sysfs_emit in mux_id_show
Daniele Palmas (2):
net: usb: qmi_wwan: add qmap id sysfs file for qmimux interfaces
net: qmi_wwan: document qmap/mux_id sysfs file
Documentation/ABI/testing/sysfs-class-net-qmi | 10 +++++++
drivers/net/usb/qmi_wwan.c | 27 +++++++++++++++++++
2 files changed, 37 insertions(+)
--
2.17.1
Add qmimux interface sysfs file qmap/mux_id to show qmap id set
during the interface creation, in order to provide a method for
userspace to associate QMI control channels to network interfaces.
Signed-off-by: Daniele Palmas <redacted>
---
drivers/net/usb/qmi_wwan.c | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
@@ -48,3 +48,13 @@ Description: Write a number ranging from 1 to 254 to delete a previously created qmap mux based network device.++What: /sys/class/net/<qmimux iface>/qmap/mux_id+Date: January 2021+KernelVersion: 5.12+Contact: Daniele Palmas <dnlplm@gmail.com>+Description:+ Unsigned integer++ Indicates the mux id associated to the qmimux network interface+ during its creation.
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 27 Jan 2021 16:34:31 +0100 you wrote:
Hello,
this patch series add a sysfs file to let userspace know which mux
id has been used to create a qmimux network interface.
I'm aware that adding new sysfs files is not usually the right path,
but my understanding is that this piece of information can't be
retrieved in any other way and its absence restricts how
userspace application (e.g. like libqmi) can take advantage of the
qmimux implementation in qmi_wwan.
[...]