[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a20R+H6m5GZj2_0w3s-xF+J_qSVrQH8EjyQXe6+9WTYxw@mail.gmail.com>
Date: Mon, 18 May 2020 11:30:21 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Sudeep Holla <sudeep.holla@....com>
Cc: Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Steven Price <steven.price@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
harb@...erecomputing.com
Subject: Re: [PATCH v4 7/7] firmware: smccc: Add ARCH_SOC_ID support
On Mon, May 18, 2020 at 11:12 AM Sudeep Holla <sudeep.holla@....com> wrote:
> +static ssize_t
> +jep106_cont_bank_code_show(struct device *dev, struct device_attribute *attr,
> + char *buf)
> +{
> + return sprintf(buf, "0x%02x\n", JEP106_BANK_CONT_CODE(soc_id_version));
> +}
> +
> +static DEVICE_ATTR_RO(jep106_cont_bank_code);
> +
> +static ssize_t
> +jep106_identification_code_show(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + return sprintf(buf, "0x%02x\n", JEP106_ID_CODE(soc_id_version));
> +}
I think we should try hard to avoid nonstandard attributes for the soc device.
Did you run into a problem with finding one of the existing attributes
that can be used to hold the fields?
Arnd
Powered by blists - more mailing lists