docs: remove deprecated I2C references
As from this PR, Zephyr has no I2C_X references
and this notes presented in the documentation
can be removed.
Signed-off-by: Sylvio Alves <sylvio.alves@espressif.com>
diff --git a/doc/guides/build/kconfig/tips.rst b/doc/guides/build/kconfig/tips.rst
index 3df4bfe..8f6f0c0 100644
--- a/doc/guides/build/kconfig/tips.rst
+++ b/doc/guides/build/kconfig/tips.rst
@@ -56,14 +56,6 @@
In particular, avoid adding new Kconfig options of the following types:
-Options enabling individual devices
-===================================
-
-Existing examples like :kconfig:`CONFIG_I2C_0` and :kconfig:`CONFIG_I2C_1` were
-introduced before Zephyr supported devicetree, and new cases are discouraged.
-See :ref:`dt-create-devices` for details on how to do this with devicetree
-instead.
-
Options that specify a device in the system by name
===================================================
diff --git a/doc/guides/dts/howtos.rst b/doc/guides/dts/howtos.rst
index c0edaaa..acd161a 100644
--- a/doc/guides/dts/howtos.rst
+++ b/doc/guides/dts/howtos.rst
@@ -353,17 +353,6 @@
particular :ref:`compatible <dt-important-props>` (or related set of
compatibles) supported by the driver.
-.. note::
-
- Historically, Zephyr has used Kconfig options like :kconfig:`CONFIG_I2C_0` and
- :kconfig:`CONFIG_I2C_1` to enable driver support for individual devices of
- some type. For example, if ``CONFIG_I2C_1=y``, the SoC's I2C peripheral
- driver would create a ``struct device`` for "I2C bus controller number 1".
-
- This style predates support for devicetree in Zephyr and its use is now
- discouraged. Existing device drivers may be made "devicetree-aware"
- in future releases.
-
Writing a devicetree-aware driver begins by defining a :ref:`devicetree binding
<dt-bindings>` for the devices supported by the driver. Use existing bindings
from similar drivers as a starting point. A skeletal binding to get started
