Age | Commit message (Collapse) | Author |
|
set CONFIG_REGULATOR_FIXED_VOLTAGE=y so that fixed
regulator driver is built into kernel image, not as a module.
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Because latest kernel has been upgraded to v5.8, update
kernel config for raspberry pi4 platform accordingly.
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Enable phy driver for raspberry pi4 platform.
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Kernel version has beed upgraded to v5.8, it is need to enable
CONFIG_MEDIA_PLATFORM_SUPPORT to support media related
features on renesas-rcar platform.
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
In order to match with latest kernel v5.7, some kernel configs
need to be updated.
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
This will enable CONFIG_ICE=m for intel-x86 bsp.
Signed-off-by: Yongxin Liu <yongxin.liu@windriver.com>
Signed-off-by: Liwei Song <liwei.song@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Yongxin Liu <yongxin.liu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
intel-corei7-64-standard.scc
CONFIG_INTEL_SPEED_SELECT_INTERFACE depends on x86-64.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
This will enable various USB web camera support for intel-x86 bsp.
Signed-off-by: Liwei Song <liwei.song@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
In latest kernel v5.7, CONFIG_ARCH_R8A7795 is removed and
splited into 2 configs CONFIG_ARCH_R8A77950/1.
The config CONFIG_ARCH_R8A7796 is replaced by
CONFIG_ARCH_R8A77960.
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
drivers/usb/dwc3/drd.c invokes functions defined in
drivers/usb/roles/class.c. So, enable the related kernel config.
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
A System Trace Module (STM) is a device exporting data in System Trace Protocol
(STP) format as defined by MIPI STP standards.Examples of such devices are
Intel(R) Trace Hub and Coresight STM.
And the Intel(R) Software Trace Hub uses stm class device to interface with its
sources.
Signed-off-by: Jun Miao <jun.miao@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Intel Trace Hub is a new concept/mechanism, used to transport messages from the
SoC to external monitor through a USB connector.
Add the Intel Trace Hub support on Tiger Lake UP3/UP4 Platform.
Signed-off-by: Jun Miao <jun.miao@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Enable the following config to support the "legency mcelog" and
"recovery from hardware memory errors":
CONFIG_X86_MCELOG_LEGACY=y
CONFIG_MEMORY_FAILURE=y
CONFIG_HWPOISON_INJECT=m
Signed-off-by: Liwei Song <liwei.song@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
1/1 [
Author: Jack Tan
Email: jack.tan@windriver.com
Subject: mti_malta32: fix the pci resource conflicts
Date: Wed, 10 Mar 2010 15:05:39 +0800
commit id 79896cf42f use request_resource() to replace the
insert_resource() in pci_claim_resource(). But this does
not fit the malta pci. With the new request_resource()
kernel allocate a collision io resource for PCI ethernet.
This disturb the PCI io space. One device use 0x1000 - 0x103f
and the PCI ethernet use 0x1020 - 0x103f and this is cause the
ethernet can't be accessed.
This fix supplies a fixup function to fix the ioport collision.
The old kernel log:
pci 0000:00:0a.1: BAR 4: assigned [io 0x1040-0x104f]
pci 0000:00:0a.1: BAR 4: set to [io 0x1040-0x104f] (PCI address [0x1040-0x104f]
pci 0000:00:0a.2: BAR 4: assigned [io 0x1000-0x101f]
pci 0000:00:0a.2: BAR 4: set to [io 0x1000-0x101f] (PCI address [0x1000-0x101f]
pci 0000:00:0a.3: address space collision: [io 0x1000-0x103f] already in use
pci 0000:00:0a.3: quirk: [io 0x1000-0x103f] claimed by PIIX4 ACPI
pci 0000:00:0a.3: address space collision: [io 0x1100-0x110f] already in use
pci 0000:00:0a.3: quirk: [io 0x1100-0x110f] claimed by PIIX4 SMB
pci 0000:00:0a.3: BAR 7: [io 0x1000-0x103f] has bogus alignment
pci 0000:00:0a.3: BAR 8: [io 0x1100-0x110f] has bogus alignment
pci 0000:00:0b.0: BAR 0: assigned [io 0x1020-0x103f]
pci 0000:00:0b.0: BAR 0: set to [io 0x1020-0x103f] (PCI address [0x1020-0x103f]
pci 0000:00:0b.0: BAR 1: assigned [mem 0x10111000-0x1011101f]
pci 0000:00:0b.0: BAR 1: set to [mem 0x10111000-0x1011101f] (PCI address [0x10111000-0x1011101f]
pci 0000:00:0b.0: BAR 6: assigned [mem 0x10000000-0x100fffff pref]
pci 0000:00:0c.0: BAR 0: assigned [mem 0x10110000-0x10110fff]
pci 0000:00:0c.0: BAR 0: set to [mem 0x10110000-0x10110fff] (PCI address [0x10110000-0x10110fff]
pci 0000:00:0c.0: BAR 1: assigned [mem 0x10100000-0x1010ffff]
pci 0000:00:0c.0: BAR 1: set to [mem 0x10100000-0x1010ffff] (PCI address [0x10100000-0x1010ffff]
......
pcnet32.c:v1.35 21.Apr.2008 tsbogend@alpha.franken.de
pcnet32: No access methods
......
......
And a fixup to the original change:
[
mips: malta PCI fixup, fix __init annotation warning
Currently we see the following link warning:
WARNING: vmlinux.o(.pci_fixup_final+0xefc): Section mismatch in
reference from the variable __pci_fixup_malta_pcnet32_ioports_fixup164
to the function .init.text:malta_pcnet32_ioports_fixup()
The variable __pci_fixup_malta_pcnet32_ioports_fixup164 references
a function __init malta_pcnet32_ioports_fixup().
This is often seen when error handling in the init function
uses functionality in the exit path.
The fix is often to remove the __init annotation of
malta_pcnet32_ioports_fixup() so it may be used outside an exit section.
This is from the addition of "mti_malta32: fix the pci resource conflicts"
(5c19c1c31c77 on v5.2/standard/mti-malta32) - which is a relatively old
commit, but w/o a malta+PCnet32, I can't speak to whether this commit is
still needed, or if the PCI resource overlap was solved another way.
Hence here, we take the safe path and just remove the __init annotation.
]
Signed-off-by: Jack Tan <jack.tan@windriver.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
CONFIG_NETDEVICES is set twice, remove one of them.
Signed-off-by: Yanfei Xu <yanfei.xu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
drop TI_DAVINCI_CPDMA option removed from v5.2 kernel
https://github.com/torvalds/linux/commit/99f629718272974405e8d180d2fa70c03c06d61f
drop SND_DAVINCI_SOC_MCASP option removed from v5.0 kernel
https://github.com/torvalds/linux/commit/f2055e145f2975a75dace8e386fad9364828cdb4
drop MMC_UNSAFE_RESUME option removed from v3.16 kernel
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/m
mc/core/Kconfig?h=v3.16.82&id=2501c9179dff2add6aadd3898cd729e94e777d3a
drop DRM_OMAP_PANEL_DPI option removed from v5.2 kernel.
https://github.com/torvalds/linux/commit/8bf4b1621178ef05bde5b9a14a117ff951dd1260
MTD_NAND option was renamed MTD_RAW_NAND in v5.2 kernel
https://github.com/torvalds/linux/commit/72c5af00272339af6bbed6fe7275cd731f57be2d
MTD_NAND_ECC was renamed MTD_NAND_ECC_SW_HAMMING in v5.2 kernel
https://github.com/torvalds/linux/commit/9bb94643b94115990ffec18c8129f1ab970765c1
drop BACKLIGHT_LCD_SUPPORT option removed from v5.2 kernel
https://github.com/torvalds/linux/commit/8c5dc8d9f19c7992b5ed557b865127a80149041b
drop TI_CPSW_ALE option removed from v5.2 kernel
https://github.com/torvalds/linux/commit/16f54164828b253d7792b67b05c07540f236ece5
drop MMC_BLOCK_BOUNCE removed from v4.13 kernel
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/m
mc/core/Kconfig?h=linux-4.13.y&id=c3dccb74be28a345a2ebcc224e41b774529b8b8f
Signed-off-by: Yanfei Xu <yanfei.xu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Because of upstream commit b35b9a10362d ("mtd: spi-nor: Move m25p80 code
in spi-nor.c"), CONFIG_MTD_M25P80 is not used anymore.
Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
1)CONFIG_ENERGY_MODEL is a default configure items of arm64
defconfig.
Reference: https://patchwork.kernel.org/patch/10944391/
2)THERMAL_GOV_POWER_ALLOCATOR is set to y in nxp-ls20xx.cfg, but
from v5.5 kernel, the THERMAL_GOV_POWER_ALLOCATOR depends on
ENERGY_MODEL. So we enable it for THERMAL_GOV_POWER_ALLOCATOR
can take effect.
Reference: https://github.com/torvalds/linux/commit/a4e893e802e6a807df2e2f3f660f7399bc7e104e
Signed-off-by: Yanfei Xu <yanfei.xu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
In latest kernel v5.6, new clock drvier clk-raspberrypi.c is created.
So, enable kernel config CONFIG_CLK_RASPBERRYPI in kernel-cache
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Item CONFIG_CRYPTO_AES_X86_64 has been dropped from v5.4 kernel,
therefore, we drop it too.
Reference: https://github.com/torvalds/linux/commit/1d2c3279311e4f03fcf164e1366f2fda9f4bfccf
Signed-off-by: Yanfei Xu <yanfei.xu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Because of upstream commit 788961462f347161 ("ARM: psci: cpuidle:
Enable PSCI CPUidle driver"), the new kernel option CONFIG_ARM_PSCI_CPUIDLE
is used to enable PSCI CPUidle driver. So enable CONFIG_ARM_PSCI_CPUIDLE
for zcu102 board.
Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
In latest kernel v5.6, the kernel config HID_LOGITECH
for raspberry pi4 platform depends on LEDS_CLASS.
So, add it in cfg file.
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
This will allow testing libinput in particular:
https://www.kernel.org/doc/html/latest/input/uinput.html
https://wayland.freedesktop.org/libinput/doc/latest/test-suite.html
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Drop the setting of the qemumips64 option, since it disables h/w
clocks in VDSO.
With the latest glibc, we are no longer segfaulting on boot during
VDSO clock access, so we can drop the use of this option (for now).
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
We no longer need to override optimization levels for armv5 on
vsprintf and asprintf. There are no more boot/build issues, and
in fact, the different optimization level is triggering build
warnings.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
1/1 [
Author: Bruce Ashfield
Email: bruce.ashfield@gmail.com
Subject: mips: Kconfig: add QEMUMIPS64 option
Date: Tue, 7 Jan 2020 03:34:12 +0000
In 5.4+ mips has switched to using the generic VDSO implementation, in
particular the following commits are the bulk of the changes:
932bb934ed4d mips: compat: vdso: Use legacy syscalls as fallback
cdab7e2c73d5 mips: vdso: Fix flip/flop vdso building bug
b4c0f7fa5308 mips: vdso: Fix source path
1f66c45db330 mips: Add clock_gettime64 entry point
abed3d826f2f mips: Add clock_getres entry point
6393e6064486 mips: fix vdso32 build, again
24640f233b46 mips: Add support for generic vDSO
8919975b6171 MIPS: VDSO: Fix build for binutils < 2.25
90800281e761 MIPS: VDSO: Remove unused gettimeofday.c
There is a (currently) unknown interaction between qemumips64, the
mti_malta64 platform, glibc and VDSO that causes a segfault when
gettimeofday is called during boot. It appears that the VDSO
configuration of the gic address is incorrect, and hence when
read_gic_count() is called during do_hres() initialization, the
page is not properly mapped and a segfault is triggered.
If we avoid reading the gic, and let the vdso syscall fallbacks
be enabled, we are find for boot. The most flexible way to avoid
these reads is to make the two malta clocksources not be selected
when we are booting under qemumips64. This allows other platforms
to not be impacted.
Once a root cause of this bad mapping is found, we can drop the
new CONFIG_QEMUMIPS64 option and behaviour will revert to using
the git automatically.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Two types spi-nor flash support on TI's AM654 EVM:
ospi-nor: mt35xu512aba Octal flash with 512-Mbit
spi-nor : mt25ql128aba SPI NOR Flash with 128-Mbit
Signed-off-by: Jun Miao <jun.miao@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Yongxin Liu <yongxin.liu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Since the upstream commit 6334150e9a36 ("remoteproc: don't allow modular build")
has forbidden CONFIG_REMOTEPROC from being "m", so we change it to be "y". Or else
there will be warning as below:
---------- CONFIG_REMOTEPROC -----------------
Config: CONFIG_REMOTEPROC
From: tmp-glibc/work-shared/xilinx-zynqmp/kernel-source/.kernel-meta/configs/standard/xilinx-zynqmp/bsp/xilinx-zynqmp/xilinx-zynqmp.cfg
Requested value: CONFIG_REMOTEPROC=m
Actual value: # CONFIG_REMOTEPROC is not set
Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Yongxin Liu <yongxin.liu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
This driver for Broadcom V3D 3.3 and 4.1 OpenGL ES GPUs.
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
This add cfg&scc files to support xilinx zc702 and zc706 boards.
Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
canfd driver depend on clock wizard, so enable it.
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
CONFIG_OCTEONTX2_PF depends on ARM64_LSE_ATOMICS, but commit:
b32baf91f60f ("arm64: lse: Make ARM64_LSE_ATOMICS depend on JUMP_LABEL")
makes ARM64_LSE_ATOMICS depends on JUMP_LABEL.
Signed-off-by: Xiaotao Yin <xiaotao.yin@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Add scc/cfg kernel fragment to build and boot AM65X GP EVM board with am6548 soc.
Signed-off-by: Jun Miao <jun.miao@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
arm-versatile-926ejs systems hang at random places when
CONFIG_CC_OPTIMIZE_FOR_SIZE is enabled.
standard.scc -> arm.scc -> arm.cfg -> CONFIG_CC_OPTIMIZE_FOR_SIZE=y
Use CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE instead before we find the root cause.
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
This is needed by some ODP applications and enable it as requested
by some customers.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Don't need to set CONFIG_VIRTIO to be "y" explicitly, or else
when bitbake core-image-base there will be building warning as below:
WARNING: linux-yocto-5.2.x+gitAUTOINC+343a633207_b039f25b0a-r0 do_kernel_configcheck: [kernel config]: specified values did not make it into the kernel's final configuration:
---------- CONFIG_VIRTIO -----------------
Config: CONFIG_VIRTIO
Requested value: CONFIG_VIRTIO=y
Actual value: CONFIG_VIRTIO=m
Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
There is no LVDS panel supported on renesas-rcar platform,
So, delete CONFIG_DRM_PANEL_LVDS from kernel configure file.
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
These kernel configures don't exist in wrlinux1019 kernel.
So, delete them to avoid building warning
Signed-off-by: Meng Li <Meng.Li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Ti-am335x bsp includes the standard.scc file, which will set CONFIG_CC_OPTIMIZE_FOR_SIZE=y.
As a result, the system boot hangs like below in v5.4.0-rc4 kernel version:
When we enable CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE for -O2 Optimization level,
the boot succeeds.
boot log:
systemd[1]: Set hostname to <ti-am335x>.
systemd[1]: Failed to open netlink: Operation not permitted
systemd-fstab-generator[120]: Failed to write unit file -.mount: Bad address
systemd-fstab-generator[120]: Failed to write unit file var-volatile.mount: Bad address
... ...
systemd[1]: Failed to start device monitor: Bad address
systemd[1]: SO_PASSCRED failed: Bad address
[!!!!!!] Failed to start up manager.
systemd[1]: Freezing execution.
Signed-off-by: Jun Miao <jun.miao@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Add profiling related options for convenience for perf and etc.
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
These kernel options have been removed frome kernel, so
delete them from xilinx-zynqmp.cfg.
Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|