From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 729A4C48BE8 for ; Fri, 18 Jun 2021 09:14:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 55F2E61209 for ; Fri, 18 Jun 2021 09:14:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233081AbhFRJQX (ORCPT ); Fri, 18 Jun 2021 05:16:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58838 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232009AbhFRJQU (ORCPT ); Fri, 18 Jun 2021 05:16:20 -0400 Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9084EC061574 for ; Fri, 18 Jun 2021 02:14:10 -0700 (PDT) Received: by mail-lj1-x230.google.com with SMTP id b37so13032390ljr.13 for ; Fri, 18 Jun 2021 02:14:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fk/g4Uf4e6ndK9NTLJ4fya67I6nyHsWdWmINzLkYxxQ=; b=Ej/kae+4z4muiWg6EWVSQJZ0hKf207pahpJvxNxI5rzvReNLTOakQyMu0hPKFKQapC KdfIPU1/IY5qQj8piocGrYiAvwhAsKgD6Aac0EfK5OBIgHBnb0t9I5fWbElLuPl9j7uG f8EsIa72iX68DlTtcVZ2ZytW6itc2zcRTL2NmByb6VBTT/40OIdIokHxEx3crUwnaeej do28bIC90BwWHOqkQQANMqlKuQAUvGklT9o4LJ+nOW/mFuWiHSGCUkSA0RXj+USUl5Zu gL+aEhP1YsJsUvXvI7EYMZVd4VlDwDMgbNhmdQLYBjLy9adLLvADaViX2g39cl3yZ8oY AMCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fk/g4Uf4e6ndK9NTLJ4fya67I6nyHsWdWmINzLkYxxQ=; b=koREirlYylikC6RzluxudQAKSAjj7RZNXZtGCLbxBBlxn4H6j31ZPp2w9wnZbRYHkt o0VUGsAvaJ3PCoJOFg2neUT5VqjKYDIZ0cJa86rI/TCjdUXTup3dkI7+Ov30y30SXdeT eVqvxYCnPkhb1RIto33bNkXS0j2ve3sySyO8ONpEd4a1vvx23kOeChcqOC29d9SRq0HN KlExKt5r/KtltXR0EfhQtghC+g/v0KgO+2ZDEyL+rAtPIoJuzhy/tRkkOahAWpJvIu1r 4/ij/yEd+ws6l+jR8NX4Go0mpQm9MgnjMPg0KUsUkJI6ISEJswGLxlDf5ugmymfBRp5k bmgQ== X-Gm-Message-State: AOAM531ZkaZYoEf/1Cz9zELX8sgbb12JiFsE6giibPQPGqvig7n/MirM kQIMh4YxZEMNV9QcDvBEqKCbpxZyCQF/AtypjA8omQ== X-Google-Smtp-Source: ABdhPJxO5angft3VVWPEspBXdSa1jj492/Lqu/sjYy6Szkm5Bb7VcFbM7lZNp02NJxKP3yiLMp83/cpYtRf0ZvPmzDg= X-Received: by 2002:a2e:95d8:: with SMTP id y24mr2468745ljh.368.1624007648913; Fri, 18 Jun 2021 02:14:08 -0700 (PDT) MIME-Version: 1.0 References: <10442926ae8a65f716bfc23f32339a6b35e51d5a.1623326176.git.viresh.kumar@linaro.org> <8d58da79-8e54-048b-db89-8c1caaa0320f@metux.net> In-Reply-To: <8d58da79-8e54-048b-db89-8c1caaa0320f@metux.net> From: Linus Walleij Date: Fri, 18 Jun 2021 11:13:57 +0200 Message-ID: Subject: Re: [PATCH V3 1/3] gpio: Add virtio-gpio driver To: "Enrico Weigelt, metux IT consult" Cc: Bjorn Andersson , Viresh Kumar , Geert Uytterhoeven , Bartosz Golaszewski , "Enrico Weigelt, metux IT consult" , Viresh Kumar , "Michael S. Tsirkin" , Jason Wang , Vincent Guittot , Bill Mills , "Alex Benn?e" , stratos-dev@op-lists.linaro.org, "open list:GPIO SUBSYSTEM" , linux-kernel , Stefan Hajnoczi , "Stefano Garzarella --cc virtualization @ lists . linux-foundation . org" , virtualization@lists.linux-foundation.org, Alistair Strachan Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 16, 2021 at 5:52 PM 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 using shared memory as transport mechanism and virtio is providing this. rpmsg is conceptually a child of virtio: when the subsystem was proposed by TI Arnd noted that virtio has large similarities in shared memory transport and as the potential reuse for buffer handling etc was excellent virtio was used as a base for rpmsg/remoteproc work. Yours, Linus Walleij