From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: hdegoede@redhat.com, markgross@kernel.org,
ilpo.jarvinen@linux.intel.com, andriy.shevchenko@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH v2 0/4] Minor SST optimizations
Date: Tue, 3 Oct 2023 09:32:30 -0700 [thread overview]
Message-ID: <20231003163234.1856669-1-srinivas.pandruvada@linux.intel.com> (raw)
Contains some minor changes to use SST for non dynamic use cases
for display purpose and remove hardcoded size for map.
v2
Update commit description, no code change
Added a new patch which was independent before
Srinivas Pandruvada (4):
platform/x86: ISST: Use fuse enabled mask instead of allowed levels
platform/x86: ISST: Allow level 0 to be not present
platform/x86: intel_speed_select_if: Remove hardcoded map size
platform/x86: intel_speed_select_if: Use devm_ioremap_resource
.../x86/intel/speed_select_if/isst_if_mmio.c | 21 ++++++++++++-------
.../intel/speed_select_if/isst_tpmi_core.c | 5 +----
2 files changed, 14 insertions(+), 12 deletions(-)
--
2.41.0
next reply other threads:[~2023-10-03 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 16:32 Srinivas Pandruvada [this message]
2023-10-03 16:32 ` [PATCH v2 1/4] platform/x86: ISST: Use fuse enabled mask instead of allowed levels Srinivas Pandruvada
2023-10-03 16:32 ` [PATCH v2 2/4] platform/x86: ISST: Allow level 0 to be not present Srinivas Pandruvada
2023-10-03 16:32 ` [PATCH v2 3/4] platform/x86: intel_speed_select_if: Remove hardcoded map size Srinivas Pandruvada
2023-10-03 16:32 ` [PATCH v2 4/4] platform/x86: intel_speed_select_if: Use devm_ioremap_resource Srinivas Pandruvada
2023-10-04 9:08 ` [PATCH v2 0/4] Minor SST optimizations Ilpo Järvinen
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=20231003163234.1856669-1-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@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
all inboxes | Powered by JetHome®