[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d0e227e3-39dc-dfc8-b94c-3d9d072f6562@lechnology.com>
Date: Mon, 26 Nov 2018 16:37:45 -0600
From: David Lechner <david@...hnology.com>
To: Roger Quadros <rogerq@...com>, ohad@...ery.com,
bjorn.andersson@...aro.org
Cc: tony@...mide.com, robh+dt@...nel.org, bcousson@...libre.com,
ssantosh@...nel.org, s-anna@...com, nsekhar@...com,
t-kristo@...com, nsaulnier@...com, jreeder@...com,
m-karicheri2@...com, woods.technical@...il.com,
linux-omap@...r.kernel.org, linux-remoteproc@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 05/16] remoteproc/pru: Add pru-specific debugfs support
On 11/26/18 1:52 AM, Roger Quadros wrote:
> From: Suman Anna <s-anna@...com>
>
> The remoteproc core creates certain standard debugfs entries,
> that does not give a whole lot of useful information for the
> PRUs. The PRU remoteproc driver is enhanced to add additional
> debugfs entries for PRU. These will be auto-cleaned up when
> the parent rproc debug directory is removed.
>
> The enhanced debugfs support adds two new entries: 'regs' and
> 'single_step'. The 'regs' dumps out the useful CTRL sub-module
> registers as well as each of the 32 GPREGs and CT_REGs registers.
> The GPREGs and CT_REGs though are printed only when the PRU is
> halted and accessible as per the IP design.
>
If the driver used regmap to access the CTRL I/O memory, then
'regs' wouldn't be needed since regmap already does debugfs.
Powered by blists - more mailing lists