From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Olof Johansson <olof@lixom.net>
Cc: Andy Gross <agross@kernel.org>,
arm@kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
Kevin Hilman <khilman@baylibre.com>
Subject: Re: [GIT PULL] Qualcomm ARM64 Defconfig updates for 5.5
Date: Wed, 6 Nov 2019 15:18:05 -0800 [thread overview]
Message-ID: <20191106231805.GG36595@minitux> (raw)
In-Reply-To: <20191106220406.4aoq5suvwww6c3ov@localhost>
On Wed 06 Nov 14:04 PST 2019, Olof Johansson wrote:
> On Wed, Nov 06, 2019 at 01:33:56PM -0600, Andy Gross wrote:
> > The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
> >
> > Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git tags/qcom-arm64-defconfig-for-5.5
> >
> > for you to fetch changes up to a36612b7469cf76953cf237a2b9a62f6c97730bb:
> >
> > arm64: defconfig: Enable Qualcomm watchdog driver (2019-10-20 23:04:59 -0700)
> >
> > ----------------------------------------------------------------
> > Qualcomm ARM64 Based defconfig Updates for v5.5
> >
> > * Enable Qualcomm cpufreq, watchdog, prng, socinfo, SPI, and QSPI controllers
> > * Enable SN65DSI86 display bridge
> > * Enable QCA Bluetooth over Uart
> > * Enable various Qualcomm remoteproc dependencies
> >
> > ----------------------------------------------------------------
> > Bjorn Andersson (6):
> > arm64: defconfig: Enable Qualcomm remoteproc dependencies
> > arm64: defconfig: Enable Qualcomm SPI and QSPI controller
> > arm64: defconfig: Enable Qualcomm socinfo driver
> > arm64: defconfig: Enable Qualcomm CPUfreq HW driver
>
>
> Hi, this turns on the driver as =y, when the option is tristate. Other
> cpufreq drivers are also modules. Is this driver truly needed to be
> a built-in for a generic defconfig?
>
linux-next has 7 CPUfreq drivers =y and 3 =m, so I picked =y for the
Qualcomm by majority choice. And the same driver is used by a number of
different Qualcomm platforms, so the growth looks to be bounded.
It should work as =m as well, but we would need to validate that.
Regards,
Bjorn
next prev parent reply other threads:[~2019-11-06 23:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 19:33 [GIT PULL] Qualcomm ARM64 Defconfig updates for 5.5 Andy Gross
2019-11-06 19:33 ` [GIT PULL] Qualcomm ARM64 DT " Andy Gross
2019-11-07 14:06 ` Amit Kucheria
2019-11-08 3:18 ` Andy Gross
2019-12-10 10:57 ` Stephan Gerhold
2019-12-10 17:36 ` Amit Kucheria
2019-12-10 18:17 ` Bjorn Andersson
2019-12-10 21:00 ` Olof Johansson
2019-12-11 6:26 ` Bjorn Andersson
2019-12-11 10:00 ` Amit Kucheria
2019-11-06 19:33 ` [GIT PULL] Qualcomm Defconfig " Andy Gross
2019-11-06 19:33 ` [GIT PULL] Qualcomm Driver " Andy Gross
2019-11-06 19:34 ` [GIT PULL] Qualcomm Device Tree " Andy Gross
2019-11-06 22:04 ` [GIT PULL] Qualcomm ARM64 Defconfig " Olof Johansson
2019-11-06 23:18 ` Bjorn Andersson [this message]
2019-12-06 5:02 ` Bjorn Andersson
2019-12-06 16:32 ` Olof Johansson
2019-12-06 17:28 ` Bjorn Andersson
2019-12-06 17:57 ` Amit Kucheria
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=20191106231805.GG36595@minitux \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=olof@lixom.net \
/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).