| Age | Commit message (Collapse) | Author |
|---|
|
There's no reason for the x1000 feature to include anything from
common-pc, and it causes unnecessary bloat.
If a particular bsp requires anything included here, it should include
it explicitly.
A representative x1000 platform, the Galileo2, works fine without any
of this.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Quark and tiny have no need or desire to drag around pointless
features like eg20t, so use the common-drivers-32-essential feature
instead of the full common-drivers-32.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The intel-common-drivers-32 contains features such as eg20t that that
aren't applicable to some platforms such as quark, and unwanted in a
tiny configuration.
Splitting out and reusing an 'essential' subset allows them to include
only those features.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Add a feature for enabling debug files to be generated by kernel LTO.
To enable LTO debug for the kernel, add (for example):
KERNEL_FEATURES_append_galileo += " features/lto-debug.scc"
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Add features/lto/lto-disable, a feature to disable LTO. This isn't
really needed, since it's the default, but it makes kernel feature
selection for currently incompatible features such as tracing less
confusing - disable by adding (for example):
KERNEL_FEATURES_append_galileo += " features/lto/lto-disable.scc"
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Add a feature allowing the enablement of LTO (Link-Time Optimization)
for the Linux kernel. To enable LTO for the kernel, add (for
example):
KERNEL_FEATURES_append_galileo += " features/lto.scc"
Note that this feature requires special toolchain support (HJ Lu's
Linux binutils and gcc >= 4.9).
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
This is incompatible with preempt-rt and would be a mess to fix any
other way. If we were to move CONFIG_LEDS_TRIGGER_CPU to a new feature
such as leds-full, it would require us to add leds-full to every non-rt
BSP wanting leds support, and -rt BSPs would need the feature without
it. Setting "# CONFIG_LEDS_TRIGGER_CPU is not set" also doesn't work, as
it depends on !PREEMPT_RT_BASE, making it completely unavailable for
setting and still giving us a warning in kernel_configcheck.
All this option does is allow CPUs to trigger LEDs based on their usage,
so it is not a major loss anyway.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The newer BMP280 IIO driver appears to support the BMP085 chip as well,
and the old BMP085 driver cannot be enabled at the same time, giving us
configcheck warnings if we try.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Some drivers (e.g. INV_MPU6050_I2C) rely on this, and in most cases
this gets selected automatically, but in some cases its not and it
causes a configcheck warning.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The inclusion of the mei feature was invalid, since it is missing
the "include" keyword .. adding it gets us the features we expect
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Enable Intel Whiskey Cove PMIC TMU driver as module.
Signed-off-by: Nilesh Bacchewar <nilesh.bacchewar@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
In mei-me.cfg, CONFIG_PCI was mistakenly set to =m when its a boolean.
In bosch-pressure-sensor-i2c, change CONFIG_BMP085 to =m instead of =y,
as its dependency is a module. Also attempt to disable BMP280, as it
conflicts with the BMP085 driver and throws a warning.
In x1000.cfg, remove CONSOLE related 'is not set' CONFIGs. VGA_CONSOLE
can't be disabled without enabling EXPERT (and therefore DEBUG_KERNEL),
which we don't want normally. The other two configurations are missing
dependencies, so they don't get set anyway, but cause warnings.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
IOSF_MBI gets selected by CONFIG_X86_INTEL_LPSS, forcing it to =y and
giving us a warning in the kernel_configcheck stage. Fix this by setting
CONFIG_IOSF_MBI=y.
INV_MPU6050, MPL115, and NFC_PN533 all had their core driver separated
from specific implementations such as I2C, SPI, and USB, and can only
be enabled by adding one or more of those implementations. This means
we weren't getting the drivers and warnings occurred during the
kernel_configcheck stage. Fix this by adding the implementations that
were separated.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The kernel_configcheck complains about these unnecessary kernel options.
The final .config is the same with or without them.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
1/1 [
Author: Jianxun Zhang
Email: jianxun.zhang@linux.intel.com
Subject: uvesafb: provide option to specify timeout for task completion
Date: Thu, 25 Aug 2016 15:30:55 -0700
We try to make this change a generic extension, but it is
actually for a corner case. When a VM (qemu) gets a very limited
cpu bandwidth from host, which could be under a heavy load, the
existing 5000 ms timeout could occur and trigger error messages
in the task function's callers.
This change adds a new timeout parameter so that we can tweak
the value as a workaround or for troubleshooting purposes. In
the infinite wait case, A warning message is printed at 5000ms
interval.
In real world, the current 5 sec is generous enough for a video
request in my opinion, so this change could not be very useful.
Upstream Status: Inappropriate
Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
In a follow-up to e9ec769926b2378e63380bd7762ce7ce201af151
explicitly disable CONFIG_64BIT on Quark too.
Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
I missed these in my first pass. This should fix the remaining warnings
that occur with the intel-corei7-64 configurations. The ISDN
configurations might need to be broken out into their own feature but
for now just enable them as dependencies for BT_CMTP.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The new kernel tools do not automagically do this, causing dependency
issues and architecture mismatch errors. Explicitly disable the CONFIG
to fix it.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: fli <fupan.li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
No need to have these similar configurations spread all around. Also
solves a warning where skylake tried to set MFD_INTEL_LPSS to build as
a module, but MFD_INTEL_LPSS_PCI in broxton hits a select and forces it
to built in.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
CONFIG_IIO_BUFFER_CB is a tristate and CONFIG_IIO is set to =m, so
CONFIG_IIO_BUFFER_CB gets forced to =m anyway. Fixes a
kernel_configcheck warning we get with the new tools.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
For now just add the minimum configuration necessary to support other
6LoWPAN options we are already trying to enable. Fixes some
configuration warnings that occur due to missing dependencies.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
It results in errors while parsing the scc files for patches.
Signed-off-by: Anuj Mittal <anujx.mittal@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Pranav Tipnis <pranav.tipnis@intel.com>
Signed-off-by: Bruce Ashfield <bruce@zedd.org>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Enable some popular sensor drivers(including staging iio drivers)
Signed-off-by: Yong Li <yong.b.li@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Legacy PTY support adds overhead to the kernel and delays to
the boot process. So we disable it by default.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
There is no need to include kernel-debug.scc into printk.scc as
options from printk.cfg don't depend on CONFIG_DEBUG* options from
kernel-debug.cfg
Moreover, enabling CONFIG_DEBUG* options makes kernel much bigger,
increases build time and consumed a lot of additional disk space.
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
1. Separate mei-me and mei-txe support and enable them only on
appropriate platforms
2. Amt is not enabled on all platforms and exists only on BigCores over
mei-me.
To not break anything we left amt.cfg in
bsp/intel-common/intel-common-drivers.scc, but this should be fine tuned
later.
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The mei storage proxy driver is required on some of
bxt-m platforms where cse firmware and bios stores
it's data on the RPMB partition.
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
following warning msg is found when compiling the kernel for qemumips:
.../drivers/input/mousedev.c:749:15: warning: passing argument 1 of
'__cpu_to_le16p' from incompatible pointer type
[-Wincompatible-pointer-types]
convert the function's parameter to (__u16 *) to fix this warning.
Signed-off-by: Zhenbo Gao <zhenbo.gao@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Replay Protected Memory Block (RPMB) subsystem
The feature provides 3 configurations
1. Base : enables the subsystem
2. UAPI : enables user space api via /dev/rpmbX
3. Sim : RPMB HW simulation device
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The patch [menuconfig,check-lxdiaglog.sh: Allow specification of ncurses
location] has been carried since the 3.14 kernel. As it has been updated
multiple times, the if block checking for CROSS_CURSES_LIB has migrated
to an invalid location in the checks.
This change moves it back on top where it belongs.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Enable Intel Whiskey Cove PMIC gpio driveri as module.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
ARCH=x86 defaults to 64 bit on modern kernels. So we need to
explicitly disable 64bit in common-pc if we want a 32bit build
(common-pc builds with ARCH=x86, not ARCH=i386)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Rebecca Chang Swee Fun <rebecca.swee.fun.chang@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Disable Intel Whiskey Cove PMIC gpio driver.
Signed-off-by: Nilesh Bacchewar <nilesh.bacchewar@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
Tom Zanussi
Bruce Ashfield
California Sullivan
Nilesh Bacchewar
Kevin Hao
Alejandro Hernandez
Mikko Ylinen
fli
Anuj Mittal
Pranav Tipnis
Yong Li
Ed Bartosh
Tomas Winkler
Rebecca Chang Swee Fun