linux-kernel - Platform device initialization

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 for Android: free password hash cracker in your pocket

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

Message-ID: <54DB47D1.9040503@vltc.net.eu.org>
Date:	Wed, 11 Feb 2015 15:15:13 +0300
From:	Tsendrovskii Vladislav <vlad@...c.net.eu.org>
To:	linux-kernel@...r.kernel.org
Subject: Platform device initialization

Hello!

I'm writing module for new SPI master device, and I have some strange 
problem during probing. Exactly, it looks that probe function even 
doesn't called.

static int spi_gpio_cs_probe(struct platform_device* pdev)
{
.....
}
......
static struct platform_driver spi_gpio_cs_driver = {
     .driver = {
         .name    = DRIVER_NAME,
     },
     .probe        = spi_gpio_cs_probe,
     .remove        = spi_gpio_cs_remove,
};

module_platform_driver(spi_gpio_cs_driver);

I've tried to put "return -ENODEV;" and "return -ENOMEM;" in the 
begining of the probe function, but insmod works without error message.
I've looked other modules, which uses platform device infrastructure, 
this part of code in most of them looks the same.

--
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/