From: Wolfram Sang <wsa@kernel.org>
To: Avri Altman <Avri.Altman@wdc.com>
Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH v6 7/7] arm64: dts: renesas: r8a779f0: spider-cpu: Enable UFS device
Date: Wed, 22 Jun 2022 10:38:03 +0200 [thread overview]
Message-ID: <YrLU6/jAZ5lGnL3p@shikoro> (raw)
In-Reply-To: <DM6PR04MB6575D7C91E0925B5D498ABF3FCB29@DM6PR04MB6575.namprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
Hi Avri, all,
> > [ 0.449917] ufshcd-renesas e6860000.ufs: ufshcd_query_attr: opcode 0x03
> > for idn 1 failed, index 0, err = 253
> > [ 0.452035] ufshcd-renesas e6860000.ufs: ufshcd_query_attr: opcode 0x03
> > for idn 1 failed, index 0, err = 253
> > [ 0.453859] ufshcd-renesas e6860000.ufs: ufshcd_query_attr: opcode 0x03
> > for idn 1 failed, index 0, err = 253
> > [ 0.453874] ufshcd-renesas e6860000.ufs: ufshcd_query_attr_retry: query
> > attribute, idn 1, failed with error 253 after 3 retires
> Should be interesting to find out who is trying to read an undefined (reserved) attribute in your system.
So, the call trace is:
[ 0.455361] Call trace:
[ 0.455521] ufshcd_query_attr_retry+0x68/0xb0
[ 0.455808] ufshpb_get_dev_info+0x80/0x110
[ 0.456083] ufshcd_probe_hba+0xce0/0x10d0
[ 0.456349] ufshcd_async_scan+0x34/0x310
[ 0.456609] async_run_entry_fn+0x34/0x130
[ 0.456873] process_one_work+0x1e4/0x434
[ 0.457136] worker_thread+0x174/0x4dc
[ 0.457379] kthread+0xdc/0xe0
[ 0.457580] ret_from_fork+0x10/0x20
which leads me to this call in ufshpb_get_dev_info():
2622 ret = ufshcd_query_attr_retry(hba, UPIU_QUERY_OPCODE_READ_ATTR,
2623 QUERY_ATTR_IDN_MAX_HPB_SINGLE_CMD, 0, 0, &max_single_cmd);
And from here on, I miss the UFS experience to debug further. But I will
happily provide more information if people give me pointers.
All the best,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-22 8:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 11:05 [PATCH v6 0/7] treewide: ufs: Add support for Renesas R-Car UFS controller Yoshihiro Shimoda
2022-06-03 11:05 ` [PATCH v6 1/7] dt-bindings: ufs: Document Renesas R-Car UFS host controller Yoshihiro Shimoda
2022-06-03 11:05 ` [PATCH v6 2/7] ufs: add UFSHCD_QUIRK_BROKEN_64BIT_ADDRESS Yoshihiro Shimoda
2022-06-03 11:05 ` [PATCH v6 3/7] ufs: add UFSHCD_QUIRK_HIBERN_FASTAUTO Yoshihiro Shimoda
2022-06-03 11:05 ` [PATCH v6 4/7] scsi: ufs-renesas: Add support for Renesas R-Car UFS controller Yoshihiro Shimoda
2022-06-03 11:05 ` [PATCH v6 5/7] scsi: MAINTAINERS: Add maintainer for Renesas UFS driver Yoshihiro Shimoda
2022-06-03 11:05 ` [PATCH v6 6/7] arm64: dts: renesas: r8a779f0: Add UFS node Yoshihiro Shimoda
2022-06-14 8:02 ` Geert Uytterhoeven
2022-06-03 11:05 ` [PATCH v6 7/7] arm64: dts: renesas: r8a779f0: spider-cpu: Enable UFS device Yoshihiro Shimoda
2022-06-14 8:06 ` Geert Uytterhoeven
2022-06-21 15:14 ` Wolfram Sang
2022-06-22 6:32 ` Avri Altman
2022-06-22 8:38 ` Wolfram Sang [this message]
2022-06-22 9:42 ` Avri Altman
2022-06-22 9:47 ` Avri Altman
2022-06-22 11:16 ` Wolfram Sang
2022-06-23 4:20 ` Yoshihiro Shimoda
2022-06-22 8:11 ` Yoshihiro Shimoda
2022-06-22 8:22 ` Wolfram Sang
2022-06-22 8:28 ` Yoshihiro Shimoda
2022-06-14 8:00 ` [PATCH v6 0/7] treewide: ufs: Add support for Renesas R-Car UFS controller Geert Uytterhoeven
2022-06-15 2:53 ` Martin K. Petersen
2022-06-15 7:20 ` Geert Uytterhoeven
2022-06-17 1:29 ` Martin K. Petersen
2022-06-17 2:21 ` 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=YrLU6/jAZ5lGnL3p@shikoro \
--to=wsa@kernel.org \
--cc=Avri.Altman@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jejb@linux.ibm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=robh+dt@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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