From: Pranav Prasad <pranavpp@google.com>
To: Jack Wang <jinpu.wang@cloud.ionos.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Pranav Prasad <pranavpp@google.com>
Subject: [PATCH 0/6] scsi: pm80xx: Enhanced debug logs for HW events
Date: Tue, 18 Apr 2023 19:00:55 +0000 [thread overview]
Message-ID: <20230418190101.696345-1-pranavpp@google.com> (raw)
This patch series enhances debug logs for pm80xx HW events, and provides
a minor fix in the case of a hard reset. The log enhancement involves
changing the log severity level to enable logging for HW events
which consequently help debug disk discovery issues.
1. Changed log severity level from MSG to EVENT for HW events.
Enhanced the HW event logs by adding the phyid.
2. Enabled INIT logging.
3. Log portid along with the PHY_UP event.
4. Print phyid and portid sent as part of device registration
request.
5. Log port state during HW events.
6. Update phy_state and phy_attached to correct values after
a hard reset.
Akshat Jain (5):
scsi: pm80xx: Enable init logging
scsi: pm80xx: Print port_id in hardware events
scsi: pm80xx: Log phyid and portid device register request
scsi: pm80xx: Log port state during HW event
scsi: pm80xx: Log some HW events by default
Changyuan Lyu (1):
scsi: pm80xx: Update PHY state after hard reset
drivers/scsi/pm8001/pm8001_init.c | 3 +-
drivers/scsi/pm8001/pm8001_sas.h | 1 +
drivers/scsi/pm8001/pm80xx_hwi.c | 126 +++++++++++++++++++-----------
3 files changed, 85 insertions(+), 45 deletions(-)
--
2.40.0.634.g4ca3ef3211-goog
next reply other threads:[~2023-04-18 19:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 19:00 Pranav Prasad [this message]
2023-04-18 19:00 ` [PATCH 1/6] scsi: pm80xx: Log some HW events by default Pranav Prasad
2023-04-19 7:17 ` Jinpu Wang
2023-04-18 19:00 ` [PATCH 2/6] scsi: pm80xx: Enable init logging Pranav Prasad
2023-04-19 7:19 ` Jinpu Wang
2023-04-18 19:00 ` [PATCH 3/6] scsi: pm80xx: Print port_id in HW events Pranav Prasad
2023-04-19 7:20 ` Jinpu Wang
2023-04-18 19:00 ` [PATCH 4/6] scsi: pm80xx: Log phy_id and port_id in the device registration request Pranav Prasad
2023-04-19 7:20 ` Jinpu Wang
2023-04-18 19:01 ` [PATCH 5/6] scsi: pm80xx: Log port state during HW event Pranav Prasad
2023-04-19 7:22 ` Jinpu Wang
2023-04-18 19:01 ` [PATCH 6/6] scsi: pm80xx: Update PHY state after hard reset Pranav Prasad
2023-04-19 7:23 ` Jinpu Wang
2023-05-06 21:59 ` [PATCH 0/6] scsi: pm80xx: Enhanced debug logs for HW events Martin K. Petersen
2023-05-17 2:12 ` Martin K. Petersen
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=20230418190101.696345-1-pranavpp@google.com \
--to=pranavpp@google.com \
--cc=jejb@linux.ibm.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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