From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: William Breathitt Gray <wbg@kernel.org>
Cc: Rob Herring <robh@kernel.org>, Judith Mendez <jm@ti.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Nishanth Menon <nm@ti.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>,
linux-arm-kernel@lists.infradead.org,
David Lechner <david@lechnology.com>
Subject: Re: [PATCH v5 1/8] dt-bindings: counter: Add new ti,am62-eqep compatible
Date: Thu, 27 Jun 2024 09:31:23 +0200 [thread overview]
Message-ID: <a3813504-4b6b-4e3f-ad9d-c93841a13b52@linaro.org> (raw)
In-Reply-To: <ZnyZTq0rEFP_eWCw@ishi>
On 27/06/2024 00:42, William Breathitt Gray wrote:
> On Wed, Jun 12, 2024 at 08:55:31AM -0500, Judith Mendez wrote:
>> Add new compatible ti,am62-eqep for TI K3 devices. If a device
>> uses this compatible, require power-domains property.
>>
>> Since there is only one functional and interface clock for eqep,
>> clock-names is not really required, so removed from required
>> section, make it optional for ti,am3352-eqep compatible, and
>> update the example.
>>
>> The clock-name also changed for TI K3 SoCs so do not allow
>> clock-names property for the new compatible.
>>
>> Signed-off-by: Judith Mendez <jm@ti.com>
>> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>> Reviewed-by: David Lechner <david@lechnology.com>
>> ---
>> Changes since v4:
>> - Drop the new example from binding
>> ---
>
> Hi Krzysztof,
>
> Are you satisfied with the changes made for this version of the patch?
I did not check, because it already has an Ack from Conor. I am usually
not double-acking, but FWIW:
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-06-27 7:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 13:55 [PATCH v5 0/8] Enable eQEP DT support for Sitara K3 platforms Judith Mendez
2024-06-12 13:55 ` [PATCH v5 1/8] dt-bindings: counter: Add new ti,am62-eqep compatible Judith Mendez
2024-06-26 22:42 ` William Breathitt Gray
2024-06-27 7:31 ` Krzysztof Kozlowski [this message]
2024-06-12 13:55 ` [PATCH v5 2/8] counter/ti-eqep: Add new ti-am62-eqep compatible Judith Mendez
2024-06-12 13:55 ` [PATCH v5 3/8] arm64: dts: ti: k3-am62-main: Add eQEP nodes Judith Mendez
2024-06-12 13:55 ` [PATCH v5 4/8] arm64: dts: ti: k3-am62a-main: " Judith Mendez
2024-06-12 13:55 ` [PATCH v5 5/8] arm64: dts: ti: k3-am62p-main: " Judith Mendez
2024-06-12 13:55 ` [PATCH v5 6/8] arm64: dts: ti: k3-am64-main: " Judith Mendez
2024-06-12 13:55 ` [PATCH v5 7/8] arm64: dts: ti: k3-am64x-sk: Enable eQEP Judith Mendez
2024-06-12 13:55 ` [PATCH v5 8/8] counter: ti-eqep: Allow eQEP driver to be built for K3 devices Judith Mendez
2024-07-01 2:38 ` [PATCH v5 0/8] Enable eQEP DT support for Sitara K3 platforms William Breathitt Gray
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=a3813504-4b6b-4e3f-ad9d-c93841a13b52@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=jm@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
--cc=wbg@kernel.org \
/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).