Messages in this thread | | | From | Alexander Williams <> | Date | Wed, 28 Apr 2021 08:58:32 -0700 | Subject | Re: [PATCH 1/3] mtd: spi-nor: Export SFDP access to sysfs |
| |
On Wed, Apr 28, 2021 at 8:51 AM Michael Walle <michael@walle.cc> wrote: > > Am 2021-04-28 17:37, schrieb Alexander Williams: > > On Wed, Apr 28, 2021 at 12:58 AM Michael Walle <michael@walle.cc> > > wrote: > >> > >> Hi Alexander, > >> > >> Am 2021-04-28 07:27, schrieb Alexander Williams: > >> > Add the ability to specify a technology-specific attribute_group, and > >> > expose the SFDP through spi-nor's private group. This enables user > >> > space > >> > to have full access to the contents of the SFDP, so all information is > >> > available without regard for whether the kernel supports parsing it. > >> > >> Please see: > >> https://lore.kernel.org/linux-mtd/20210318092406.5340-1-michael@walle.cc/ > > > > Thanks for the pointer! Sorry I didn't see that patch series already: > > My search > > skills need some work... In any case, there's no good reason for me to > > duplicate > > work. > > > > I should probably comment on that series directly, but I'll note that > > one thing > > I tried to do with the sysfs attributes here was avoid racing with user > > space. > > The uevent is suppressed until all the related files are created in > > sysfs. See > > http://kroah.com/log/blog/2013/06/26/how-to-create-a-sysfs-file-correctly/ > > for > > Greg's explanation of a scenario. > > Sure, reviews and remarks are always welcome. Btw. what is patch 2/3 and > 3/3? > I couldn't find it on the LKML.
There are none. I goofed and forgot to fix up the subject line. The two commits that followed merely added quick-and-dirty SFDP support to intel-spi.c to enable testing on one of the platforms I had lying around.
--Alex
| |