[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1524672945.21176.594.camel@linux.intel.com>
Date: Wed, 25 Apr 2018 19:15:45 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Javier Arteaga <javier@...tex.com>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Pavel Machek <pavel@....cz>
Cc: Dan O'Donovan <dan@...tex.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Lee Jones <lee.jones@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>,
linux-gpio@...r.kernel.org, linux-leds@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH RESEND 2/3] leds: upboard: Add LED support
On Sat, 2018-04-21 at 09:50 +0100, Javier Arteaga wrote:
> Allow userspace to use the on-board LEDs as "upboard:<color>:".
> + struct upboard_led *led = container_of(cdev, struct
> upboard_led, cdev);
#define to_upboard_led(cdev) container_of(cdev, struct upboard_led,
cdev)
... led = to_upboard_led(cdev);
> + struct upboard_led *led = container_of(cdev, struct
> upboard_led, cdev);
Ditto.
> +static int __init upboard_led_probe(struct platform_device *pdev)
Are you sure about __init here?
> + struct upboard_led_data * const pdata = pdev-
> >dev.platform_data;
Don't use direct dereference to platform_data.
> + if (!pdev->dev.parent)
> + return -EINVAL;
> +
> + upboard = dev_get_drvdata(pdev->dev.parent);
> + if (!upboard || !pdata)
> + return -EINVAL;
Wouldn't be better to supply regmap as part of platform data?
It will allow be flexible of parent device.
> +MODULE_LICENSE("GPL");
License mismatch.
--
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy
Powered by blists - more mailing lists