public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: linux-arm-kernel@lists.infradead.org, Arnd Bergmann <arnd@arndb.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Francois Ozog <francois.ozog@linaro.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Etienne Carriere <etienne.carriere@st.com>,
	Jose Marinho <jose.marinho@arm.com>,
	linux-kernel@vger.kernel.org, harb@amperecomputing.com
Subject: Re: [PATCH v3] firmware: smccc: Add ARCH_SOC_ID support
Date: Tue, 30 Jun 2020 14:25:12 +0100	[thread overview]
Message-ID: <20200630132512.GB4188@bogus> (raw)
In-Reply-To: <20200625095939.50861-1-sudeep.holla@arm.com>

Hi Arnd,

On Thu, Jun 25, 2020 at 10:59:39AM +0100, Sudeep Holla wrote:
> SMCCC v1.2 adds a new optional function SMCCC_ARCH_SOC_ID to obtain a
> SiP defined SoC identification value. Add support for the same.
> 
> Also using the SoC bus infrastructure, let us expose the platform
> specific SoC atrributes under sysfs.
> 
> There are various ways in which it can be represented in shortened form
> for efficiency and ease of parsing for userspace. The chosen form is
> described in the ABI document.
> 

If you happy with this version, I can send PR for this along with the
clean up series that Greg and others have acked [1]

-- 
Regards,
Sudeep

[1] https://lore.kernel.org/linux-arm-kernel/20200527165238.GA21440@bogus

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2020-06-30 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25  9:59 [PATCH v3] firmware: smccc: Add ARCH_SOC_ID support Sudeep Holla
2020-06-30 13:25 ` Sudeep Holla [this message]

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=20200630132512.GB4188@bogus \
    --to=sudeep.holla@arm.com \
    --cc=arnd@arndb.de \
    --cc=etienne.carriere@st.com \
    --cc=francois.ozog@linaro.org \
    --cc=harb@amperecomputing.com \
    --cc=jose.marinho@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mark.rutland@arm.com \
    /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