From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH 05/16] remoteproc/pru: Add pru-specific debugfs support References: <1543218769-5507-1-git-send-email-rogerq@ti.com> <1543218769-5507-6-git-send-email-rogerq@ti.com> From: David Lechner Message-ID: Date: Mon, 26 Nov 2018 16:37:45 -0600 MIME-Version: 1.0 In-Reply-To: <1543218769-5507-6-git-send-email-rogerq@ti.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit To: Roger Quadros , ohad@wizery.com, bjorn.andersson@linaro.org Cc: tony@atomide.com, robh+dt@kernel.org, bcousson@baylibre.com, ssantosh@kernel.org, s-anna@ti.com, nsekhar@ti.com, t-kristo@ti.com, nsaulnier@ti.com, jreeder@ti.com, m-karicheri2@ti.com, woods.technical@gmail.com, linux-omap@vger.kernel.org, linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org List-ID: On 11/26/18 1:52 AM, Roger Quadros wrote: > From: Suman Anna > > 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.