docs: Bus emulators: Limit content to only bus emulation

Limit the content of this page to only cover the bus
emulators and their peripherals.
Until now, there was some out of place references to
emulators of a completely different type which did
not match the descriptions in this page.

Signed-off-by: Alberto Escolar Piedras <[email protected]>

Author: aescolar

doc/hardware/emulator/bus_emulators.rst

@@ -6,10 +6,10 @@ External Bus and Bus Connected Peripherals Emulators
 Overview
 ========
 
-Zephyr supports a simple emulator framework to support testing of drivers
+Zephyr supports a simple emulator framework to support testing of external peripheral drivers
 without requiring real hardware.
 
-Emulators are used to emulate hardware devices, to support testing of
+Emulators are used to emulate external hardware devices, to support testing of
 various subsystems. For example, it is possible to write an emulator
 for an I2C compass such that it appears on the I2C bus and can be used
 just like a real hardware device.
@@ -141,8 +141,6 @@ Available Emulators
 
 Zephyr includes the following emulators:
 
-* EEPROM, which uses a file as the EEPROM contents
-
 * I2C emulator driver, allowing drivers to be connected to an emulator so that
   tests can be performed without access to the real hardware
 
@@ -151,10 +149,6 @@ Zephyr includes the following emulators:
 * eSPI emulator driver, which does the same for eSPI. The emulator is being
   developed to support more functionalities.
 
-* CAN loopback driver
-
-A GPIO emulator is planned but is not yet complete.
-
 Samples
 =======
 
@@ -167,13 +161,6 @@ Here are some examples present in Zephyr:
       :board: native_sim
       :goals: build
 
-#. Simple test of the EEPROM emulator:
-
-   .. zephyr-app-commands::
-      :app: tests/drivers/eeprom/api
-      :board: native_sim
-      :goals: build
-
 #. The same test can be built with a second EEPROM which is an Atmel AT24 EEPROM driver
    connected via I2C an emulator: