[PATCH v4 2/2] leds: mt6360: Add LED driver for MT6360

[Jacek Anaszewski]

On 9/24/20 8:21 AM, Gene Chen wrote:
> Jacek Anaszewski <jacek.anaszewski at gmail.com> 於 2020年9月24日 週四 上午5:49寫道：
> 
>>
>> Hi Gene,
>>
>> Thank you for the update. I have some more comments below.
>>
>> On 9/23/20 2:50 PM, Gene Chen wrote:
>>> From: Gene Chen <gene_chen at richtek.com>
>>>
>>> Add MT6360 LED driver include 2-channel Flash LED with torch/strobe mode,
>>> and 4-channel RGB LED support Register/Flash/Breath Mode
>>>
>>> Signed-off-by: Gene Chen <gene_chen at richtek.com>
>>> ---
>>>    drivers/leds/Kconfig       |  11 +
>>>    drivers/leds/Makefile      |   1 +
>>>    drivers/leds/leds-mt6360.c | 705 +++++++++++++++++++++++++++++++++++++++++++++
>>>    3 files changed, 717 insertions(+)
>>>    create mode 100644 drivers/leds/leds-mt6360.c
>>>
>>> diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
>>> index 1c181df..5561b08 100644
>>> --- a/drivers/leds/Kconfig
>>> +++ b/drivers/leds/Kconfig
>>> @@ -271,6 +271,17 @@ config LEDS_MT6323
>>>          This option enables support for on-chip LED drivers found on
>>>          Mediatek MT6323 PMIC.
>>>
>>> +config LEDS_MT6360
>>> +     tristate "LED Support for Mediatek MT6360 PMIC"
>>> +     depends on LEDS_CLASS_FLASH && OF
>>> +     depends on V4L2_FLASH_LED_CLASS || !V4L2_FLASH_LED_CLASS
>>> +     depends on MFD_MT6360
>>> +     help
>>> +       This option enables support for dual Flash LED drivers found on
>>> +       Mediatek MT6360 PMIC.
>>> +       Independent current sources supply for each flash LED support torch
>>> +       and strobe mode.
>>> +
>>>    config LEDS_S3C24XX
>>>        tristate "LED Support for Samsung S3C24XX GPIO LEDs"
>>>        depends on LEDS_CLASS
>>> diff --git a/drivers/leds/Makefile b/drivers/leds/Makefile
>>> index c2c7d7a..5596427 100644
>>> --- a/drivers/leds/Makefile
>>> +++ b/drivers/leds/Makefile
>>> @@ -66,6 +66,7 @@ obj-$(CONFIG_LEDS_MIKROTIK_RB532)   += leds-rb532.o
>>>    obj-$(CONFIG_LEDS_MLXCPLD)          += leds-mlxcpld.o
>>>    obj-$(CONFIG_LEDS_MLXREG)           += leds-mlxreg.o
>>>    obj-$(CONFIG_LEDS_MT6323)           += leds-mt6323.o
>>> +obj-$(CONFIG_LEDS_MT6360)            += leds-mt6360.o
>>>    obj-$(CONFIG_LEDS_NET48XX)          += leds-net48xx.o
>>>    obj-$(CONFIG_LEDS_NETXBIG)          += leds-netxbig.o
>>>    obj-$(CONFIG_LEDS_NIC78BX)          += leds-nic78bx.o
>>> diff --git a/drivers/leds/leds-mt6360.c b/drivers/leds/leds-mt6360.c
>>> new file mode 100644
>>> index 0000000..1c3486e
>>> --- /dev/null
>>> +++ b/drivers/leds/leds-mt6360.c
>>> @@ -0,0 +1,705 @@
>>> +// SPDX-License-Identifier: GPL-2.0-only
>>> +
>>> +#include <linux/delay.h>
>>> +#include <linux/init.h>
>>> +#include <linux/interrupt.h>
>>> +#include <linux/kernel.h>
>>> +#include <linux/led-class-flash.h>
>>> +#include <linux/module.h>
>>> +#include <linux/platform_device.h>
>>> +#include <linux/property.h>
>>> +#include <linux/regmap.h>
>>> +#include <media/v4l2-flash-led-class.h>
>>> +
>>> +enum {
>>> +     MT6360_LED_ISNK1 = 0,
>>> +     MT6360_LED_ISNK2,
>>> +     MT6360_LED_ISNK3,
>>> +     MT6360_LED_ISNK4,
>>
>> One question about these ISINKs - how are they exploited in your device?
>> Are these LEDs used to indicate camera activity or it is one RGB LED
>> for status? And what functionality has the remaining amber one (sticking
>> to the naming from your DT bindings)?
>>
>> Can you share how the documenation for this device describes the purpose
>> of these sinks, if it does it at all?
>>
>> I got probably mislead by your naming in the driver and got fixed on
>> their function as camera activity indicators, for which V4L2 has
>> support. If that is not the case, then you'd better switch to using
>> multicolor framework for all four "indicator" LEDs.
>>
> 
> It's one RGB LED for status, not for camera.
> 
> The MT6360 integrates a three-channel RGB LED driver, designed to
> provide a variety of lighting effects for mobile device applications.
> The RGB LED driver includes a smart LED string controller, and it can
> drive 3 channels of LEDs with a sink current of up to 24mA. The
> default setting of RGB_ISINK1 is auto mode for TA charging indicator,
> and RGB_ISINK1 also supports software mode. It provides three
> operation modes for the RGB LEDs: flash mode, breath mode, and
> register mode. The device can increase or decrease the brightness of
> the RGB LEDs upon command via the I2C interface. The RGB_ISINK4
> provide more sink current up to 150mA, which we can moonlight mode.
> 
> Do you mean we should remove "isink register v4l2 device, only need
> register ledclass device"?

I'd say that in addition to the LED flash class device, you should
allow for registering LED multicolor device comprising RGB LEDs,
and one LED class device for ISINK4 (you could even add
LED_FUNCTION_MOONLIGHT for it).

I wonder what others think.

[...]
>>> +static int mt6360_led_probe(struct platform_device *pdev)
>>> +{
>>> +     struct mt6360_priv *priv;
>>> +     struct fwnode_handle *child;
>>> +     size_t count;
>>> +     int i = 0, ret;
>>> +
>>> +     count = device_get_child_node_count(&pdev->dev);
>>> +     if (!count || count > MT6360_MAX_LEDS)
>>
>> Please add dev_err() here.
>>
> 
> dev_err(&pdev->dev, "No child node or node count over max led number
> %d\n", count);

If we will exploit also LED multicolor class then DT bindings will
look different, so let's discuss this detail later.

-- 
Best regards,
Jacek Anaszewski