Abstract and PDF here:
https://lpc.events/event/17/contributions/1468/
Video:
https://www.youtube.com/watch?v=3vL3gtAu84s
Patch 1 deals in detail documentation on minidump.
Patch 2-4 refactors minidump existing layout and separate it from remoteproc
files.
Patch 6 is the Qualcomm APSS minidump d
Add the qualcomm minidump guide for the users which tries to cover
the dependency, API use and the way to test and collect minidump
on Qualcomm supported SoCs.
Signed-off-by: Mukesh Ojha
Reviewed-by: Bagas Sanjaya
---
Documentation/admin-guide/index.rst | 1 +
Documentation/admin-guid
Add qcom_rproc_minidump module in a preparation to remove
minidump specific code from driver/remoteproc/qcom_common.c
and provide needed exported API, this as well helps to
abstract minidump specific data layout from qualcomm's
remoteproc driver.
It is just a copying of qcom_minidump() functionali
Now, as all the minidump specific data structure is moved to
minidump specific files and implementation wise qcom_rproc_minidump()
and qcom_minidump() exactly same and the name qcom_rproc_minidump
make more sense as it happen to collect the minidump for the
remoteproc processors. So, let's use qcom
As minidump specific data structure and functions move under
config QCOM_RPROC_MINIDUMP, so remove minidump specific data
from driver/remoteproc/qcom_common.c .
Signed-off-by: Mukesh Ojha
---
drivers/remoteproc/qcom_common.c | 160 ---
1 file changed, 160 deletions(-)
Some debug loadable module like minidump is interested in knowing
the kernel version against which it is being build. Let's export
linux_banner.
Signed-off-by: Mukesh Ojha
---
include/linux/init.h | 3 +++
init/version-timestamp.c | 2 ++
2 files changed, 5 insertions(+)
diff --git a/includ
Add the entries into maintainer file for all the minidump related
modules.
Signed-off-by: Mukesh Ojha
---
MAINTAINERS | 10 ++
1 file changed, 10 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index c45587eb4c1d..a7eea6e64dce 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -18176,6
Minidump is a best effort mechanism to collect useful and predefined
data for first level of debugging on end user devices running on
Qualcomm SoCs. It is built on the premise that System on Chip (SoC)
or subsystem part of SoC crashes, due to a range of hardware and
software bugs. Hence, the abilit
Client like minidump is interested in knowing ramoops
individual zone addresses and their size so that it
could register them with its table.
Let's introduce a info notifier in ramoops which
gets called when ramoops driver probes successfully
and it passes the ramoops region information to the
pas
The reserved memory region for ramoops is assumed to be at a fixed
and known location when read from the devicetree. This may not be
required for something like Qualcomm's minidump which is interested
in knowing addresses of ramoops region but it does not put hard
requirement of address being fixed
Register ramoops region with APSS minidump via ramoops
info notifier so that these region gets captured on
system crash.
Signed-off-by: Mukesh Ojha
---
drivers/soc/qcom/qcom_minidump.c | 84
1 file changed, 84 insertions(+)
diff --git a/drivers/soc/qcom/qcom_min
Extend the list of maintainer profiles with SoC and netdev.
Signed-off-by: Krzysztof Kozlowski
---
Documentation/maintainer/maintainer-entry-profile.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/maintainer/maintainer-entry-profile.rst
b/Documentation/maintainer/mainta
On Tue, Jan 30, 2024 at 3:16 AM Masahiro Yamada wrote:
>
> On Fri, Jan 26, 2024 at 1:04 AM Simon Glass wrote:
> >
> > Hi,
> >
> > On Wed, 17 Jan 2024 at 06:14, Simon Glass wrote:
> > >
> > > Hi Masahiro, Tom,
> > >
> > > On Tue, 9 Jan 2024 at 07:33, Tom Rini wrote:
> > > >
> > > > On Tue, Jan 0
On Thu, Feb 1, 2024 at 7:03 AM Rob Herring wrote:
>
> On Tue, Jan 30, 2024 at 3:16 AM Masahiro Yamada wrote:
> >
> > On Fri, Jan 26, 2024 at 1:04 AM Simon Glass wrote:
> > >
> > > Hi,
> > >
> > > On Wed, 17 Jan 2024 at 06:14, Simon Glass wrote:
> > > >
> > > > Hi Masahiro, Tom,
> > > >
> > > >
14 matches
Mail list logo