From: Leonard Crestez <leonard.crestez@nxp.com>
To: Stephen Boyd <sboyd@kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] scripts/gdb: Initial clk support
Date: Mon, 22 Apr 2019 08:26:56 +0000 [thread overview]
Message-ID: <cover.1555921081.git.leonard.crestez@nxp.com> (raw)
Tested with openocd on imx but should be useful everywhere. It is common
for clk issues to lockup the system and make /sys inaccesible.
Not sure where to send this; there doesn't appear to be any list more
specific than LKML.
Leonard Crestez (3):
scripts/gdb: Add hlist utilities
scripts/gdb: Initial clk support: lx-clk-summary
scripts/gdb: Add $lx_clk_core_lookup function
scripts/gdb/linux/clk.py | 69 ++++++++++++++++++++++++++++++++++++++
scripts/gdb/linux/lists.py | 23 +++++++++++++
scripts/gdb/vmlinux-gdb.py | 1 +
3 files changed, 93 insertions(+)
create mode 100644 scripts/gdb/linux/clk.py
--
2.17.1
next reply other threads:[~2019-04-22 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 8:26 Leonard Crestez [this message]
2019-04-22 8:26 ` [PATCH 1/3] scripts/gdb: Add hlist utilities Leonard Crestez
2019-04-22 20:41 ` Stephen Boyd
2019-04-23 9:20 ` Leonard Crestez
2019-04-22 8:26 ` [PATCH 2/3] scripts/gdb: Initial clk support: lx-clk-summary Leonard Crestez
2019-04-22 20:22 ` Stephen Boyd
2019-04-22 8:26 ` [PATCH 3/3] scripts/gdb: Add $lx_clk_core_lookup function Leonard Crestez
[not found] ` <155596430227.15276.13435242792506854365@swboyd.mtv.corp.google.com>
2019-04-23 11:12 ` Leonard Crestez
2019-04-23 18:16 ` Stephen Boyd
2019-04-22 20:40 ` [PATCH 0/3] scripts/gdb: Initial clk support 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=cover.1555921081.git.leonard.crestez@nxp.com \
--to=leonard.crestez@nxp.com \
--cc=akpm@linux-foundation.org \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@kernel.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
Powered by JetHome