From: Ryan Chen <ryan_chen@aspeedtech.com>
To: "'vitor'" <vitor.soares@synopsys.com>,
"'Boris Brezillon'" <bbrezillon@kernel.org>
Cc: "linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>
Subject: RE: i3c application
Date: Tue, 5 Feb 2019 14:49:19 +0000 [thread overview]
Message-ID: <004301d4bd61$f6d664b0$e4832e10$@aspeedtech.com> (raw)
In-Reply-To: <2dfbed05-1dba-c297-ae44-e54aa3ab13a2@synopsys.com>
Hello Boris,
Got it. Thanks a lot
-----Original Message-----
From: vitor [mailto:vitor.soares@synopsys.com]
Sent: Monday, February 4, 2019 6:59 PM
To: Ryan Chen <ryan_chen@aspeedtech.com>; 'Boris Brezillon' <bbrezillon@kernel.org>
Cc: linux-i3c@lists.infradead.org; 'Vitor Soares' <vitor.soares@synopsys.com>
Subject: Re: i3c application
Hi Ryan,
On 04/02/19 07:08, Ryan Chen wrote:
> Sorry for confuse.
> Let me explain more.
> For example at i2c, In our SOC, we have i2c slave and master. So I can
> use I2c slave to be dummy memory device. And I can connect my I2c
> master and slave.
> I2c master use i2c-tools to have i2cget, i2cset for read/write i2c
> slave dummy memory.
>
> So, I just wonder if i3c have some user application that I can have a
> start point. It will easy way for me do the same thing.
>
>
> Regards,
>
> Ryan
>
As Boris said for now there is nothing like i2c-tools for i3c.
Based on initial discussion with Boris, I'm working on something to submit soon.
Best regards,
Vitor Soares
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2019-02-05 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 0:54 i3c application Ryan Chen
2019-01-29 13:30 ` Boris Brezillon
2019-02-02 3:01 ` Ryan Chen
2019-02-03 17:33 ` Boris Brezillon
2019-02-04 7:08 ` Ryan Chen
2019-02-04 10:59 ` vitor
2019-02-05 14:49 ` Ryan Chen [this message]
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='004301d4bd61$f6d664b0$e4832e10$@aspeedtech.com' \
--to=ryan_chen@aspeedtech.com \
--cc=bbrezillon@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=vitor.soares@synopsys.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;
as well as URLs for NNTP newsgroup(s).