linux-kernel - [PATCHv1 bluetooth-next] cc2520: set the default fifo pin value from platform data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <BLU168-W12778BE0A70F0EA756A9E8CD6700@phx.gbl>
Date:	Mon, 10 Aug 2015 15:29:07 +0800
From:	LIYONG <sdliyong@...il.com>
To:	"varkabhadram@...il.com" <varkabhadram@...il.com>,
	"alex.aring@...il.com" <alex.aring@...il.com>,
	"linux-wpan@...r.kernel.org" <linux-wpan@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:	YONG LI <sdliyong@...il.com>
Subject: [PATCHv1 bluetooth-next] cc2520: set the default fifo pin value
 from platform data

In case of the device tree support is disabled, the fifo_pin is uninitialized, this
patch will set the fifo_pin value based on platform data

Signed-off-by: Yong Li <sdliyong@...il.com>
---
 drivers/net/ieee802154/cc2520.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/net/ieee802154/cc2520.c b/drivers/net/ieee802154/cc2520.c
index 613dae5..c5b54a1 100644
--- a/drivers/net/ieee802154/cc2520.c
+++ b/drivers/net/ieee802154/cc2520.c
@@ -833,6 +833,7 @@ static int cc2520_get_platform_data(struct spi_device *spi,
                if (!spi_pdata)
                        return -ENOENT;
                *pdata = *spi_pdata;
+               priv->fifo_pin = pdata->fifo;
                return 0;
        }

--
2.1.0

 		 	   		  --
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/