Go to file
Krzysztof Kopyściński 00bfac00ae Bluetooth: gatt: Add option to read multiple without variable length
Currently, with EATT enabled, when bt_gatt_read is called with multiple
handles first it'll try to use gatt_read_mult_vl, and if it fails
gatt_read_mult will be used to try again. Add option to skip
the gatt_read_mult_vl and use gatt_read_mult right away. This is needed
by tests that expect BT_ATT_OP_READ_MULT_REQ but support variable
lenght, thus don't return BT_ATT_ERR_NOT_SUPPORTED.

Removed fallback from read multiple vl to read multiple on
BT_ATT_ERR_NOT_SUPPORTED error.

This was affecting:
GATT/CL/GAR/BV-05-C, GATT/CL/GAR/BI-18-C, GATT/CL/GAR/BI-19-C,
GATT/CL/GAR/BI-20-C, GATT/CL/GAR/BI-21-C, GATT/CL/GAR/BI-22-C

Signed-off-by: Krzysztof Kopyściński <krzysztof.kopyscinski@codecoup.pl>
2021-08-12 11:07:08 -04:00
.buildkite ci: Bump to use SDK 0.13.0 2021-08-03 22:57:41 -04:00
.github doc-build.yml: build west 0.11.1a1 2021-08-09 13:29:57 -04:00
arch ARC: MWDT: fix SMP build for MWDT toolchain 2021-08-10 07:36:25 -04:00
boards Microchip: MEC172x: ADC driver 2021-08-11 19:44:31 -04:00
cmake cmake: dts: removing generated <board>.dts_compiled 2021-08-11 11:16:18 -04:00
doc Bluetooth: gatt: Add option to read multiple without variable length 2021-08-12 11:07:08 -04:00
drivers display: introduce CONFIG_DISPLAY_INIT_PRIORITY 2021-08-12 17:00:39 +02:00
dts dts: arm: st: rename g0 tim1 interrupt to align with f0 series 2021-08-12 07:06:14 -05:00
include Bluetooth: gatt: Add option to read multiple without variable length 2021-08-12 11:07:08 -04:00
kernel pm: device: Add wakeup source API 2021-08-11 19:39:13 -04:00
lib lib: newlib: Add retargetable locking implementation 2021-08-09 08:51:24 -05:00
misc
modules modules: hal_nxp: tweak integration to utilize cmake-ext/kconfig-ext 2021-08-11 12:26:28 -05:00
samples doc: guides: Add a TF-M guide 2021-08-12 10:03:57 -05:00
scripts cmake: add a comment header to zephyr_settings.txt 2021-08-10 07:37:19 -04:00
share cmake: check zephyr version if specified and ZEPHYR_BASE is set 2021-05-25 16:48:35 -05:00
soc drivers: can: Fix isotp test failed on rt1170 EVK 2021-08-12 09:00:30 -05:00
subsys Bluetooth: gatt: Add option to read multiple without variable length 2021-08-12 11:07:08 -04:00
tests Bluetooth: gatt: Add option to read multiple without variable length 2021-08-12 11:07:08 -04:00
.checkpatch.conf checkpatch: ignore linux specific ENOSYS warning 2021-03-30 10:50:14 -05:00
.clang-format clang-format: Change lines length limit from 80 to 100 2021-05-06 08:13:32 -05:00
.codecov.yml
.editorconfig
.gitattributes
.gitignore gitignore: add common Python venv directories 2021-04-20 11:30:40 -05:00
.gitlint
.mailmap mailmap: update mailmap file with some stray emails 2021-06-17 14:15:41 -04:00
.uncrustify.cfg
CMakeLists.txt kernel: fix kobj table if having .sdata section. 2021-07-22 07:29:21 -05:00
CODE_OF_CONDUCT.md
CODEOWNERS esp32s2: drivers: serial: add minimal uart driver 2021-08-09 13:03:14 -04:00
CONTRIBUTING.rst
Kconfig
Kconfig.zephyr soc: esp32s2: add initial soc support files for esp32s2 2021-07-28 21:09:27 -04:00
LICENSE
MAINTAINERS.yml MAINTAINERS: Add 'Nuvoton_Numicro Platform' for Nuvoton Numicro family. 2021-08-07 20:37:24 -04:00
README.rst readme: add missing logo 2021-07-21 10:37:37 -05:00
VERSION version: add EXTRAVERSION to VERSION file 2021-06-05 07:07:01 -04:00
version.h.in
west.yml modules: hal_nxp: tweak integration to utilize cmake-ext/kconfig-ext 2021-08-11 12:26:28 -05:00
zephyr-env.cmd
zephyr-env.sh

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <img src="doc/_static/images/logo-readme.png">
     </p>
   </a>

   <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
   src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
   <a href="https://buildkite.com/zephyr/zephyr">
   <img
   src="https://badge.buildkite.com/f5bd0dc88306cee17c9b38e78d11bb74a6291e3f40e7d13f31.svg?branch=main"></a>


The Zephyr Project is a scalable real-time operating system (RTOS) supporting
multiple hardware architectures, optimized for resource constrained devices,
and built with security in mind.

The Zephyr OS is based on a small-footprint kernel designed for use on
resource-constrained systems: from simple embedded environmental sensors and
LED wearables to sophisticated smart watches and IoT wireless gateways.

The Zephyr kernel supports multiple architectures, including ARM Cortex-M,
Intel x86, ARC, Nios II, Tensilica Xtensa, and RISC-V, and a large number of
`supported boards`_.

.. below included in doc/introduction/introduction.rst


Getting Started
***************

Welcome to Zephyr! See the `Introduction to Zephyr`_ for a high-level overview,
and the documentation's `Getting Started Guide`_ to start developing.

.. start_include_here

Community Support
*****************

Community support is provided via mailing lists and Slack; see the Resources
below for details.

.. _project-resources:

Resources
*********

Here's a quick summary of resources to help you find your way around:

* **Help**: `Asking for Help Tips`_
* **Documentation**: http://docs.zephyrproject.org (`Getting Started Guide`_)
* **Source Code**: https://github.com/zephyrproject-rtos/zephyr is the main
  repository; https://elixir.bootlin.com/zephyr/latest/source contains a
  searchable index
* **Releases**: https://github.com/zephyrproject-rtos/zephyr/releases
* **Samples and example code**: see `Sample and Demo Code Examples`_
* **Mailing Lists**: users@lists.zephyrproject.org and
  devel@lists.zephyrproject.org are the main user and developer mailing lists,
  respectively. You can join the developer's list and search its archives at
  `Zephyr Development mailing list`_. The other `Zephyr mailing list
  subgroups`_ have their own archives and sign-up pages.
* **Nightly CI Build Status**: https://lists.zephyrproject.org/g/builds
  The builds@lists.zephyrproject.org mailing list archives the CI
  (buildkite) nightly build results.
* **Chat**: Zephyr's Slack workspace is https://zephyrproject.slack.com.  Use
  this `Slack Invite`_ to register.
* **Contributing**: see the `Contribution Guide`_
* **Wiki**: `Zephyr GitHub wiki`_
* **Issues**: https://github.com/zephyrproject-rtos/zephyr/issues
* **Security Issues**: Email vulnerabilities@zephyrproject.org to report
  security issues; also see our `Security`_ documentation. Security issues are
  tracked separately at https://zephyrprojectsec.atlassian.net.
* **Zephyr Project Website**: https://zephyrproject.org

.. _Slack Invite: https://tinyurl.com/2vue8666
.. _supported boards: http://docs.zephyrproject.org/latest/boards/index.html
.. _Zephyr Documentation: http://docs.zephyrproject.org
.. _Introduction to Zephyr: http://docs.zephyrproject.org/latest/introduction/index.html
.. _Getting Started Guide: http://docs.zephyrproject.org/latest/getting_started/index.html
.. _Contribution Guide: http://docs.zephyrproject.org/latest/contribute/index.html
.. _Zephyr GitHub wiki: https://github.com/zephyrproject-rtos/zephyr/wiki
.. _Zephyr Development mailing list: https://lists.zephyrproject.org/g/devel
.. _Zephyr mailing list subgroups: https://lists.zephyrproject.org/g/main/subgroups
.. _Sample and Demo Code Examples: http://docs.zephyrproject.org/latest/samples/index.html
.. _Security: http://docs.zephyrproject.org/latest/security/index.html
.. _Asking for Help Tips: https://docs.zephyrproject.org/latest/getting_started/index.html#asking-for-help