The 'wwan' devtype is meant for devices that require additional
configuration to be used, like WWAN specific APN setup over AT/QMI
commands, rmnet link creation, etc. This is the case for MHI (Modem
host Interface) netdev which targets modem/WWAN endpoints.

Signed-off-by: Loic Poulain <loic.poul...@linaro.org>
---
 drivers/net/mhi_net.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/drivers/net/mhi_net.c b/drivers/net/mhi_net.c
index f83562d..e3f9c0d 100644
--- a/drivers/net/mhi_net.c
+++ b/drivers/net/mhi_net.c
@@ -234,6 +234,10 @@ static void mhi_net_rx_refill_work(struct work_struct 
*work)
                schedule_delayed_work(&mhi_netdev->rx_refill, HZ / 2);
 }
 
+static struct device_type wwan_type = {
+       .name = "wwan",
+};
+
 static int mhi_net_probe(struct mhi_device *mhi_dev,
                         const struct mhi_device_id *id)
 {
@@ -253,6 +257,7 @@ static int mhi_net_probe(struct mhi_device *mhi_dev,
        mhi_netdev->ndev = ndev;
        mhi_netdev->mdev = mhi_dev;
        SET_NETDEV_DEV(ndev, &mhi_dev->dev);
+       SET_NETDEV_DEVTYPE(ndev, &wwan_type);
 
        INIT_DELAYED_WORK(&mhi_netdev->rx_refill, mhi_net_rx_refill_work);
        u64_stats_init(&mhi_netdev->stats.rx_syncp);
-- 
2.7.4

Reply via email to