[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK=WgbbP8UQAbFauE80PnF5bj3FTAkB2KfF0kFE8Pt23jQrDhA@mail.gmail.com>
Date: Thu, 30 Oct 2014 15:34:12 +0200
From: Ohad Ben-Cohen <ohad@...ery.com>
To: Bjorn Andersson <bjorn.andersson@...ymobile.com>
Cc: Kumar Gala <galak@...eaurora.org>,
Andy Gross <agross@...eaurora.org>,
Arnd Bergmann <arnd@...db.de>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Grant Likely <grant.likely@...aro.org>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Lee Jones <lee.jones@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Pawel Moll <pawel.moll@....com>,
Rob Herring <robh+dt@...nel.org>,
Samuel Ortiz <sameo@...ux.intel.com>,
Kevin Hilman <khilman@...prootsystems.com>
Subject: Re: [RFC 5/7] soc: qcom: Add Shared Memory Driver
Hi Bjorn,
On Thu, Oct 30, 2014 at 2:38 AM, Bjorn Andersson
<bjorn.andersson@...ymobile.com> wrote:
> My concern is that merging SMD into rpmsg will still give us two different
> solutions, except that they will be deeply tangled.
I agree.
It's very clear that SMD and rpmsg are different. But fundamentally,
they do exactly the same: new messages are placed in a ring buffer and
then an interrupt is triggered.
If Qualcomm wanted to adopt rpmsg I'm confident there would have been
no technical barriers to do so.
But given that SMD is not going anywhere, I personally hope that you
could at least avoid having two different implementations of it merged
upstream.
Good luck,
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists