From: Dylan Hung <dylan_hung@aspeedtech.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 0/2] [RFC] i3c: ast2600: Add MCTP-over-I3C support
Date: Mon, 6 May 2024 18:51:18 +0800 [thread overview]
Message-ID: <20240506105120.3028083-1-dylan_hung@aspeedtech.com> (raw)
Add Aspeed AST2600 I3C controllers and add minimal changes to validate
the functionality for MCTP-over-I3C.
Dylan Hung (2):
[RFC] ARM: dts: aspeed-g6: Add AST2600 I3Cs
[RFC] i3c: ast2600: Validate AST2600 I3C for MCTP-over-I3C
arch/arm/boot/dts/aspeed/aspeed-g6.dtsi | 137 +++++++
drivers/i3c/master/ast2600-i3c-master.c | 137 +++++++
drivers/i3c/master/dw-i3c-master.c | 513 ++++++++++++++++++++----
drivers/i3c/master/dw-i3c-master.h | 12 +
4 files changed, 718 insertions(+), 81 deletions(-)
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Dylan Hung <dylan_hung@aspeedtech.com>
To: <robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<joel@jms.id.au>, <andrew@codeconstruct.com.au>,
<jk@codeconstruct.com.au>, <alexandre.belloni@bootlin.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<linux-i3c@lists.infradead.org>
Cc: <BMC-SW@aspeedtech.com>
Subject: [PATCH 0/2] [RFC] i3c: ast2600: Add MCTP-over-I3C support
Date: Mon, 6 May 2024 18:51:18 +0800 [thread overview]
Message-ID: <20240506105120.3028083-1-dylan_hung@aspeedtech.com> (raw)
Add Aspeed AST2600 I3C controllers and add minimal changes to validate
the functionality for MCTP-over-I3C.
Dylan Hung (2):
[RFC] ARM: dts: aspeed-g6: Add AST2600 I3Cs
[RFC] i3c: ast2600: Validate AST2600 I3C for MCTP-over-I3C
arch/arm/boot/dts/aspeed/aspeed-g6.dtsi | 137 +++++++
drivers/i3c/master/ast2600-i3c-master.c | 137 +++++++
drivers/i3c/master/dw-i3c-master.c | 513 ++++++++++++++++++++----
drivers/i3c/master/dw-i3c-master.h | 12 +
4 files changed, 718 insertions(+), 81 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: Dylan Hung <dylan_hung@aspeedtech.com>
To: <robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<joel@jms.id.au>, <andrew@codeconstruct.com.au>,
<jk@codeconstruct.com.au>, <alexandre.belloni@bootlin.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<linux-i3c@lists.infradead.org>
Cc: <BMC-SW@aspeedtech.com>
Subject: [PATCH 0/2] [RFC] i3c: ast2600: Add MCTP-over-I3C support
Date: Mon, 6 May 2024 18:51:18 +0800 [thread overview]
Message-ID: <20240506105120.3028083-1-dylan_hung@aspeedtech.com> (raw)
Add Aspeed AST2600 I3C controllers and add minimal changes to validate
the functionality for MCTP-over-I3C.
Dylan Hung (2):
[RFC] ARM: dts: aspeed-g6: Add AST2600 I3Cs
[RFC] i3c: ast2600: Validate AST2600 I3C for MCTP-over-I3C
arch/arm/boot/dts/aspeed/aspeed-g6.dtsi | 137 +++++++
drivers/i3c/master/ast2600-i3c-master.c | 137 +++++++
drivers/i3c/master/dw-i3c-master.c | 513 ++++++++++++++++++++----
drivers/i3c/master/dw-i3c-master.h | 12 +
4 files changed, 718 insertions(+), 81 deletions(-)
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Dylan Hung <dylan_hung@aspeedtech.com>
To: <robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<joel@jms.id.au>, <andrew@codeconstruct.com.au>,
<jk@codeconstruct.com.au>, <alexandre.belloni@bootlin.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<linux-i3c@lists.infradead.org>
Cc: <BMC-SW@aspeedtech.com>
Subject: [PATCH 0/2] [RFC] i3c: ast2600: Add MCTP-over-I3C support
Date: Mon, 6 May 2024 18:51:18 +0800 [thread overview]
Message-ID: <20240506105120.3028083-1-dylan_hung@aspeedtech.com> (raw)
Add Aspeed AST2600 I3C controllers and add minimal changes to validate
the functionality for MCTP-over-I3C.
Dylan Hung (2):
[RFC] ARM: dts: aspeed-g6: Add AST2600 I3Cs
[RFC] i3c: ast2600: Validate AST2600 I3C for MCTP-over-I3C
arch/arm/boot/dts/aspeed/aspeed-g6.dtsi | 137 +++++++
drivers/i3c/master/ast2600-i3c-master.c | 137 +++++++
drivers/i3c/master/dw-i3c-master.c | 513 ++++++++++++++++++++----
drivers/i3c/master/dw-i3c-master.h | 12 +
4 files changed, 718 insertions(+), 81 deletions(-)
--
2.25.1
next reply other threads:[~2024-05-06 10:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 10:51 Dylan Hung [this message]
2024-05-06 10:51 ` [PATCH 0/2] [RFC] i3c: ast2600: Add MCTP-over-I3C support Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` [PATCH 1/2] [RFC] ARM: dts: aspeed-g6: Add AST2600 I3Cs Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` [PATCH 2/2] [RFC] i3c: ast2600: Validate AST2600 I3C for MCTP-over-I3C Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 13:46 ` [PATCH 0/2] [RFC] i3c: ast2600: Add MCTP-over-I3C support Jeremy Kerr
2024-05-06 13:46 ` Jeremy Kerr
2024-05-06 13:46 ` Jeremy Kerr
2024-05-06 13:46 ` Jeremy Kerr
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=20240506105120.3028083-1-dylan_hung@aspeedtech.com \
--to=dylan_hung@aspeedtech.com \
--cc=linux-aspeed@lists.ozlabs.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.