From: Joshua Yeong <joshua.yeong@starfivetech.com>
To: <alexandre.belloni@bootlin.com>
Cc: <linux-i3c@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
"Joshua Yeong" <joshua.yeong@starfivetech.com>
Subject: [PATCH 0/1] Fallback mechanism for GETMXDS CCC
Date: Mon, 11 Sep 2023 16:24:55 +0800 [thread overview]
Message-ID: <20230911082456.23239-1-joshua.yeong@starfivetech.com> (raw)
Some I3C hardware will report error when incorrect length is received from
device. GETMXDS CCC are availble in 2 formats; without turnaround time (format
1) and with turnaround time (format 2). There is no mechanics to determine which
format is supported by device. In case sending GETMXDS CCC format 2 resulted
failure, try sending GETMXDS CCC format 1 instead.
Joshua Yeong (1):
i3c: Add fallback method for GETMXDS CCC
drivers/i3c/master.c | 33 ++++++++++++++++++++++++++++-----
include/linux/i3c/ccc.h | 17 +++++++++++++++--
2 files changed, 43 insertions(+), 7 deletions(-)
--
2.25.1
--
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: <alexandre.belloni@bootlin.com>
Cc: <linux-i3c@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
"Joshua Yeong" <joshua.yeong@starfivetech.com>
Subject: [PATCH 0/1] Fallback mechanism for GETMXDS CCC
Date: Mon, 11 Sep 2023 16:24:55 +0800 [thread overview]
Message-ID: <20230911082456.23239-1-joshua.yeong@starfivetech.com> (raw)
Some I3C hardware will report error when incorrect length is received from
device. GETMXDS CCC are availble in 2 formats; without turnaround time (format
1) and with turnaround time (format 2). There is no mechanics to determine which
format is supported by device. In case sending GETMXDS CCC format 2 resulted
failure, try sending GETMXDS CCC format 1 instead.
Joshua Yeong (1):
i3c: Add fallback method for GETMXDS CCC
drivers/i3c/master.c | 33 ++++++++++++++++++++++++++++-----
include/linux/i3c/ccc.h | 17 +++++++++++++++--
2 files changed, 43 insertions(+), 7 deletions(-)
--
2.25.1
next reply other threads:[~2023-09-11 8:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 8:24 Joshua Yeong [this message]
2023-09-11 8:24 ` [PATCH 0/1] Fallback mechanism for GETMXDS CCC Joshua Yeong
2023-09-11 8:24 ` [PATCH 1/1] i3c: Add fallback method " Joshua Yeong
2023-09-11 8:24 ` Joshua Yeong
2023-09-12 11:08 ` Miquel Raynal
2023-09-12 11:08 ` Miquel Raynal
2023-09-13 5:58 ` Joshua Yeong
2023-09-13 5:58 ` Joshua Yeong
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=20230911082456.23239-1-joshua.yeong@starfivetech.com \
--to=joshua.yeong@starfivetech.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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.