From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mario.Limonciello@dell.com
Cc: hughsient@gmail.com, platform-driver-x86@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] platform/x86: Export LPC attributes for the system SPI chip
Date: Mon, 11 May 2020 13:41:13 +0300 [thread overview]
Message-ID: <20200511104113.GJ487496@lahna.fi.intel.com> (raw)
In-Reply-To: <34e4985da20747a780971b8ce7cd83ab@AUSX13MPC105.AMER.DELL.COM>
On Fri, May 08, 2020 at 05:27:12PM +0000, Mario.Limonciello@dell.com wrote:
> > -----Original Message-----
> > From: platform-driver-x86-owner@vger.kernel.org <platform-driver-x86-
> > owner@vger.kernel.org> On Behalf Of Mika Westerberg
> > Sent: Friday, May 8, 2020 3:20 AM
> > To: Limonciello, Mario
> > Cc: hughsient@gmail.com; platform-driver-x86@vger.kernel.org; linux-
> > security-module@vger.kernel.org
> > Subject: Re: [PATCH] platform/x86: Export LPC attributes for the system
> > SPI chip
> >
> >
> > [EXTERNAL EMAIL]
> >
> > On Thu, May 07, 2020 at 08:03:21PM +0000, Mario.Limonciello@dell.com
> > wrote:
> > > > -----Original Message-----
> > > > From: Richard Hughes <hughsient@gmail.com>
> > > > Sent: Thursday, May 7, 2020 2:49 PM
> > > > To: Limonciello, Mario
> > > > Cc: Platform Driver; linux-security-module;
> > mika.westerberg@linux.intel.com
> > > > Subject: Re: [PATCH] platform/x86: Export LPC attributes for the
> > system SPI
> > > > chip
> > > >
> > > >
> > > > [EXTERNAL EMAIL]
> > > >
> > > > On Thu, 7 May 2020 at 20:22, <Mario.Limonciello@dell.com> wrote:
> > > > > By default the driver exposes SPI serial flash contents as read-
> > only but it
> > > > can
> > > > > be changed from kernel command line, passing “intel-
> > spi.writeable=1”.
> > > >
> > > > Ahh, that was the bit I didn't know; having the SPI as readonly by
> > > > default is certainly a good idea, and probably sane enough to enable
> > > > for Fedora/RHEL as you still need to "do" something manual to enable
> > > > SPI writing. I guess I can add my securityfs additions to
> > > > intel-spi-pci.c with Mikas approval.
> > > >
> > > > Richard
> > >
> > > Mika,
> > >
> > > Since you're being joined into the thread late, here is the context:
> > > https://www.spinics.net/lists/platform-driver-x86/msg21646.html
> >
> > Thanks for the information. I actually prefer that this would be in a
> > separate driver because I do not want distros to enable intel-spi just
> > for this. It is really only meant for special setups where firmware
> > upgrade/access flow has been thoroughly tested.
>
> Mika,
>
> Thanks for those comments and context on that driver. Considering this,
> what do you think about as part of this new driver, moving the list of
> supported IDs in there to something that can be sourced by both drivers?
> I think it should help avoid having to keep the two lists fully in sync
> as new silicon comes out.
Hi,
Since this is binding to the LPC/eSPI device I think you may be adding
this functionality to drivers/mfd/lpc_ich.c. It is also filling the data
for intel-spi so it is natural place to re-use the code. I actually
think it already has some of these PCI IDs.
prev parent reply other threads:[~2020-05-11 10:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 15:52 [PATCH] platform/x86: Export LPC attributes for the system SPI chip Richard Hughes
2020-05-06 16:29 ` Andy Shevchenko
2020-05-06 16:39 ` Richard Hughes
2020-05-07 17:05 ` Javier Martinez Canillas
2020-05-07 17:22 ` Andy Shevchenko
2020-05-07 17:28 ` Javier Martinez Canillas
2020-05-07 17:45 ` Mario.Limonciello
2020-05-07 18:47 ` Richard Hughes
2020-05-07 19:22 ` Mario.Limonciello
2020-05-07 19:49 ` Richard Hughes
2020-05-07 20:03 ` Mario.Limonciello
2020-05-08 8:20 ` Mika Westerberg
2020-05-08 16:15 ` Richard Hughes
2020-05-11 10:45 ` Mika Westerberg
2020-05-11 15:40 ` Richard Hughes
2020-05-11 16:28 ` Mika Westerberg
2020-05-11 20:08 ` Richard Hughes
2020-05-12 6:44 ` Mika Westerberg
2020-05-12 20:37 ` Richard Hughes
2020-05-08 17:27 ` Mario.Limonciello
2020-05-11 10:41 ` Mika Westerberg [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=20200511104113.GJ487496@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Mario.Limonciello@dell.com \
--cc=hughsient@gmail.com \
--cc=linux-security-module@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).