Searched refs:driver (Results 12751 – 12775 of 13070) sorted by relevance
1...<<511512513514515516517518519520>>...523
2710 .driver = {
2384 .driver = {
2291 .driver = {
2737 .driver = {
301 .driver = {
2970 .driver = {
2146 .driver = {
94 owner = sd->entity.graph_obj.mdev->dev->driver->owner; in subdev_open()
1540 .driver = {
4294 strscpy(info->driver, DRV_NAME, sizeof(info->driver)); in nv_get_drvinfo()6476 .driver.pm = NV_PM_OPS,
509 fcd7350 tegra: Add LCD driver567 08: tegra: Add LCD driver
1763 strncpy(info->driver, DRIVER_NAME, sizeof(info->driver)); in lan78xx_get_drvinfo()
922 Hay varias modelos de macros de diagnóstico de driver en <linux/dev_printk.h>924 dispositivo correcto y driver, y están etiquetados con el nivel correcto:
1797 .driver = {
277 way will be used only if the test subtantially uses the driver.
3316 .driver = {
3086 .driver = {
3327 .driver = {
2171 .driver = {
1895 .driver = {
2423 .driver = {
2539 .driver = {
223 * used in the gmac_tx clock. The gmac driver will
2005 .driver = {
3081 .driver = {