zephyrproject-rtos/zephyr
0
0
Fork 0
mirror of https://github.com/zephyrproject-rtos/zephyr synced 2025-08-12 06:46:05 +00:00
Code Issues Packages Projects Releases Wiki Activity
f08f9d6410
zephyr/samples/drivers/espi
History
Maksim Masalski f08f9d6410 samples: exclude mec15xxevb_assy6853 in espi sample when sanitycheck 
ESPI is supported in MEC15 chips but similar to PECI, I2C, eSPI bus
testing requires another device to act as eSPI host.
While this sample can be run in EVB the HW connection to a eSPI host
(Intel RVP) is not documented/supported.

Mark as not supported in that HW only in Modular card
(which setup is documented)

Also remove duplicate definition of the "depends_on: espi"
in the end of the sample.yaml file

Signed-off-by: Maksim Masalski <maksim.masalski@intel.com>
2020-09-17 16:13:51 -05:00
..
boards samples: drivers: espi: Convert espi sample to devicetree 2020-08-18 14:22:10 -04:00
dts/bindings samples: drivers: espi: Convert espi sample to devicetree 2020-08-18 14:22:10 -04:00
src device: Const-ify all device driver instance pointers 2020-09-02 13:48:13 +02:00
CMakeLists.txt samples: drivers: espi: Convert espi sample to devicetree 2020-08-18 14:22:10 -04:00
Kconfig samples: drivers: espi: Convert espi sample to devicetree 2020-08-18 14:22:10 -04:00
prj_mec1501modular_assy6885.conf samples: drivers: espi: Convert espi sample to devicetree 2020-08-18 14:22:10 -04:00
prj.conf
README.rst samples: exclude mec15xxevb_assy6853 in espi sample when sanitycheck 2020-09-17 16:13:51 -05:00
sample.yaml samples: exclude mec15xxevb_assy6853 in espi sample when sanitycheck 2020-09-17 16:13:51 -05:00

README.rst 

.. _espi-sample:

Enhanced Serial Peripheral Interface
####################################

Overview
********

This sample demonstrates how to use the Enhanced Serial Peripheral Interface
(eSPI) API.
It shows how to configure and select eSPI controller capabilities as part of
a simple eSPI handshake that includes exchanging virtual wire packets.

Standard platform signals are sent virtual wire packets over the bus.
Callbacks are registered that will write to the console indicating main
eSPI events and when a virtual wire is received.

Building and Running
********************

The sample can be built and executed on boards supporting eSPI.
Any pins required for minimum eSPI handshake should be configured.
Sample requires a correct harness and fixture setup.
Please connect an eSPI device to the testing board.
After that for the correct execution of that sample in sanitycheck, add into
boards's map-file next fixture settings::

      - fixture: espi_device_connect

Sample output
=============

.. code-block:: console

   Hello eSPI test!
   eSPI test - I/O initialization...complete
   eSPI slave configured successfully!
   eSPI test - callbacks initialization... complete
   eSPI test - callbacks registration... complete
   eSPI test - Power initialization...complete
   eSPI test - Handshake
   eSPI BUS reset 0
   VW channel is ready

   PLT_RST changed 1
        1st phase completed
        2nd phase completed
        3rd phase completed

note:: The values shown above might differ.