Age | Commit message (Collapse) | Author | Files | Lines |
|
Bug-AGL: SPEC-1945
Latest meta-rcar update SDIO frequency for TI's WLAN driver.
However, in M3 case, the this patch raise ti/wlcore driver WANING.
[ 107.009706] ------------[ cut here ]------------
[ 107.014342] WARNING: CPU: 0 PID: 4224 at /kernel-source//drivers/net/wireless/ti/wlcore/sdio.c:145 wl12xx_sdio_raw_write+0xb0/0x160 [wlcore_sdio]
[ 107.027375] Modules linked in: rfcomm 8021q garp stp mrp llc can_bcm can bnep nfc arc4 wl18xx wlcore mac80211 cfg80211 crc32_ce crct10dif_ce btwilink bluetooth ecdh_generic wlcore_sdio rcar_can st_drv rfkill can_dev vspm_if(O) vsp2(O) vspm(O) uvcs_drv(O) sllin(O) pvrsrvkm(O) mmngrbuf(O) mmngr(O) hdm_usb(O) hdm_i2c(O) hdm_dim2(O) aim_v4l2(O) aim_sound(O) aim_network(O) aim_cdev(O) mostcore(O) ipv6
[ 107.062537] CPU: 0 PID: 4224 Comm: wpa_supplicant Tainted: G O 4.14.35-yocto-standard #1
[ 107.071749] Hardware name: Renesas M3ULCB Kingfisher board based on r8a7796 (DT)
[ 107.079138] task: ffff8005fc610e00 task.stack: ffff000020bc8000
[ 107.085054] PC is at wl12xx_sdio_raw_write+0xb0/0x160 [wlcore_sdio]
[ 107.091316] LR is at wl12xx_sdio_raw_write+0x7c/0x160 [wlcore_sdio]
<snip>
[ 107.467808] ---[ end trace 0140d637a5afd50b ]---
[ 107.472613] wl1271_sdio mmc2:0001:2: sdio write failed (-84)
[ 107.478340] ------------[ cut here ]------------
[ 107.483008] WARNING: CPU: 0 PID: 4224 at /kernel-source//drivers/net/wireless/ti/wlcore/main.c:796 wl12xx_queue_recovery_work.part.26+0x58/0x60 [wlcore]
[ 107.496648] Modules linked in: rfcomm 8021q garp stp mrp llc can_bcm can bnep nfc arc4 wl18xx wlcore mac80211 cfg80211 crc32_ce crct10dif_ce btwilink bluetooth ecdh_generic wlcore_sdio rcar_can st_drv rfkill can_dev vspm_if(O) vsp2(O) vspm(O) uvcs_drv(O) sllin(O) pvrsrvkm(O) mmngrbuf(O) mmngr(O) hdm_usb(O) hdm_i2c(O) hdm_dim2(O) aim_v4l2(O) aim_sound(O) aim_network(O) aim_cdev(O) mostcore(O) ipv6
[ 107.531806] CPU: 0 PID: 4224 Comm: wpa_supplicant Tainted: G W O 4.14.35-yocto-standard #1
[ 107.541018] Hardware name: Renesas M3ULCB Kingfisher board based on r8a7796 (DT)
[ 107.548406] task: ffff8005fc610e00 task.stack: ffff000020bc8000
[ 107.554363] PC is at wl12xx_queue_recovery_work.part.26+0x58/0x60 [wlcore]
[ 107.561265] LR is at wl12xx_queue_recovery_work+0x1c/0x28 [wlcore]
Change-Id: I6f15251e6997f52892efd118e8941af5930c5ca9
Signed-off-by: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>
(cherry picked from commit b142e42f4fd851a4f8a016cbffb0473f3b88419e)
|
|
virtual/gpsd-conf is a runtime dependency in packagegroup-agl-core-navigation.
So, PREFERRED_RPROVIDER must be used in place of PREFERRED_PROVIDER
Bug-AGL: SPEC-1861
Change-Id: I15b915c2e7a1410000f7527b13f3206242778bc0
Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
|
|
* For the Renesas Gen3 extention board Kingfisher,
we must specify the GPS device for gpsd service.
* Create a new machine type kingfisher.
Bug-AGL: SPEC-1538
Change-Id: If6b7e49f6a006218e57c58e15855e0d65eb849cd
Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh>
|
|
- The PACKAGECONFIG value "experimental" was remove recently
(Upgrade Bluez version 5.43 -> 5.44).
(From poky): feacb428b055fd714eb1b15402023f4a726dce54
-PACKAGECONFIG[experimental] = "--enable-experimental,--disable-experimental,"
- So we can remove "experimental" feature to avoid yocto Warning.
Bug-AGL: SPEC-1398
Change-Id: Ibd96a788bd0c4e0d9bc6959012bbbf839d890e9d
Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh>
|
|
* valgrind was backport in meta-rcar from cogent (unidentified reason).
In some builds environement, the build of this recipes failed
(issue hardly reproductible). So remove valgrind backported recipes
should resolve the build issue and upstream recipes from yocto will be
used.
Bug-AGL: SPEC-1374
Change-Id: I1bc3d065badd1e2cd35b2a7b1a3c5fb43c357c06
Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh>
|
|
Change-Id: I115096811662403f34846f434fbc7772024c1634
Signed-off-by: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>
|
|
This commit is removed from meta-renesas-rcar-gen3
====
commit a5dfadaa3931977a221e0508354e9ab97482b9ab
Author: Scott Murray <scott.murray@konsulko.com>
Date: Thu Dec 21 20:46:30 2017 -0500
====
Some changes to allow integration with the AGL radio binding and
improve FM configuration with some tweaks and additional configuration
options.
Changes include:
- Add command-line option for selecting FM band plan. The default
band plan is US / Canada.
- Add command-line options for setting FM scanning valid SNR and RSSI
thresholds to allow tweaking sensitivity in poor radio environments.
- Increased seeking scan timeout to 3 seconds, which seems to improve
behavior in poor radio environments where powerful stations may be
far apart.
- Removed explicit setting of FM_SOFTMUTE_SNR_LIMITS, as it seemed
like it might be resulting in odd muting behavior when scanning.
- Changed initial FM frequency if not specified to the minimum of the
band plan.
Change-Id: I5d8c95947489b83384babb50285b76d3de45214a
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Signed-off-by: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>
|
|
Kingfisher has MedlaLB Interface for most, kernel tree has
most driver as build-in driver. So these configs is enabled.
Howemver AGL use most driver in gerrit repository. So AGL
should be disable it.
Change-Id: Ia46500d58fc16f348a098c58f5e807cf37913e5e
Signed-off-by: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>
|
|
We need to provide a systemd unit for UIM to be started at boot. We
also do not want the blacklist that Cogent has created, so delete that.
Bug-AGL: SPEC-1175
Change-Id: Ia35a6007722d4e42a7a76fe9d8d26b90b073f73b
Signed-off-by: Matt Porter <mporter@konsulko.com>
Signed-off-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>
|
|
Change-Id: Id1b6b88e606d0a102eefbdb9c8deae2dfe0cf73b
Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh>
Signed-off-by: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>
|
|
Change-Id: I75b9ced887249380a6164296b73acaaca91e3060
Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh>
|