From: Trilok Soni <tsoni@codeaurora.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
rtc-linux@googlegroups.com, linux-arm-msm@vger.kernel.org,
Richard Purdie <rpurdie@rpsys.net>
Subject: Re: [RFC v1 PATCH 3/6] led: pmic8058: Add PMIC8058 leds driver
Date: Mon, 06 Dec 2010 19:14:23 +0530 [thread overview]
Message-ID: <4CFCE8B7.8080305@codeaurora.org> (raw)
In-Reply-To: <4CDBDE5D.4040801@codeaurora.org>
Hi Peter,
>
>>> +
>>> +/**
>>> + * struct pmic8058_led - per led data
>>> + * @name - name of the led
>>> + * @default_trigger - default trigger which needs to e attached
>>> + * @max_brightness - maximum brightness level supported by the led
>>> + * @id - supported led id
>>> + */
>>> +struct pmic8058_led {
>>> + const char *name;
>>> + const char *default_trigger;
>>> + unsigned max_brightness;
>> Should max_brightness not rather be hardcoded in the driver? As far as I can tell it
>> depend on the hardware and is 4 bits wide for flash and bl leds and 5 bits for the
>> others.
>>> + int id;
>>
>> enum pmic8058_leds instead of int
>
> Ack.
>
>>> +struct pmic8058_leds_platform_data {
>>> + int num_leds;
>> size_t
>
> Ack.
>
>>> + struct pmic8058_led *leds;
>>> +};
>>
>>
>> If max_brightness is hardcoded in the driver you can reuse "struct led_info" and
>> "struct struct led_platform_data" instead of adding your own structs.
>
I couldn't remove these pmic8058_led structure due to the "enum pmic8058_led id" member
info which I need from every led. This can be removed completely only if I abuse
the "flags" parameter in struct led_info to pass the led id. Let me know what you think.
---Trilok Soni
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2010-12-06 13:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 12:47 [RFC v1 PATCH 0/6] Qualcomm PMIC8058 sub-device drivers Trilok Soni
2010-11-10 12:47 ` [RFC v1 PATCH 1/6] matrix_keypad: Increase the max limit of rows and columns Trilok Soni
2010-11-10 18:33 ` Eric Miao
2010-11-10 23:30 ` Dmitry Torokhov
2010-11-17 17:54 ` Dmitry Torokhov
2010-11-10 12:47 ` [RFC v1 PATCH 2/6] input: pm8058_keypad: Qualcomm PMIC8058 keypad controller driver Trilok Soni
2010-11-16 3:49 ` Trilok Soni
2010-11-17 18:02 ` Dmitry Torokhov
2010-12-06 18:14 ` Dmitry Torokhov
2010-12-07 9:22 ` Trilok Soni
2010-12-07 9:30 ` Dmitry Torokhov
2010-12-07 9:32 ` Trilok Soni
2011-01-06 11:56 ` [rtc-linux] " Anirudh Ghayal
2010-11-10 12:47 ` [RFC v1 PATCH 3/6] led: pmic8058: Add PMIC8058 leds driver Trilok Soni
2010-11-10 20:45 ` Lars-Peter Clausen
2010-11-10 23:28 ` Dmitry Torokhov
2010-11-10 23:50 ` Lars-Peter Clausen
2010-11-11 12:15 ` Trilok Soni
2010-12-06 13:44 ` Trilok Soni [this message]
2010-12-07 15:11 ` Lars-Peter Clausen
2010-12-07 15:47 ` Trilok Soni
2010-11-10 12:47 ` [RFC v1 PATCH 4/6] input: pmic8058_pwrkey: Add support for power key Trilok Soni
2010-11-11 7:21 ` Dmitry Torokhov
2010-11-11 12:00 ` Trilok Soni
2010-11-12 0:57 ` Dmitry Torokhov
2010-11-12 8:56 ` Trilok Soni
2010-11-12 19:58 ` Dmitry Torokhov
2010-11-10 12:48 ` [RFC v1 PATCH 5/6] input: pmic8058-othc: Add support for PM8058 based OTHC Trilok Soni
2010-11-16 3:08 ` Trilok Soni
2010-11-16 5:36 ` Datta, Shubhrajyoti
2010-11-16 6:36 ` Trilok Soni
2010-12-01 5:34 ` Anirudh Ghayal
2010-12-07 10:04 ` Dmitry Torokhov
2010-12-07 12:10 ` Anirudh Ghayal
2010-11-10 12:48 ` [RFC v1 PATCH 6/6] drivers: rtc: Add support for Qualcomm PMIC8058 RTC Trilok Soni
2010-11-12 8:53 ` Trilok Soni
2010-11-12 12:53 ` Lars-Peter Clausen
2010-11-12 15:17 ` [rtc-linux] " Anirudh Ghayal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CFCE8B7.8080305@codeaurora.org \
--to=tsoni@codeaurora.org \
--cc=lars@metafoo.de \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=rtc-linux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).