From: Arnaud POULIQUEN <arnaud.pouliquen@st.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Tomer Maimon <tmaimon77@gmail.com>
Cc: "wsa@kernel.org" <wsa@kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"ohad@wizery.com" <ohad@wizery.com>,
"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
"linux-remoteproc@vger.kernel.org"
<linux-remoteproc@vger.kernel.org>,
"avi.fishman@nuvoton.com" <avi.fishman@nuvoton.com>,
"eyal.cohen@nuvoton.com" <eyal.cohen@nuvoton.com>
Subject: Re: Upstream I2C driver that designed for rpmsg
Date: Tue, 22 Sep 2020 14:27:23 +0200 [thread overview]
Message-ID: <fc013df0-b670-eead-4c14-515af474fed3@st.com> (raw)
In-Reply-To: <20200922090956.GK3956970@smile.fi.intel.com>
On 9/22/20 11:09 AM, Andy Shevchenko wrote:
> On Tue, Sep 22, 2020 at 12:41:35AM +0300, Tomer Maimon wrote:
>> Hello all,
>>
>> Our BMC have two processors
>>
>> 1. main processors - A35
>> 2. Coprocessor(CP) - M4.
>>
>> The BMC handles more than 30 I2C buses.
>>
>> We like to handle the I2C module in the Coprocessor for offload the i2c
>> transaction from main processor.
>>
>> The main processor is running Linux,
>>
>> The main processor and the CP communicate through rpmsg.
>>
>> Is an I2C driver that designed for rpmsg will be up-streamed to Linux.Org?
>
> There are examples in the kernel of indirect access to I2C host controllers
> which are parts of auxiliary micro controllers. I guess in principle it's okay
> and most of the success of the submission depends on implementation.
>
> Nice to see such requirement.
We developed this type of driver in STMicroelectronics to be able to share an I2C
link between the main processor(Linux) and the coprocessor (Zephyr).
We plan to usptream it but some other patchsets currently in pipe are requested first.
The Linux driver is available here:
https://github.com/arnopo/linux/commit/747a05d4f3a875ff0b6ad3fc57965134d7a02ed3
The full project created for the ELCE 2019 is described in this page:
https://github.com/arnopo?tab=projects
Hope that this can help.
Regards,
Arnaud
prev parent reply other threads:[~2020-09-22 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP6Zq1jrT-AmNT2J11OEk80=qL04=jCKTBoM-FLEt1na6d00kQ@mail.gmail.com>
2020-09-22 9:09 ` Upstream I2C driver that designed for rpmsg Andy Shevchenko
2020-09-22 12:27 ` Arnaud POULIQUEN [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=fc013df0-b670-eead-4c14-515af474fed3@st.com \
--to=arnaud.pouliquen@st.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=avi.fishman@nuvoton.com \
--cc=bjorn.andersson@linaro.org \
--cc=eyal.cohen@nuvoton.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=tmaimon77@gmail.com \
--cc=wsa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox