From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: lee@kernel.org, sean.wang@mediatek.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, matthias.bgg@gmail.com,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH v2 0/7] Add support for MT6331 and MT6332 LEDs
Date: Thu, 13 Apr 2023 13:31:29 +0200 [thread overview]
Message-ID: <dee54623-9065-98e7-0505-bdb08ec1e643@collabora.com> (raw)
In-Reply-To: <ZDfeKhUvo5a9jd9E@duo.ucw.cz>
Il 13/04/23 12:49, Pavel Machek ha scritto:
> Hi!
>
>> Changes in v2:
>> - Rebase over next-20230412
>>
>> NOTE: Since v1 of this series was sent in Semptember 2022 and got
>> ignored for *7 months* with no feedback, I'm retrying the upstreaming
>> of this same series.
>> There are no changes, if not just a simple rebase and another test
>> run on the same hardware.
>>
>>
>> MT6323 is not the only PMIC that has a LEDs controller IP and it was
>> found that the others do have a compatible register layout, except
>> for some register offsets.
>> The logic contained in this driver can be totally reused for other
>> PMICs as well, so I can't see any reason to keep this specific to
>> the MT6323 part.
>>
>> This series brings meaningful platform data to this driver, giving
>> it flexibility and adding support for LED controllers found in the
>> MT6331 and MT6332 PMICs.
>>
>> Tested on MT6795 Sony Xperia M5 smartphone.
>
> Please cc phone-devel with phone related stuff.
Sorry, I completely forgot to :-(
>
> Can I get ls /sys/class/leds on that machine?
Yes you can, but that will require some time, as I'm on other tasks.
I should be able to provide that next week, sorry for the delay!
Regards,
Angelo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-04-13 11:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 15:33 [PATCH v2 0/7] Add support for MT6331 and MT6332 LEDs AngeloGioacchino Del Regno
2023-04-12 15:33 ` [PATCH v2 1/7] dt-bindings: leds: leds-mt6323: Document mt6331 compatible AngeloGioacchino Del Regno
2023-04-13 8:35 ` Alexandre Mergnat
2023-04-12 15:33 ` [PATCH v2 2/7] dt-bindings: leds: leds-mt6323: Document mt6332 compatible AngeloGioacchino Del Regno
2023-04-13 8:35 ` Alexandre Mergnat
2023-04-13 10:47 ` Pavel Machek
2023-04-12 15:33 ` [PATCH v2 3/7] leds: leds-mt6323: Specify registers and specs in platform data AngeloGioacchino Del Regno
2023-04-13 10:11 ` Alexandre Mergnat
2023-04-13 10:57 ` Pavel Machek
2023-04-12 15:33 ` [PATCH v2 4/7] leds: leds-mt6323: Open code and drop MT6323_CAL_HW_DUTY macro AngeloGioacchino Del Regno
2023-04-13 13:06 ` Alexandre Mergnat
2023-04-12 15:33 ` [PATCH v2 5/7] leds: leds-mt6323: Drop MT6323_ prefix from macros and defines AngeloGioacchino Del Regno
2023-04-13 10:59 ` Pavel Machek
2023-04-13 13:41 ` Alexandre Mergnat
2023-04-12 15:33 ` [PATCH v2 6/7] leds: leds-mt6323: Add support for MT6331 leds AngeloGioacchino Del Regno
2023-04-13 11:01 ` Pavel Machek
2023-04-13 13:19 ` Alexandre Mergnat
2023-04-12 15:33 ` [PATCH v2 7/7] leds: leds-mt6323: Add support for WLEDs and MT6332 AngeloGioacchino Del Regno
2023-04-13 11:06 ` Pavel Machek
2023-04-13 11:29 ` AngeloGioacchino Del Regno
2023-04-13 11:32 ` AngeloGioacchino Del Regno
2023-04-14 7:07 ` Lee Jones
2023-04-14 7:09 ` AngeloGioacchino Del Regno
2023-04-13 14:15 ` Alexandre Mergnat
2023-04-14 10:19 ` AngeloGioacchino Del Regno
2023-04-13 10:49 ` [PATCH v2 0/7] Add support for MT6331 and MT6332 LEDs Pavel Machek
2023-04-13 11:31 ` AngeloGioacchino Del Regno [this message]
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=dee54623-9065-98e7-0505-bdb08ec1e643@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.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