Linux LED subsystem development
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Nam Tran <trannamatk@gmail.com>
Cc: pavel@kernel.org, devicetree@vger.kernel.org,
	conor+dt@kernel.org,  corbet@lwn.net,
	linux-kernel@vger.kernel.org, lee@kernel.org,
	 linux-leds@vger.kernel.org, krzk+dt@kernel.org
Subject: Re: [PATCH v4 0/5] leds: add new LED driver for TI LP5812
Date: Mon, 07 Apr 2025 07:47:56 -0500	[thread overview]
Message-ID: <174402971830.1782904.14648060042339616468.robh@kernel.org> (raw)
In-Reply-To: <20250405183246.198568-1-trannamatk@gmail.com>


On Sun, 06 Apr 2025 01:32:41 +0700, Nam Tran wrote:
> This patch series adds support for the Texas Instruments LP5812 LED driver.
> Patch 1 adds the Device Tree (DT) bindings documentation.
> Patch 2 introduces the core driver implementation.
> Patch 3 adds documentation of sysfs ABI interfaces.
> Patch 4 adds Driver documentation in reStructuredText format.
> Patch 5 adds the LP5812 device tree node for Raspberry Pi 4B.
> 
> Changes in v4:
> - Merge leds-lp5812-common.c into leds-lp5812.c
> - Implemented the core of aeu_pwm[1-4]_{store, show}()
> - Used kstrdup() instead of kmalloc() for allocating characters array
> - Add sysfs ABI documentation
> - Updated device tree binding documentation
> 
> Best regards,
> Nam
> 
> 


My bot found new DTB warnings on the .dts files added or changed in this
series.

Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.

If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:

  pip3 install dtschema --upgrade


This patch series was applied (using b4) to base:
 Base: attempting to guess base-commit...
 Base: tags/v6.14-1107-g406fad7698f5 (exact match)

If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)

New warnings running 'make CHECK_DTBS=y for arch/arm/boot/dts/broadcom/' for 20250405183246.198568-1-trannamatk@gmail.com:

arch/arm/boot/dts/broadcom/bcm2836-rpi-2-b.dtb: /soc/i2s@7e203000: failed to match any schema with compatible: ['brcm,bcm2835-i2s']






      parent reply	other threads:[~2025-04-07 12:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-05 18:32 [PATCH v4 0/5] leds: add new LED driver for TI LP5812 Nam Tran
2025-04-05 18:32 ` [PATCH v4 1/5] dt-bindings: leds: add TI/National Semiconductor LP5812 LED Driver Nam Tran
2025-04-06 11:59   ` Krzysztof Kozlowski
2025-04-10 15:59     ` Nam Tran
2025-04-05 18:32 ` [PATCH v4 2/5] " Nam Tran
2025-04-06 22:35   ` kernel test robot
2025-04-05 18:32 ` [PATCH v4 3/5] docs: ABI: Document LP5812 LED sysfs interfaces Nam Tran
2025-04-06 12:08   ` Krzysztof Kozlowski
2025-04-10 16:25     ` Nam Tran
2025-04-05 18:32 ` [PATCH v4 4/5] docs: leds: Document TI LP5812 LED driver Nam Tran
2025-04-05 18:32 ` [PATCH v4 5/5] arm64: dts: Add LP5812 LED node for Raspberry Pi 4 Model B Nam Tran
2025-04-07 12:47 ` Rob Herring (Arm) [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=174402971830.1782904.14648060042339616468.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@kernel.org \
    --cc=trannamatk@gmail.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