mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mauro Lima <mauro.lima@eclypsium.com>
Cc: broonie@kernel.org, linux-spi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] spi: intel: Fix device private data and PR_NUM for BXT
Date: Wed, 1 Feb 2023 07:48:39 +0200	[thread overview]
Message-ID: <Y9n9NyV4x7G2cS/J@black.fi.intel.com> (raw)
In-Reply-To: <20230201050455.505135-2-mauro.lima@eclypsium.com>

Hi Mauro,

Please call it "Broxton".

On Wed, Feb 01, 2023 at 02:04:54AM -0300, Mauro Lima wrote:
> Some private data fields have to change from bxt_info to cnl_info.
> Here is the list of Device IDs with the respective documentation taken for
> validation:
>     0xa0a4 - Intel® 500 Series Chipset Family On-Package Platform Controller Hub
>     0x02a4 - Intel® 400 Series Chipset Family On-Package PCH
>     0x06a4 - Intel® 400 Series Chipset Family Platform Controller Hub
>     0x34a4 - Intel® 495 Chipset Family On-Package
>     0xa3a4 - Intel® B460 and H410 Chipset
> 
> According to documentation BXT has five PR registers.

Here too, "Broxton".

> Signed-off-by: Mauro Lima <mauro.lima@eclypsium.com>

Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>

  reply	other threads:[~2023-02-01  5:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01  5:04 [PATCH 0/2] spi: intel: PCI driver housekeeping Mauro Lima
2023-02-01  5:04 ` [PATCH 1/2] spi: intel: Fix device private data and PR_NUM for BXT Mauro Lima
2023-02-01  5:48   ` Mika Westerberg [this message]
2023-02-01  5:04 ` [PATCH 2/2] spi: intel: Add support for controllers Mauro Lima
2023-02-01  5:49   ` Mika Westerberg
2023-02-01 14:27     ` ALOK TIWARI

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=Y9n9NyV4x7G2cS/J@black.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mauro.lima@eclypsium.com \
    /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

Powered by JetHome