linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	Boris Brezillon <boris.brezillon@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH] spi-nor: intel-spi: Add support for Intel Ice Lake SPI serial flash
Date: Tue, 28 Aug 2018 21:20:17 +0200	[thread overview]
Message-ID: <39875af1-731d-a5b7-7b10-13701b913751@gmail.com> (raw)
In-Reply-To: <20180828165959.GG2283@lahna.fi.intel.com>

On 08/28/2018 06:59 PM, Mika Westerberg wrote:
> On Tue, Aug 28, 2018 at 06:56:38PM +0200, Marek Vasut wrote:
>> On 08/28/2018 06:50 PM, Mika Westerberg wrote:
>>> Intel Ice Lake exposes the SPI serial flash controller as a PCI device
>>> in the same way than Intel Denverton. Add Ice Lake SPI serial flash PCI
>>> ID to the driver list of supported devices.
>>>
>>> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
>>
>> This should probably go through trivial patches ML, no ?
> 
> Hmm, what do you mean? This is not a typo fix or similar but adds a new
> PCI ID to the driver.

I mean, adding PCI IDs might be considered trivial. But if you want it
to go through MTD, fine:

Acked-by: Marek Vasut <marek.vasut@gmail.com>

>> Also, CC Stable.
> 
> OK.
> 
>>> ---
>>>  drivers/mtd/spi-nor/intel-spi-pci.c | 1 +
>>>  1 file changed, 1 insertion(+)
>>>
>>> diff --git a/drivers/mtd/spi-nor/intel-spi-pci.c b/drivers/mtd/spi-nor/intel-spi-pci.c
>>> index c0976f2e3dd1..872b40922608 100644
>>> --- a/drivers/mtd/spi-nor/intel-spi-pci.c
>>> +++ b/drivers/mtd/spi-nor/intel-spi-pci.c
>>> @@ -65,6 +65,7 @@ static void intel_spi_pci_remove(struct pci_dev *pdev)
>>>  static const struct pci_device_id intel_spi_pci_ids[] = {
>>>  	{ PCI_VDEVICE(INTEL, 0x18e0), (unsigned long)&bxt_info },
>>>  	{ PCI_VDEVICE(INTEL, 0x19e0), (unsigned long)&bxt_info },
>>> +	{ PCI_VDEVICE(INTEL, 0x34a4), (unsigned long)&bxt_info },
>>>  	{ PCI_VDEVICE(INTEL, 0xa1a4), (unsigned long)&bxt_info },
>>>  	{ PCI_VDEVICE(INTEL, 0xa224), (unsigned long)&bxt_info },
>>>  	{ },
>>>
>>
>>
>> -- 
>> Best regards,
>> Marek Vasut


-- 
Best regards,
Marek Vasut

  reply	other threads:[~2018-08-28 20:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 16:50 [PATCH] spi-nor: intel-spi: Add support for Intel Ice Lake SPI serial flash Mika Westerberg
2018-08-28 16:56 ` Marek Vasut
2018-08-28 16:59   ` Mika Westerberg
2018-08-28 19:20     ` Marek Vasut [this message]
2018-08-29  9:09       ` Mika Westerberg
2018-08-29  9:17   ` Boris Brezillon
2018-08-29 10:28     ` Joakim Tjernlund
2018-08-29 10:33       ` Boris Brezillon
2018-08-29 10:37         ` Marek Vasut
2018-08-29 10:44         ` Joakim Tjernlund
2018-08-29 10:54           ` Marek Vasut
2018-08-29 11:46             ` Boris Brezillon
  -- strict thread matches above, loose matches on Subject: below --
2018-06-27 12:11 Mika Westerberg

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=39875af1-731d-a5b7-7b10-13701b913751@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=boris.brezillon@bootlin.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=richard@nod.at \
    /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).