From: Joshua Yeong <joshua.yeong@starfivetech.com>
To: Frank Li <Frank.li@nxp.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: "linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>
Subject: Re: [PATCH] i3c: don't fail if GETHDRCAP is unsupported
Date: Thu, 26 Jun 2025 02:46:35 +0000 [thread overview]
Message-ID: <26c2b49b-713e-4e9c-8bf4-0ffbd0b4b050@starfivetech.com> (raw)
In-Reply-To: <aFwUx65gdpv6H6rU@lizhi-Precision-Tower-5810>
On 25-Jun-2025 11:24 PM, Frank Li wrote:
> On Wed, Jun 25, 2025 at 09:34:52AM +0200, Wolfram Sang wrote:
>> If a target has the HDR_CAP bit set in BCR, the core wants to get
>> additional information using the CCC 'GETHDRCAP'. Not all controllers
>> support this CCC, though.
>
> Do you know which target device support HDR? I3C master API don't HDR yet.
>
>> This is not fatal. We can just skip it. The
>> information is not needed if the controller won't support HDR anyhow.
>
> This is not fatal and can be safely skipped, as the information is not
> necessary if HDR is unsupported by the controller anyway.
>
> Frank
Hi Frank
I'm use `MMC5633` to test out the HDR-DDR functionality master functionality.
The patch can be accepted as some controller might not support HDR.
>>
>> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
>> ---
>>
>> Found during the I3C plugfest in Warsaw.
>>
>> drivers/i3c/master.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c
>> index 204b96e6be1e..b6b96cf9e4e0 100644
>> --- a/drivers/i3c/master.c
>> +++ b/drivers/i3c/master.c
>> @@ -1440,7 +1440,7 @@ static int i3c_master_retrieve_dev_info(struct i3c_dev_desc *dev)
>>
>> if (dev->info.bcr & I3C_BCR_HDR_CAP) {
>> ret = i3c_master_gethdrcap_locked(master, &dev->info);
>> - if (ret)
>> + if (ret && ret != -ENOTSUPP)
>> return ret;
>> }
>>
>> --
>> 2.47.2
>>
>>
>> --
>> linux-i3c mailing list
>> linux-i3c@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-i3c
>
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
WARNING: multiple messages have this Message-ID (diff)
From: Joshua Yeong <joshua.yeong@starfivetech.com>
To: Frank Li <Frank.li@nxp.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: "linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>
Subject: Re: [PATCH] i3c: don't fail if GETHDRCAP is unsupported
Date: Thu, 26 Jun 2025 02:46:35 +0000 [thread overview]
Message-ID: <26c2b49b-713e-4e9c-8bf4-0ffbd0b4b050@starfivetech.com> (raw)
In-Reply-To: <aFwUx65gdpv6H6rU@lizhi-Precision-Tower-5810>
On 25-Jun-2025 11:24 PM, Frank Li wrote:
> On Wed, Jun 25, 2025 at 09:34:52AM +0200, Wolfram Sang wrote:
>> If a target has the HDR_CAP bit set in BCR, the core wants to get
>> additional information using the CCC 'GETHDRCAP'. Not all controllers
>> support this CCC, though.
>
> Do you know which target device support HDR? I3C master API don't HDR yet.
>
>> This is not fatal. We can just skip it. The
>> information is not needed if the controller won't support HDR anyhow.
>
> This is not fatal and can be safely skipped, as the information is not
> necessary if HDR is unsupported by the controller anyway.
>
> Frank
Hi Frank
I'm use `MMC5633` to test out the HDR-DDR functionality master functionality.
The patch can be accepted as some controller might not support HDR.
>>
>> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
>> ---
>>
>> Found during the I3C plugfest in Warsaw.
>>
>> drivers/i3c/master.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c
>> index 204b96e6be1e..b6b96cf9e4e0 100644
>> --- a/drivers/i3c/master.c
>> +++ b/drivers/i3c/master.c
>> @@ -1440,7 +1440,7 @@ static int i3c_master_retrieve_dev_info(struct i3c_dev_desc *dev)
>>
>> if (dev->info.bcr & I3C_BCR_HDR_CAP) {
>> ret = i3c_master_gethdrcap_locked(master, &dev->info);
>> - if (ret)
>> + if (ret && ret != -ENOTSUPP)
>> return ret;
>> }
>>
>> --
>> 2.47.2
>>
>>
>> --
>> linux-i3c mailing list
>> linux-i3c@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-i3c
>
next prev parent reply other threads:[~2025-06-26 3:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 7:34 [PATCH] i3c: don't fail if GETHDRCAP is unsupported Wolfram Sang
2025-06-25 7:34 ` Wolfram Sang
2025-06-25 15:24 ` Frank Li
2025-06-25 15:24 ` Frank Li
2025-06-25 16:41 ` Wolfram Sang
2025-06-25 16:41 ` Wolfram Sang
2025-06-26 2:46 ` Joshua Yeong [this message]
2025-06-26 2:46 ` Joshua Yeong
2025-07-03 6:41 ` Wolfram Sang
2025-07-03 6:41 ` Wolfram Sang
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=26c2b49b-713e-4e9c-8bf4-0ffbd0b4b050@starfivetech.com \
--to=joshua.yeong@starfivetech.com \
--cc=Frank.li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.