From: Tony Lindgren <tony@atomide.com>
To: David Lechner <david@lechnology.com>
Cc: linux-omap@vger.kernel.org,
"Benoît Cousson" <bcousson@baylibre.com>,
"Robert Nelson" <robertcnelson@gmail.com>,
"Drew Fustini" <drew@beagleboard.org>,
"Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Enable eQEP counter driver on BeagleBone Blue
Date: Mon, 16 Nov 2020 13:36:58 +0200 [thread overview]
Message-ID: <20201116113658.GE26857@atomide.com> (raw)
In-Reply-To: <20201012211229.3282128-1-david@lechnology.com>
* David Lechner <david@lechnology.com> [201013 00:13]:
> This series adds device tree nodes for the eQEP portion of the PWMSS on AM33xx
> and enables it on BeagleBone Blue.
>
> I actually submitted these a year ago, but it looks like these patches never got
> applied with the actual eQEP driver when it was merged.
Sorry if I dropped these earlier, I guess I though you're reposting the
series and untagged them.
> For reference, there was some previous discussion about the clocks in "ARM: dts:
> am33xx: Add nodes for eQEP". [1]
>
> [1]: https://lore.kernel.org/linux-omap/20190723145100.GS5447@atomide.com/
>
> I have also included a new patch to enable the eQEP driver in the defconfig.
Great, thanks applying these into omap-for-v5.11/dt and defconfig branches.
Regards,
Tony
next prev parent reply other threads:[~2020-11-16 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 21:12 [PATCH 0/3] Enable eQEP counter driver on BeagleBone Blue David Lechner
2020-10-12 21:12 ` [PATCH 1/3] ARM: dts: am33xx: Add nodes for eQEP David Lechner
2020-10-12 21:12 ` [PATCH 2/3] ARM: dts: am335x-boneblue: Enable eQEP David Lechner
2020-10-12 21:12 ` [PATCH 3/3] ARM: omap2plus_defconfig: Enable TI eQEP counter driver David Lechner
2020-11-16 11:36 ` Tony Lindgren [this message]
2020-11-16 14:27 ` [PATCH 0/3] Enable eQEP counter driver on BeagleBone Blue David Lechner
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=20201116113658.GE26857@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=drew@beagleboard.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robertcnelson@gmail.com \
--cc=robh+dt@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).