All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: <linux-clk@vger.kernel.org>, <sboyd@kernel.org>,
	<mturquette@baylibre.com>
Cc: <tomi.valkeinen@ti.com>
Subject: [PATCH 0/4] clk: debugfs: add some simple debug functionality
Date: Tue, 1 Oct 2019 12:01:58 +0300	[thread overview]
Message-ID: <20191001090202.26346-1-t-kristo@ti.com> (raw)

Hi,

I have been using a variation of these patches myself for several years
for debugging / testing different clock issues. Basically what I do here
is extend the functionality of debugfs to allow write access to certain
properties, like rate, enable / prepare counts, mux parents.

This allows simple testing of new features or debugging directly from
userspace. The functionality is hidden behind a Kconfig option because
it can be rather dangerous to allow access to these unconditionally if
the user does not know what they are doing.

Any thoughts?

-Tero


--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

             reply	other threads:[~2019-10-01  9:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01  9:01 Tero Kristo [this message]
2019-10-01  9:01 ` [PATCH 1/4] clk: debug: add support for setting clk_rate from debugfs Tero Kristo
2019-10-01  9:02 ` [PATCH 2/4] clk: debug: add support for enable/disable/prep/un-prep " Tero Kristo
2019-10-01  9:02 ` [PATCH 3/4] clk: ti: mux: add debugfs support for read/write of parent ID Tero Kristo
2019-10-01  9:02 ` [PATCH 4/4] clk: keystone: sci-clk: " Tero Kristo
2019-10-01  9:21 ` [PATCH 0/4] clk: debugfs: add some simple debug functionality Tomi Valkeinen
2020-01-06  3:13 ` Stephen Boyd

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=20191001090202.26346-1-t-kristo@ti.com \
    --to=t-kristo@ti.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=tomi.valkeinen@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.