[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a0WKODYvHzsf05QZ1dFh5uMQu2z7dzO1DMp1E9TWCrsPQ@mail.gmail.com>
Date: Tue, 30 Jun 2020 17:00:14 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Daniel Gutson <daniel@...ypsium.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Derek Kiernan <derek.kiernan@...inx.com>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Richard Hughes <hughsient@...il.com>,
Alex Bazhaniuk <alex@...ypsium.com>
Subject: Re: [PATCH] SPI LPC information kernel module
On Tue, Jun 30, 2020 at 4:43 PM Daniel Gutson <daniel@...ypsium.com> wrote:
> On Tue, Jun 30, 2020 at 5:56 AM Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
>> On Mon, Jun 29, 2020 at 07:59:32PM -0300, Daniel Gutson wrote:
>> Why is this going in securityfs at all? Why not just sysfs as it is a
>> CPU attribute, right?
>
> Richard already discussed that, but "it" is not only (one) CPU attribute, are SPI chip
> settings and attributes coming from the firmware.
> Please note that I wanted to submit the minimum patch, but I need to add more attributes.
Why can't the SPI chip settings be attributes of the SPI chip device in sysfs?
Which firmware are you actually talking about here? Do you mean firmware running
on a device behind the SPI controller?
Arnd
Powered by blists - more mailing lists