[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200802115701.GD1162@bug>
Date: Sun, 2 Aug 2020 13:57:01 +0200
From: Pavel Machek <pavel@....cz>
To: Grzegorz Jaszczyk <grzegorz.jaszczyk@...aro.org>
Cc: ssantosh@...nel.org, s-anna@...com, santosh.shilimkar@...cle.com,
robh+dt@...nel.org, lee.jones@...aro.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
wmills@...com, praneeth@...com
Subject: Re: [PATCH 0/6] Add TI PRUSS platform driver
On Sun 2020-08-02 13:53:30, Pavel Machek wrote:
> Hi!
>
> > A typical usage scenario would be to load the application firmware into one or
> > more of the PRU cores, initialize one or more of the peripherals and perform I/O
> > through shared RAM from either a kernel driver or directly from userspace.
> >
> > This series contains the PRUSS platform driver. This is the parent driver for
> > the entire PRUSS and is used for managing the subsystem level resources like
> > various memories and the CFG module. It is responsible for the creation and
> > deletion of the platform devices for the child PRU devices and other child
> > devices (like Interrupt Controller, MDIO node and some syscon nodes) so that
> > they can be managed by specific platform drivers.
>
> > drivers/soc/ti/Kconfig | 11 + drivers/soc/ti/Makefile | 1 + drivers/soc/ti/pruss.c |
>
> Is drivers/soc right place for that? We already have subsystem for various
> programmable accelerators...
....see drivers/remoteproc.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Powered by blists - more mailing lists