From: Leonard Crestez <leonard.crestez@nxp.com>
To: Stephen Boyd <sboyd@kernel.org>,
Kieran Bingham <kbingham@kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michael Turquette <mturquette@baylibre.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] gdb/scripts: Improve lx-clk-summary
Date: Fri, 3 May 2019 11:19:30 +0000 [thread overview]
Message-ID: <cover.1556881728.git.leonard.crestez@nxp.com> (raw)
The earlier series adding clk support to gdb/scripts was quickly
accepted but some concerns were raised by Stephen Boyd so this series
attempts to address them.
Link to previous series: https://lkml.org/lkml/2019/4/22/55
This is not a v2 and squashing is not expected.
Fields other than clk rate not covered because they're much more rarely
used and cache logic can get more complicated and brittle.
LX_GDBPARSED is used in constants.py.in because python does not
understand C integer literal suffixes like the "1UL" from the definition
of BIT() used by CLK_GET_RATE_NOCACHE. Alternative workarounds would be
hacking away UL suffixes with sed or redefining BIT&co but relying on
gdb evaluation is easier and much more flexible.
Leonard Crestez (2):
scripts/gdb: Cleanup error handling in list helpers
scripts/gdb: Print cached rate in lx-clk-summary
scripts/gdb/linux/clk.py | 21 ++++++++++++++-------
scripts/gdb/linux/constants.py.in | 4 ++++
scripts/gdb/linux/lists.py | 10 ++--------
3 files changed, 20 insertions(+), 15 deletions(-)
--
2.17.1
next reply other threads:[~2019-05-03 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 11:19 Leonard Crestez [this message]
2019-05-03 11:19 ` [PATCH 1/2] scripts/gdb: Cleanup error handling in list helpers Leonard Crestez
2019-05-03 16:33 ` Stephen Boyd
2019-05-03 11:19 ` [PATCH 2/2] scripts/gdb: Print cached rate in lx-clk-summary Leonard Crestez
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.1556881728.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-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--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