From: Andrew Davis <afd@ti.com>
To: Robert Nelson <robertcnelson@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jason Kridner <jkridner@beagleboard.org>,
Drew Fustini <drew@beagleboard.org>,
Tony Lindgren <tony@atomide.com>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] uio: pruss: Deprecate use of this driver
Date: Tue, 26 Mar 2024 12:36:46 -0500 [thread overview]
Message-ID: <ceb391d3-c7f4-4d46-9f97-b651e1f5451c@ti.com> (raw)
In-Reply-To: <ZgME0qSL3KXCD07I@chinchilla>
On 3/26/24 12:24 PM, Matthijs van Duin wrote:
> I'll write a more in-depth reply when I have a moment, but right now I'd
> like to point out that the uio-pruss driver in mainline linux is for the
> pru subsystem on the freon/primus family of ARM9-based SoCs (OMAP-L1xx /
> AM17xx / AM18xx / TMS320C674x / DA8xx), which is not currently supported
> by remoteproc-pru.
>
I'll wait for your full reply, but a quick note, for those devices listed
this driver isn't usable either after they all moved to DT. As this driver
never got a DT port and relies on platform data (which is gone for those
couple devices).
Andrew
next prev parent reply other threads:[~2024-03-26 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 21:00 [PATCH] uio: pruss: Deprecate use of this driver Andrew Davis
2024-03-26 5:41 ` Greg Kroah-Hartman
2024-03-26 16:19 ` Robert Nelson
2024-03-26 17:02 ` Andrew Davis
2024-03-26 17:12 ` Greg Kroah-Hartman
2024-03-26 17:32 ` Robert Nelson
2024-03-26 17:34 ` Andrew Davis
2024-03-26 17:36 ` Matthijs van Duin
2024-03-26 17:24 ` Matthijs van Duin
2024-03-26 17:36 ` Andrew Davis [this message]
2024-03-26 18:18 ` Matthijs van Duin
2024-04-05 15:39 ` Robert Nelson
2024-04-10 14:47 ` Andrew Davis
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=ceb391d3-c7f4-4d46-9f97-b651e1f5451c@ti.com \
--to=afd@ti.com \
--cc=drew@beagleboard.org \
--cc=gregkh@linuxfoundation.org \
--cc=jkridner@beagleboard.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robertcnelson@gmail.com \
--cc=tony@atomide.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