devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Hackmann <ghackmann@google.com>
To: Christoffer Dall <christoffer.dall@linaro.org>,
	Rob Herring <robh@kernel.org>
Cc: "Jin Qian" <jinqian@android.com>,
	"Pawel Moll" <pawel.moll@arm.com>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
	"Kumar Gala" <galak@codeaurora.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Joe Perches" <joe@perches.com>,
	"Dan Carpenter" <dan.carpenter@oracle.com>,
	"Peter Senna Tschudin" <peter.senna@gmail.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] platform: goldfish: pipe: add devicetree bindings
Date: Fri, 27 Nov 2015 10:17:44 -0800	[thread overview]
Message-ID: <56589E48.9000708@google.com> (raw)
In-Reply-To: <20151126083412.GB14945@lvm>

On 11/26/15 12:34 AM, Christoffer Dall wrote:
> On Wed, Nov 25, 2015 at 02:24:16PM -0600, Rob Herring wrote:
>>
>> The binding may be trivial, but there's a bigger question of whether
>> this is the right long term direction. For example is upstream QEMU
>> going to take all the Android pipe stuff? Couldn't virtio be used here
>> as the transport?
>>
>
> But I wonder if that should really block this from being merged?  The
> support may not be in QEMU but it's in the Android emulator and it would
> be a less broken implementation with these patches in the kernel than
> without, I think.
>
> -Christoffer
>

To add to Christoffer's point, we added these bindings so we don't need 
to rely on the goldfish virtual bus for probing anymore.

Switching from the goldfish virtual bus to Device-Tree already 
eliminates one big piece where the Android emulator has diverged from 
upstream qemu.  And on the kernel side, it means we don't need ARM and 
MIPS goldfish board code to instantiate the bus.

In the long term I'm happy to push the SDK team towards replacing the 
Android pipe with a virtio alternative.  (We've already been switching 
over to virtio for things like storage.)  But in the short term, we 
still need it.  And I don't think it benefits the mainline kernel if we 
have to maintain cleanup patches like this out-of-tree.

  reply	other threads:[~2015-11-27 18:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 19:59 [PATCH v2 1/1] platform: goldfish: pipe: add devicetree bindings Jin Qian
     [not found] ` <1448481582-16991-1-git-send-email-jinqian-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>
2015-11-25 20:24   ` Rob Herring
2015-11-26  8:34     ` Christoffer Dall
2015-11-27 18:17       ` Greg Hackmann [this message]
     [not found]         ` <56589E48.9000708-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2015-11-27 20:14           ` Rob Herring
2015-11-30 21:32   ` Rob Herring
2015-12-21 21:35 ` Greg Kroah-Hartman
2016-01-08 22:32   ` Jin Qian
2016-01-09  4:55     ` Greg Kroah-Hartman

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=56589E48.9000708@google.com \
    --to=ghackmann@google.com \
    --cc=alex.bennee@linaro.org \
    --cc=christoffer.dall@linaro.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jinqian@android.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=peter.senna@gmail.com \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).