public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Rishabh Bhatnagar <rishabhb@codeaurora.org>
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
	tsoni@codeaurora.org, psodagud@codeaurora.org,
	sidgup@codeaurora.org
Subject: Re: [PATCH v3 1/3] remoteproc: Expose remoteproc configuration through sysfs
Date: Thu, 3 Sep 2020 19:04:54 -0500	[thread overview]
Message-ID: <20200904000454.GD3715@yoga> (raw)
In-Reply-To: <1599174226-2307-2-git-send-email-rishabhb@codeaurora.org>

On Thu 03 Sep 18:03 CDT 2020, Rishabh Bhatnagar wrote:

> Add a feature flag to expose some of the remoteproc configuration
> through sysfs. This feature is helpful in systems where debugfs is
> not available/mounted. Currently the recovery and coredump
> configuration is exposed through sysfs rather than debugfs when
> this feature is selected.
> 

This commit message gives me the feeling that it's about making a
selection between debugfs vs sysfs. But the patches moves the code from
debugfs to sysfs and then hide it behind this config option.

That said, I just commented on v2 questioning that this should be a
compile time option at all - might be useful for some drivers to
dynamically "hide" these sysfs attributes though.

Regards,
Bjorn

> Signed-off-by: Rishabh Bhatnagar <rishabhb@codeaurora.org>
> ---
>  drivers/remoteproc/Kconfig | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig
> index c6659dfe..98d52cbe 100644
> --- a/drivers/remoteproc/Kconfig
> +++ b/drivers/remoteproc/Kconfig
> @@ -275,6 +275,17 @@ config TI_K3_DSP_REMOTEPROC
>  	  It's safe to say N here if you're not interested in utilizing
>  	  the DSP slave processors.
>  
> +config RPROC_SYSFS_CONFIGURATION_SUPPORT
> +	bool "Expose remoteproc configuration sysfs entries"
> +	default y
> +	help
> +	  Say y here to expose recovery and coredump configuration sysfs
> +	  entries. This is helpful in operating systems where debugfs is
> +	  not available/mounted.
> +
> +	  It's safe to say N here if you are not interested in accessing
> +	  recovery and coredump configuration through sysfs.
> +
>  endif # REMOTEPROC
>  
>  endmenu
> -- 
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
> 

  reply	other threads:[~2020-09-04  0:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 23:03 [PATCH v3 0/3] Expose recovery/coredump configuration from sysfs Rishabh Bhatnagar
2020-09-03 23:03 ` [PATCH v3 1/3] remoteproc: Expose remoteproc configuration through sysfs Rishabh Bhatnagar
2020-09-04  0:04   ` Bjorn Andersson [this message]
2020-09-04 22:07     ` Mathieu Poirier
2020-09-03 23:03 ` [PATCH v3 2/3] remoteproc: Add coredump configuration to sysfs Rishabh Bhatnagar
2020-09-03 23:03 ` [PATCH v3 3/3] remoteproc: Add recovery " Rishabh Bhatnagar
2020-09-04  7:46 ` [PATCH v3 0/3] Expose recovery/coredump configuration from sysfs Christoph Hellwig

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=20200904000454.GD3715@yoga \
    --to=bjorn.andersson@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=psodagud@codeaurora.org \
    --cc=rishabhb@codeaurora.org \
    --cc=sidgup@codeaurora.org \
    --cc=tsoni@codeaurora.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