From: Stephen Boyd <sboyd@kernel.org>
To: Andy Shevchenko <andy@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Mark Gross <markgross@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
platform-driver-x86@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 1/1] platform/x86: Drop the PMC_ATOM Kconfig option
Date: Wed, 18 May 2022 14:00:06 -0700 [thread overview]
Message-ID: <20220518210007.E4BDCC34118@smtp.kernel.org> (raw)
In-Reply-To: <20220503114607.98844-2-hdegoede@redhat.com>
Quoting Hans de Goede (2022-05-03 04:46:07)
> The def_bool y PMC_ATOM Kconfig option provides a couple of symbols used
> by the code enabled by the X86_INTEL_LPSS option and it registers some
> clocks. These clocks are only registered on Bay Trail, Cherry Trail and
> Brasswell Intel SoCs and kernels targeting these SoCs must always have
> the X86_INTEL_LPSS option enabled otherwise many things will not work.
>
> Building the PMC_ATOM code on kernels which are not targeting the
> mentioned SoCs and which do not have the X86_INTEL_LPSS enabled is
> not useful.
>
> This means that we can simplify things by replacing the PMC_ATOM Kconfig
> option in Makefiles with X86_INTEL_LPSS and then drop the option.
>
> Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
Acked-by: Stephen Boyd <sboyd@kernel.org>
next prev parent reply other threads:[~2022-05-18 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 11:46 [PATCH 0/1] platform/x86: Drop the PMC_ATOM Kconfig option Hans de Goede
2022-05-03 11:46 ` [PATCH 1/1] " Hans de Goede
2022-05-18 21:00 ` Stephen Boyd [this message]
2022-05-19 18:03 ` Hans de Goede
-- strict thread matches above, loose matches on Subject: below --
2022-05-03 14:02 [PATCH 0/1] " Hans de Goede
2022-05-03 14:02 ` [PATCH 1/1] " Hans de Goede
2022-05-03 14:09 ` Andy Shevchenko
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=20220518210007.E4BDCC34118@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-clk@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=mturquette@baylibre.com \
--cc=paul.gortmaker@windriver.com \
--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