public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: <linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Jon Hunter <jonathanh@nvidia.com>
Subject: [PATCH 0/5] firmware: tegra: Add support for in-band debug
Date: Sun, 12 Jul 2020 11:01:13 +0100	[thread overview]
Message-ID: <20200712100118.13343-1-jonathanh@nvidia.com> (raw)

This series adds support for in-band debug messaging for the BPMP and
updates the BPMP ABI to align with the latest version.

Jon Hunter (4):
  firmware: tegra: Use consistent return variable name
  firmware: tegra: Prepare for supporting in-band debugfs
  firmware: tegra: Add support for in-band debug
  firmware: tegra: Update BPMP ABI

Timo Alho (1):
  firmware: tegra: add return code checks and increase debugfs size

 drivers/firmware/tegra/bpmp-debugfs.c | 436 ++++++++++--
 drivers/firmware/tegra/bpmp.c         |   6 +-
 include/soc/tegra/bpmp-abi.h          | 913 ++++++++++++++++++--------
 3 files changed, 1038 insertions(+), 317 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-07-12 10:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-12 10:01 Jon Hunter [this message]
2020-07-12 10:01 ` [PATCH 1/5] firmware: tegra: add return code checks and increase debugfs size Jon Hunter
2020-07-12 10:01 ` [PATCH 2/5] firmware: tegra: Use consistent return variable name Jon Hunter
2020-07-12 10:01 ` [PATCH 3/5] firmware: tegra: Prepare for supporting in-band debugfs Jon Hunter
2020-07-12 10:01 ` [PATCH 4/5] firmware: tegra: Add support for in-band debug Jon Hunter
2020-07-12 10:01 ` [PATCH 5/5] firmware: tegra: Update BPMP ABI Jon Hunter
2020-07-14 16:18 ` [PATCH 0/5] firmware: tegra: Add support for in-band debug Thierry Reding
2020-07-14 18:12   ` Jon Hunter

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=20200712100118.13343-1-jonathanh@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox