Linux virtualization list
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: Alistair Strachan <astrachan@google.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	virtualization@lists.linux-foundation.org,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Viresh Kumar <vireshk@kernel.org>,
	stratos-dev@op-lists.linaro.org, "Enrico Weigelt,
	metux IT consult" <info@metux.net>,
	Bill Mills <bill.mills@linaro.org>
Subject: Re: [PATCH V3 1/3] gpio: Add virtio-gpio driver
Date: Mon, 21 Jun 2021 12:25:28 -0500	[thread overview]
Message-ID: <YNDLiPYkmLZN076t@yoga> (raw)
In-Reply-To: <8d58da79-8e54-048b-db89-8c1caaa0320f@metux.net>

On Wed 16 Jun 10:52 CDT 2021, Enrico Weigelt, metux IT consult wrote:

> On 16.06.21 05:30, Bjorn Andersson wrote:
> 
> > Combined with the virtio-i2c effort this could provide an alternative by
> > simply tunneling the busses and GPIOs into Linux and use standard iio
> > drivers, for cases where this suits your product requirements better.
> 
> So, you wanna use virtio as logical interface between the two CPUs ?
> Interesting idea. Usually folks use rpmsg for those things.
> 

rpmsg is a layer on top of virtio, so this would be an extension of the
existing model.

There's been discussions (and I believe some implementations) related to
bridging I2C requests over rpmsg, but I think it's preferable to
standardize around the virtio based bearer directly.

> What is running on the secondary CPU ? Some OS like Linux or some bare
> metal stuff ? What kind of CPU is that anyways ?
> 

These ideas revolves around platforms that implements something like the
"Android Sensor Hub", which provides some resource constraint
co-processor that deals with sensor device interaction and processing of
the data without waking up the power-hungry ARM cores.

Given the focus on power consumption I would guess that these are not
going to run Linux. Core-wise I've seen this implemented using primarily
ARM and Hexagon cores.

Regards,
Bjorn
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  parent reply	other threads:[~2021-06-21 17:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 12:09 [PATCH V3 0/3] gpio: Add virtio based driver Viresh Kumar
2021-06-10 12:16 ` [PATCH V3 1/3] gpio: Add virtio-gpio driver Viresh Kumar
     [not found]   ` <96994f4c-8755-90a8-0c50-4e21c436f137@metux.net>
2021-06-10 16:57     ` Viresh Kumar
2021-06-10 20:46   ` Linus Walleij
2021-06-11  3:56     ` Viresh Kumar
2021-06-11  7:42       ` Geert Uytterhoeven
2021-06-11  8:01         ` Viresh Kumar
2021-06-11  8:22           ` Geert Uytterhoeven
2021-06-15 11:15             ` Viresh Kumar
2021-06-15 11:37               ` Geert Uytterhoeven
2021-06-15 20:03               ` Linus Walleij
2021-06-16  1:45                 ` Viresh Kumar
     [not found]           ` <0478822f-9d10-deb8-86ae-3b4ac3bb0c6c@metux.net>
2021-06-14  8:12             ` Andy Shevchenko
2021-06-14  9:14               ` Viresh Kumar
     [not found]               ` <d127bb4c-722d-536b-c89f-4c40cbaa6479@metux.net>
2021-06-14  9:52                 ` Viresh Kumar
2021-06-14  9:12             ` Viresh Kumar
     [not found]         ` <db2d29fd-ff27-0c75-2472-dd031564dbf1@metux.net>
2021-06-14  9:24           ` Viresh Kumar
2021-06-16  3:30     ` Bjorn Andersson
     [not found]       ` <8d58da79-8e54-048b-db89-8c1caaa0320f@metux.net>
2021-06-18  9:13         ` Linus Walleij
2021-06-21 17:25         ` Bjorn Andersson [this message]
     [not found]   ` <CAK8P3a11YhcEOjauWc872BQv+SO-E5+gnz7Lk6UK42iVw7Oyfg@mail.gmail.com>
     [not found]     ` <01000179f6a7715c-cd106846-7770-4088-bb7c-a696bfcbf83e-000000@email.amazonses.com>
2021-06-10 17:03       ` [Stratos-dev] " Jean-Philippe Brucker
2021-06-14 10:21     ` Viresh Kumar
2021-06-10 12:16 ` [PATCH V3 2/3] gpio: virtio: Add IRQ support Viresh Kumar
2021-06-10 21:30   ` Linus Walleij
2021-06-14  7:08     ` Viresh Kumar
     [not found] ` <01000179f5da7763-2ea817c6-e176-423a-952e-de02443f71e2-000000@email.amazonses.com>
2021-06-10 17:40   ` [PATCH V3 1/3] gpio: Add virtio-gpio driver Jean-Philippe Brucker
2021-06-11  3:39     ` Viresh Kumar
     [not found]     ` <01000179f9276678-ae2bb25f-4c0c-4176-b906-650c585b9753-000000@email.amazonses.com>
     [not found]       ` <CAK8P3a2-bXfDcPymMct2aUXs2m+YgbKdmAatMMs9tnc+HjS_xQ@mail.gmail.com>
2021-06-14  5:26         ` [Stratos-dev] " Viresh Kumar

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=YNDLiPYkmLZN076t@yoga \
    --to=bjorn.andersson@linaro.org \
    --cc=astrachan@google.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=bill.mills@linaro.org \
    --cc=geert+renesas@glider.be \
    --cc=info@metux.net \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@metux.net \
    --cc=mst@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=stratos-dev@op-lists.linaro.org \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@linaro.org \
    --cc=vireshk@kernel.org \
    --cc=virtualization@lists.linux-foundation.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