From: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Andy Gross <andy.gross@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
MSM <linux-arm-msm@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] soc: qcom: socinfo: add missing soc_id sysfs entry
Date: Tue, 24 Sep 2019 21:54:41 -0600 [thread overview]
Message-ID: <CAOCk7NoNX7+fxCYNOCMVCv1_-X3ZbaHwFjzWjMp6VKL6ZoroLA@mail.gmail.com> (raw)
In-Reply-To: <5d7fe5d1.1c69fb81.eca3b.1121@mx.google.com>
On Mon, Sep 16, 2019 at 3:44 PM Stephen Boyd <swboyd@chromium.org> wrote:
>
> Quoting Srinivas Kandagatla (2019-09-12 02:10:19)
> > looks like SoC ID is not exported to sysfs for some reason.
> > This patch adds it!
> >
> > This is mostly used by userspace libraries like SNPE.
>
> What is SNPE?
Snapdragon Neural Processing Engine. Pronounced "snap-e". Its
basically the framework someone goes through to run a neural network
on a Qualcomm mobile SoC. SNPE can utilize various hardware resources
such as the applications CPU, GPU, and dedicated compute resources
such as a NSP, if available. Its been around for over a year, and
much more information can be found by just doing a simple search since
SNPE is pretty much a unique search term currently.
next prev parent reply other threads:[~2019-09-25 3:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 9:10 [PATCH] soc: qcom: socinfo: add missing soc_id sysfs entry Srinivas Kandagatla
2019-09-16 19:43 ` Stephen Boyd
2019-09-25 3:54 ` Jeffrey Hugo [this message]
2019-09-26 17:57 ` Stephen Boyd
2019-09-26 18:18 ` Jeffrey Hugo
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=CAOCk7NoNX7+fxCYNOCMVCv1_-X3ZbaHwFjzWjMp6VKL6ZoroLA@mail.gmail.com \
--to=jeffrey.l.hugo@gmail.com \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=swboyd@chromium.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).