public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Souradeep Chowdhury <quic_schowdhu@quicinc.com>
To: Masami Hiramatsu <mhiramat@kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Bjorn Andersson <andersson@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-arm-msm@vger.kernel.org>,
	Sai Prakash Ranjan <quic_saipraka@quicinc.com>,
	Sibi Sankar <quic_sibis@quicinc.com>,
	Rajendra Nayak <quic_rjendra@quicinc.com>,
	Souradeep Chowdhury <quic_schowdhu@quicinc.com>
Subject: [PATCH V0 0/1] bootconfig: Increase size and node limit of bootconfig for DCC support
Date: Mon, 9 Jan 2023 20:01:04 +0530	[thread overview]
Message-ID: <cover.1673261071.git.quic_schowdhu@quicinc.com> (raw)

The Data Capture and Compare(DCC) is a debugging tool that uses the bootconfig
for configuring the register values during boot-time. Increased the max size
and nodes supported by bootconfig to catre to the needs of the Data Capture and
Compare Driver. Further details on DCC is available on the below links:-

https://lore.kernel.org/linux-arm-kernel/20221228172825.r32vpphbdulaldvv@builder.lan/T/

https://lore.kernel.org/linux-arm-kernel/cover.1673247689.git.quic_schowdhu@quicinc.com/

Souradeep Chowdhury (1):
  bootconfig: Increase max size of bootconfig from 32 KB to 256 KB for
    DCC support

 include/linux/bootconfig.h | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

--
2.7.4


             reply	other threads:[~2023-01-09 14:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09 14:31 Souradeep Chowdhury [this message]
2023-01-09 14:31 ` [PATCH V0 1/1] bootconfig: Increase max size of bootconfig from 32 KB to 256 KB for DCC support Souradeep Chowdhury
2023-01-09 15:09   ` Bjorn Andersson
2023-01-10 10:57     ` Souradeep Chowdhury
2023-01-09 15:18   ` Masami Hiramatsu
2023-01-10 11:56     ` Souradeep Chowdhury
2023-01-10 14:46       ` Masami Hiramatsu
2023-01-10 15:08         ` Souradeep Chowdhury
2023-01-12  7:01           ` Masami Hiramatsu
2023-01-19 16:51             ` Souradeep Chowdhury
2023-01-19 23:37               ` Masami Hiramatsu

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.1673261071.git.quic_schowdhu@quicinc.com \
    --to=quic_schowdhu@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=quic_rjendra@quicinc.com \
    --cc=quic_saipraka@quicinc.com \
    --cc=quic_sibis@quicinc.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