Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: <khasim@ti.com>
Cc: <vigneshr@ti.com>, <kristo@kernel.org>, <ada@thorsis.com>,
	<pavel@ucw.cz>, <praneeth@ti.com>, <robh+dt@kernel.org>,
	<devarsht@ti.com>, <s-adivi@ti.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-leds@vger.kernel.org>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-am642-sk: Add DT entry for onboard LEDs
Date: Wed, 6 Jul 2022 18:39:56 -0500	[thread overview]
Message-ID: <20220706233918.dct7emagduy3r22t@preoccupy> (raw)
In-Reply-To: <20220629075859.6939-1-a-m1@ti.com>

On 13:28-20220629, Aparna M wrote:
[...]
>  &main_pmx0 {
> @@ -316,6 +377,14 @@
>  				  "VPP_LDO_EN", "RPI_PS_3V3_En",
>  				  "RPI_PS_5V0_En", "RPI_HAT_DETECT";
>  	};
> +
> +        exp2: gpio@60 {
> +                compatible = "ti,tpic2810";
> +                reg = <0x60>;
> +                gpio-controller;
> +                #gpio-cells = <2>;
> +                gpio-line-names = "LED1","LED2","LED3","LED4","LED5","LED6","LED7","LED8";
> +        };

https://lore.kernel.org/all/CACRpkdbj2B90-RE2XKQJ5qEj1hZQA-u=vUu2vpXwNqQLf_kaPg@mail.gmail.com/

I see Rob and Linus has acked it, but it does'nt belong to TI device
tree queue. and I cannot pick up dts node without the compatible in
master branch in rc1, so I have to skip.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2022-07-06 23:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29  7:58 [PATCH v2] arm64: dts: ti: k3-am642-sk: Add DT entry for onboard LEDs Aparna M
2022-07-06 23:39 ` Nishanth Menon [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=20220706233918.dct7emagduy3r22t@preoccupy \
    --to=nm@ti.com \
    --cc=ada@thorsis.com \
    --cc=devarsht@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=khasim@ti.com \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=praneeth@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=s-adivi@ti.com \
    --cc=vigneshr@ti.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