From: Akshu Agrawal <akshu.agrawal@amd.com>
To: akshu.agrawal@amd.com
Cc: sboyd@kernel.org, rafael@kernel.org, rjw@rjwysocki.net,
lenb@kernel.org, mturquette@baylibre.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, rahul.tanwar@linux.intel.com
Subject: [0/4] Extend AMD SoC general purpose clk for all versions
Date: Fri, 31 Jul 2020 19:06:00 +0530 [thread overview]
Message-ID: <20200731133604.12512-1-akshu.agrawal@amd.com> (raw)
Hi,
This series of patch does the following:
1. Changes the name of the AMD SoC general purpose clk
from ST(a version of SoC) to FCH (name of the IP).
2. Then make the drivers support both older and newer versions of
SoC.
Thanks,
Akshu
Akshu Agrawal (4):
ACPI: APD: Change name from ST to FCH
clk: x86: Change name from ST to FCH
ACPI: APD: Add a fmw property is_raven
clk: x86: Support RV architecture
drivers/acpi/acpi_apd.c | 18 ++--
drivers/clk/x86/Makefile | 2 +-
drivers/clk/x86/clk-fch.c | 101 ++++++++++++++++++
drivers/clk/x86/clk-st.c | 78 --------------
.../platform_data/{clk-st.h => clk-fch.h} | 11 +-
5 files changed, 119 insertions(+), 91 deletions(-)
create mode 100644 drivers/clk/x86/clk-fch.c
delete mode 100644 drivers/clk/x86/clk-st.c
rename include/linux/platform_data/{clk-st.h => clk-fch.h} (51%)
--
2.20.1
next reply other threads:[~2020-07-31 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 13:36 Akshu Agrawal [this message]
2020-07-31 13:36 ` [v2 1/4] ACPI: APD: Change name from ST to FCH Akshu Agrawal
2020-07-31 13:36 ` [v2 2/4] clk: x86: " Akshu Agrawal
2020-07-31 13:36 ` [3/4] ACPI: APD: Add a fmw property is_raven Akshu Agrawal
2020-07-31 13:36 ` [v3 4/4] clk: x86: Support RV architecture Akshu Agrawal
2020-08-07 18:17 ` [0/4] Extend AMD SoC general purpose clk for all versions Rafael J. Wysocki
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=20200731133604.12512-1-akshu.agrawal@amd.com \
--to=akshu.agrawal@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rafael@kernel.org \
--cc=rahul.tanwar@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@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).