- 16 Nov, 2016 19 commits
-
-
Vinayak Chettimada authored
Change-id: I7b691d082d080239c35b63221e3c6c7aa93ed58e Signed-off-by:
Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
-
Vinayak Chettimada authored
External interrupts are indexed from value 16, wherein 0 to 15 are ARM cortex M exceptions. Fixed code in _irq_is_priority_equal to fetch correct external interrupt line ISR priority. Change-id: I9cfd411480e78dfc9635e72d14df9d667a9d8400 Signed-off-by:
Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
-
Ramesh Thomas authored
testcase.ini was not building for ARC. This app would run on x86 and arc. Change-Id: I961d56079aa1db7d84e0fcc87780ba11d7f4d831 Signed-off-by:
Ramesh Thomas <ramesh.thomas@intel.com>
-
Ramesh Thomas authored
Remove redundant platform filtering and only use SOC filtering Change-Id: Ib823e076a874ce61a235eca63eebb7f19d2fdd30 Signed-off-by:
Ramesh Thomas <ramesh.thomas@intel.com>
-
Baohong Liu authored
The variable type mismatching was caught by LLVM. Jira: ZEP-1179 Change-Id: I084406601badc64c257cbdd82b9c8b7509549303 Signed-off-by:
Baohong Liu <baohong.liu@intel.com>
-
Baohong Liu authored
The variable type mismatching was caught by LLVM. Jira: ZEP-1179 Change-Id: I1193a946ea5814510e6c07668c5d05a5d91445a8 Signed-off-by:
Baohong Liu <baohong.liu@intel.com>
-
Baohong Liu authored
The variable type mismatching was caught by LLVM. Jira: ZEP-1179 Change-Id: I402c348af142342e37e93619c4da6e3a5bfd82da Signed-off-by:
Baohong Liu <baohong.liu@intel.com>
-
Sergey Kiselev authored
Change-Id: I32e72c2845bd06b10585ac8048f67ac754c2a6d6 Signed-off-by:
Sergey Kiselev <sergey.kiselev@intel.com> Signed-off-by:
Anas Nashif <anas.nashif@intel.com>
-
Vincenzo Frascino authored
This patch fixes unchecked return value conditions in the bme280 driver. This issue was reported by Coverity (CID 151961, 151959, 151955). Change-Id: I3a2dfbabd41ae52b00fa512a40e00c2e36c3b5ca Signed-off-by:
Vincenzo Frascino <vincenzo.frascino@linaro.org>
-
Vincenzo Frascino authored
This patch fixes a less-than-zero comparison of an unsigned value condition present in bmi160 driver. This issue was reported by Coverity (CID 152002, 152003). Change-Id: I703066519652ac1ecdd9ddf7e97ec7dcbe2a9e27 Signed-off-by:
Vincenzo Frascino <vincenzo.frascino@linaro.org>
-
Ramesh Thomas authored
This sample was created intially when there were no other samples in place to enable the CONFIG flags to build code inside those flags. However, those CONFIG flags are now guarded with corresponding "SUPPORTED" flags which are enabled based in Kconfigs of socs based on their support for that power feature. This app is for x86 and those features will not get enabled for this configuration. If it is still required, then we would need to fake such support in Kconfig.board of qemu_x86. Removing it, because those flags will get enabled by sample and test apps of socs that support the power features, causing code inside them to get built. Change-Id: I647be9289a49d69880811abee499a4efd61bbc6a Signed-off-by:
Ramesh Thomas <ramesh.thomas@intel.com>
-
Ramesh Thomas authored
Cleaned up and removed some unnecessary code to avoid distraction from main sample implementation. Updated some logic based on new PM interface in soc area. Updated README to indicate it supports x86 and ARC and updated sample output of both architectures. Change-Id: I1c9c8348dae403b7ca6fe17ab867e3fbef06ae60 Signed-off-by:
Ramesh Thomas <ramesh.thomas@intel.com>
-
Baohong Liu authored
The variable type mismatching was caught by LLVM. Jira: ZEP-1179 Change-Id: I37934ef2ee47c521a78086564876843794688d55 Signed-off-by:
Baohong Liu <baohong.liu@intel.com>
-
Benjamin Walsh authored
This reverts commit "kernel/arm: add comment about _is_next_thread_current" and fixes the interrupt locking issue. The comment would have been right if only reads were done the ready queue, but that is not the case. It turns out that the comment was written ignoring the fact that _is_next_thread_current() updates the next thread cache when fetching the next thread. Change-Id: I21c9230f85f4f87a6bbf14fd4a9eb7e19b59f8c5 Signed-off-by:
Benjamin Walsh <benjamin.walsh@windriver.com>
-
Szymon Janc authored
This fix using incorrect address type for passive scanning with privacy enabled. Controller was not reporting directed advertising to RPA address due to public type being used for passive scan. This was affecting TC_CONN_GCEP_BV_01_C, TC_CONN_ACEP_BV_01_C and TC_CONN_DCEP_BV_01_C qualification test cases. Jira: ZEP-1200 Change-Id: Icc316441fcac1a72d75f9ade27a99030efc846b9 Signed-off-by:
Szymon Janc <ext.szymon.janc@tieto.com>
-
Mariusz Skmara authored
This fixes issue that L2CAP Connection Parameters Update Request was not sent. There was check that used LE features of host controller to determine if L2CAP procedure or LL shall be used. It was failing with 4.2 controller. The check shall test if remote supports LL Connection Parameters Request Procedure. If it's not supported, then L2CAP Connection Parameters Update Procedure will be used. Closes ZEP-1220 1/4 L2CAP TC_LE_CPU_BV_01_C PASS 2/4 GAP TC_CONN_CPUP_BV_01_C PASS 3/4 GAP TC_CONN_CPUP_BV_02_C PASS 4/4 GAP TC_CONN_CPUP_BV_03_C PASS Change-Id: I61ad544d9568ca6306a845e05c1a2e28d1693ab4 Signed-off-by:
Mariusz Skamra <mariusz.skamra@tieto.com>
-
Vinayak Chettimada authored
Coverity analysis discovered NULL pointer being dereferenced when passing a auto variable. The variable is now correctly assigned with address of a valid default value variable. As per design, the dereferencing will not happen as the master role does not use the passed parameter only slave role uses it to prepare the connection parameter request PDU. Change-id: I3f8519b23a83cb8c50c7fba81810eff7737ff74a Signed-off-by:
Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
-
Vinayak Chettimada authored
Coverity analysis discovered that observer filter policy field was 1 bit, whereas valid range for extended scanner filter policy feature implemented in controller is 0 to 3. Increase the bit field size from 1 to 2. Change-Id: Id4b2e354961dfb3b45f72fa4e0ab18de7425bbb5 Signed-off-by:
Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
-
Vinayak Chettimada authored
Added implementation for HCI Reset Command. Implementation gracefully disables any running advertiser, observer, and/ or connection roles, and it resets controller context members. The HCI Reset Command is implemented in such a way that driver instances shared with other sub-systems and application is not disturbed and instance/references used by Bluetooth Controller are gracefully returned back. Jira: ZEP-1282 Change-id: Ifb9ae6807736b5ec2d9f346cf2a590322056bcee Signed-off-by:
Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by:
Carles Cufi <carles.cufi@nordicsemi.no>
-
- 15 Nov, 2016 7 commits
-
-
Szymon Janc authored
BR/EDR code should have minimal impact on LE code so to keep it simple just require peripheral and central to be enabled when selecting BR/EDR support. Fix following Kconfig warning: warning: (NETWORKING_WITH_BT && BLUETOOTH_BREDR) selects BLUETOOTH_L2CAP_DYNAMIC_CHANNEL which has unmet direct dependencies (BLUETOOTH && BLUETOOTH_HCI && BLUETOOTH_HCI_HOST && BLUETOOTH_CONN && BLUETOOTH_SMP) Change-Id: I7f7cb8794def0df6daaa4abfe4596df460f1a2b2 Signed-off-by:
Szymon Janc <ext.szymon.janc@tieto.com>
-
Gil Pitney authored
Though Cortex-M4 could optionally have a floating point unit, the MCU in the cc3200 in fact does not have an FPU. Enabling CPU_HAS_FPU caused applications built with CONFIG_FLOAT=y to crash during an early call to enable_floating_point(). This patch was validated by running microPython, which is one such application. Change-Id: I8bfd42c456524e152cbbb983001d9540d93fbe98 Signed-off-by:
Gil Pitney <gil.pitney@linaro.org>
-
Benjamin Walsh authored
Change-Id: I3d533b819422d4b754afb81d3ea67c03bc7f5630 Signed-off-by:
Benjamin Walsh <benjamin.walsh@windriver.com> (cherry picked from commit 59a382e3)
-
Benjamin Walsh authored
Normally, _is_next_thread_current() must be called with interrupts locked, but the ARM interrupt exit code does not have to do that. Add explanation why. Change-Id: Id383b47a055fdd6fbd5afffa52772e92febde98f Signed-off-by:
Benjamin Walsh <benjamin.walsh@windriver.com> (cherry picked from commit dfa7ca4e)
-
Benjamin Walsh authored
Change-Id: I1919fd7b0ae3cb3ac434acc2dceddf3afb4a975b Signed-off-by:
Benjamin Walsh <benjamin.walsh@windriver.com> (cherry picked from commit ba26678f)
-
Inaky Perez-Gonzalez authored
This TC is only exercising the API, as we don't have a feedback loop mechanism to verify whichever values are fed to the ADC. Fixed the loop to complete after 10 runs; on each run, print the values and actually report the difference between them. With no inputs connected (aka: floating), they should be reporting noise relatively close to the previous reading, so we might want to use this delta as a testing pattern (assert if the delta is higher than some value, but I've seen variations as high as 40M units). For now, the test is just happy with being able to read them. The buffer has been re-typed to uint32_t so we can iterate over it without casting tricks -- it requires then only a single cast when initializing sample.buffer (which shall be a void* anyway). Duplicated the buffer, so we can flip/flop between two buffers to compare against the entries read in the previous run. v4: fixed missed warnings Change-Id: If6b48b92231007202d74f5c042f6d0cf3fdcb60a Signed-off-by:
Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com> (cherry picked from commit 9e1df6f2)
-
Szymon Janc authored
Fix following warning: CC subsys/bluetooth/host/monitor.o In file included from zephyr/include/drivers/loapic.h:58:0, from zephyr/include/drivers/ioapic.h:22, from zephyr/include/drivers/sysapic.h:20, from zephyr/include/arch/x86/irq_controller.h:33, from zephyr/include/arch/x86/arch.h:28, from zephyr/include/arch/cpu.h:23, from zephyr/include/kernel.h:2458, from zephyr/include/zephyr.h:20, from zephyr/subsys/bluetooth/host/monitor.c:24: zephyr/subsys/bluetooth/host/monitor.c: In function '_deprecation_check_sys_init_bt_monitor_init0': zephyr/include/device.h:130:16: warning: '_INIT_LEVEL_PRIMARY' is deprecated [-Wdeprecated-declarations] static struct device_config _CONCAT(__config_, dev_name) __used \ ^ zephyr/include/device.h:245:2: note: in expansion of macro 'DEVICE_AND_API_INIT' DEVICE_AND_API_INIT(dev_name, drv_name, init_fn, data, cfg_info, \ ^ zephyr/include/init.h:69:2: note: in expansion of macro 'DEVICE_INIT' DEVICE_INIT(_SYS_NAME(init_fn), "", init_fn, NULL, NULL, level, prio) ^ zephyr/subsys/bluetooth/host/monitor.c:193:1: note: in expansion of macro 'SYS_INIT' SYS_INIT(bt_monitor_init, PRIMARY, MONITOR_INIT_PRIORITY); ^ zephyr/include/device.h:48:31: note: declared here static __deprecated const int _INIT_LEVEL_PRIMARY = 1; Change-Id: I0960bfddddfd1105daf3bb8cc1114e9a25840f2c Signed-off-by:
Szymon Janc <ext.szymon.janc@tieto.com>
-
- 14 Nov, 2016 1 commit
-
-
Johan Hedberg authored
The Bluetooth documentation is found in doc/subsystems/bluetooth and not in doc/bluetooth. Change-Id: I7e7010b5ae4a26ea552d75f1a095baec18d02630 Signed-off-by:
Johan Hedberg <johan.hedberg@intel.com>
-
- 13 Nov, 2016 9 commits
-
-
Anas Nashif authored
First release candidate of 1.6. Change-Id: I01e8524c163f7e984405e2feecc0118db1605ab8 Signed-off-by:
Anas Nashif <anas.nashif@intel.com>
-
Anas Nashif authored
Update file to catch any regressions and major changes during stabilisation period. Change-Id: Id30dd1827034b96c5478c78f9c388384f51bcbec Signed-off-by:
Anas Nashif <anas.nashif@intel.com>
-
Anas Nashif authored
Change-Id: Ibe73b4fe25822731ad6c671cdefe0d8d5923a3e0 Signed-off-by:
Anas Nashif <anas.nashif@intel.com>
-
Anas Nashif authored
Change-Id: Ibeadd2e8d9efa2380f21a091ab5645c4b69a4841 Signed-off-by:
Anas Nashif <anas.nashif@intel.com>
-
Anas Nashif authored
Move away from legacy APIs and use unified kenrel instead. Change-Id: Icae86beec66df1b041405cbe3455913630fc8ad1 Signed-off-by:
Anas Nashif <anas.nashif@intel.com>
-
Anas Nashif authored
Change-Id: I2d2a1689d66ed4a9ab1ce1ed5bb70c8b65f7df31 Signed-off-by:
Anas Nashif <anas.nashif@intel.com>
-
Anas Nashif authored
Use unified kernel APIs and align syntax after function name changes. Change-Id: I028f4faeaf33e28197d5f705063459188272027d Signed-off-by:
Anas Nashif <anas.nashif@intel.com>
-
Johan Hedberg authored
These should help to make it easier to understand code passing specific durations to the kernel APIs. Change-Id: I8682fafc291e8af56fd0289d0cab8c736b88da59 Signed-off-by:
Johan Hedberg <johan.hedberg@intel.com>
-
Anas Nashif authored
prio is member of base, not k_thread struct. Change-Id: I77de52497e196eb058bf8850e25eabe42cb2ab14 Signed-off-by:
Anas Nashif <anas.nashif@intel.com>
-
- 12 Nov, 2016 4 commits
-
-
Benjamin Walsh authored
SYS_DLIST_FOR_EACH_NODE() is marked as non-safe when an item is removed from the list while looping over it. This is not true per-se, since the item, when removed, keeps its next and prev pointers intact; however, it is true if the item is then put into a list, be it a different one or the same one. To prevent this, SYS_DLIST_FOR_EACH_NODE_SAFE() must be used. _mbox_message_put() can remove items from the rx queue and then put them in the ready queue: this would cause the loop to start processing other ready threads as item in the rx queue. k_mbox_get() also removes items, from the tx queue, but does not seem to add them to another list; however, it now uses the safe version as well, since that is the proper usage. Change-Id: Ieccbff238fc8a036c0d53d873eaaf55f4f5a14af Signed-off-by:
Benjamin Walsh <benjamin.walsh@windriver.com> Signed-off-by:
Anas Nashif <anas.nashif@intel.com>
-
Johan Hedberg authored
Switch left-over usage of TICKS_NONE and TICKS_UNLIMITED to the new unified kernel counterparts K_NO_WAIT and K_FOREVER. Change-Id: I2f2a16360e816f9f8791eb216deb3c70b8cc87df Signed-off-by:
Johan Hedberg <johan.hedberg@intel.com>
-
Johan Hedberg authored
The NBLE driver is now deprecated and will be removed in a future Zephyr version. Change-Id: I50753f8cf8566ac1e4e73df480c96253c199e6a7 Signed-off-by:
Johan Hedberg <johan.hedberg@intel.com>
-
Benjamin Walsh authored
There was a lot of duplication between architectures for the definition of threads and the "nanokernel" guts. These have been consolidated. Now, a common file kernel/unified/include/kernel_structs.h holds the common definitions. Architectures provide two files to complement it: kernel_arch_data.h and kernel_arch_func.h. The first one contains at least the struct _thread_arch and struct _kernel_arch data structures, as well as the struct _callee_saved and struct _caller_saved register layouts. The second file contains anything that needs what is provided by the common stuff in kernel_structs.h. Those two files are only meant to be included in kernel_structs.h in very specific locations. The thread data structure has been separated into three major parts: common struct _thread_base and struct k_thread, and arch-specific struct _thread_arch. The first and third ones are included in the second. The struct s_NANO data structure has been split into two: com...
-