All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <swboyd@chromium.org>
To: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
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: Thu, 26 Sep 2019 10:57:38 -0700	[thread overview]
Message-ID: <5d8cfc13.1c69fb81.73236.ab28@mx.google.com> (raw)
In-Reply-To: <CAOCk7NoNX7+fxCYNOCMVCv1_-X3ZbaHwFjzWjMp6VKL6ZoroLA@mail.gmail.com>

Quoting Jeffrey Hugo (2019-09-24 20:54:41)
> 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.

I wouldn't mind if it was still spelled out instead of just as an
acronym. Who knows, a few years from now it may not be a unique acronym
and then taking the extra few seconds to write it out once would have
saved future effort.


  reply	other threads:[~2019-09-26 17:57 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
2019-09-26 17:57     ` Stephen Boyd [this message]
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=5d8cfc13.1c69fb81.73236.ab28@mx.google.com \
    --to=swboyd@chromium.org \
    --cc=andy.gross@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=jeffrey.l.hugo@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.kandagatla@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.