From: William Breathitt Gray <wbg@kernel.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Nishanth Menon <nm@ti.com>,
Judith Mendez <jm@ti.com>
Cc: William Breathitt Gray <wbg@kernel.org>,
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 0/8] Enable eQEP DT support for Sitara K3 platforms
Date: Mon, 1 Jul 2024 11:38:54 +0900 [thread overview]
Message-ID: <171980147646.3245330.16378344874755104998.b4-ty@kernel.org> (raw)
In-Reply-To: <20240612135538.2447938-1-jm@ti.com>
On Wed, 12 Jun 2024 08:55:30 -0500, Judith Mendez wrote:
> This patch series adds eQEP DT nodes for K3 Sitara devices:
> - AM62x
> - AM62ax
> - AM62px
> - AM64x
>
> The series also allows the eQEP driver to be built for K3
> architecture.
>
> [...]
Applied, thanks!
[1/8] dt-bindings: counter: Add new ti,am62-eqep compatible
commit: 151ebcf0797b1a3ba53c8843dc21748c80e098c7
[2/8] counter/ti-eqep: Add new ti-am62-eqep compatible
commit: 210457b651acd61fced405cf7fef12a482932ca1
[3/8] arm64: dts: ti: k3-am62-main: Add eQEP nodes
commit: e2e1fce199b0db4fd4eba99ff6ef779826a55731
[4/8] arm64: dts: ti: k3-am62a-main: Add eQEP nodes
commit: ba5a251b1d539a82970823dd510ee25be06d6ca7
[5/8] arm64: dts: ti: k3-am62p-main: Add eQEP nodes
commit: 131eaf47c4c5ad444e3a0547960daacd3a40f82d
[6/8] arm64: dts: ti: k3-am64-main: Add eQEP nodes
commit: afdfe6439a6d28a3062d576705b203da0857699f
[7/8] arm64: dts: ti: k3-am64x-sk: Enable eQEP
commit: 7fb9d8854fcf23b7882a34a4cf247a7f60d02fef
[8/8] counter: ti-eqep: Allow eQEP driver to be built for K3 devices
commit: 474bbfc637c719daebffb5cabcf914dd749cf393
Best regards,
--
William Breathitt Gray <wbg@kernel.org>
prev parent reply other threads:[~2024-07-01 2:39 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
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 ` William Breathitt Gray [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=171980147646.3245330.16378344874755104998.b4-ty@kernel.org \
--to=wbg@kernel.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=krzysztof.kozlowski@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 \
/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