nuttx/drivers
jianglianfang 5accd7c146 drivers/video: add Goldfish-FB driver
the register definition is described here:
https://android.googlesource.com/platform/external/qemu/+/master/docs/GOLDFISH-VIRTUAL-HARDWARE.TXT

Goldfish-FB driver is to communicate with Goldfish-FB in QEMU, and push the framebuffer data to the emulator for display on the screen.
test: CONFIG_GOLDFISH_FB =1, and run demo=>lvgldemo widgets

Signed-off-by: jianglianfang <jianglianfang@xiaomi.com>
2023-08-13 11:51:30 -03:00
..
1wire 1wrie:fix typo 2023-08-03 00:06:24 -07:00
analog
audio driver/audio: low level reset must always succeed 2023-07-18 10:14:24 -03:00
bch bch: fix sector buffer invalidation issue 2023-07-29 06:56:28 -07:00
can drivers: restore C89 compatibility by avoiding binary constants 2023-07-31 18:56:40 -07:00
clk drivers/clk: support using clk function at interrupt and idle 2023-07-28 07:12:51 -07:00
contactless
crypto Revert "Don't call lib_free in the kernel code" 2023-08-08 11:58:29 -03:00
devicetree fdt: Add initial FDT support and procfs for userspace export 2023-08-05 12:41:06 -07:00
dma
dummy
eeprom
efuse nuttx: use lib_free for memory de-allocation after strdup or asprintf 2023-08-08 11:58:29 -03:00
i2c drivers: restore C89 compatibility by avoiding binary constants 2023-07-31 18:56:40 -07:00
i2s
input drivers/input: rm sched_[un]lock 2023-08-12 23:32:38 +08:00
ioexpander ioexpander: add option to register GPIO by name for IOexpander 2023-08-03 07:02:12 -07:00
ipcc
lcd Kconfig: Simplify the conditional default statement 2023-07-16 14:39:20 -03:00
leds New implementation of the ESP32's RMT driver. 2023-07-23 16:17:57 -03:00
loop
math math acceleration api support FFT 2023-08-11 20:38:00 +08:00
misc drivers/misc/rpmsgblk: fix build break if CONFIG_DISABLE_PSEUDOFS_OPERATIONS 2023-08-11 21:20:40 +08:00
mmcsd fix byte_block_count error in byte mode 2023-08-11 13:15:57 +08:00
modem nuttx: use lib_free for memory de-allocation after strdup or asprintf 2023-08-08 11:58:29 -03:00
motor cmake: fix CMake build break 2023-07-15 23:32:36 +08:00
mtd driver/mtd_config: just query when data is null or len is zero 2023-08-07 05:45:56 -07:00
net c89: move variable declaration out from the for loop 2023-08-08 11:58:29 -03:00
note note: simplify noteram logic 2023-08-11 13:27:17 +08:00
pipes drivers/pipes: use circbuf to refine buffer model 2023-08-10 03:33:56 +08:00
power battery:add goldfish battery driver 2023-08-11 15:30:35 +08:00
rc Fix Kconfig style 2023-08-02 16:57:09 +02:00
reset added mutex lock before lookup reset controller by name 2023-08-11 20:39:16 +08:00
rf
rptun rptun: fix use after free caused by API wrong order 2023-08-03 10:53:49 -07:00
segger drivers/rtt: add rtt syslog channel configuration 2023-08-11 18:13:52 +08:00
sensors feature: sensor: add force sensor 2023-08-09 21:57:58 +08:00
serial filter out control character in pty echo 2023-08-11 13:58:54 +08:00
spi spi/slave: use POLLPRI to notify TX_COMPLETE. 2023-08-12 02:02:50 +08:00
syslog nuttx: use lib_free for memory de-allocation after strdup or asprintf 2023-08-08 11:58:29 -03:00
timers perf: The new configuration supports hardware performance counting 2023-08-12 02:20:44 +08:00
usbdev usbdev/composite: winusb devices are not automatically recognized by windows 2023-08-11 13:19:13 +08:00
usbhost drivers: usbhost: fix usbhost_hidkbd some errors 2023-07-27 00:51:59 -07:00
usbmisc
usbmonitor
usrsock usrsock_server: coverity fix for access invalid index 2023-08-11 15:29:59 +08:00
video drivers/video: add Goldfish-FB driver 2023-08-13 11:51:30 -03:00
virtio drivers/virtio: add virtio input driver 2023-08-13 11:47:39 -03:00
wireless Revert "Don't call lib_free in the kernel code" 2023-08-08 11:58:29 -03:00
.gitignore
CMakeLists.txt
drivers_initialize.c virtio: add virtio framework in NuttX 2023-08-10 03:39:39 +08:00
Kconfig support nuttx reset driver model 2023-08-11 20:39:16 +08:00
Makefile support nuttx reset driver model 2023-08-11 20:39:16 +08:00
README.txt

README
^^^^^^

This directory contains various device drivers -- both block and
character drivers as well as other more specialized drivers.

Contents:
  - Files in this directory
  - Subdirectories of this directory
  - Skeleton files

Files in this directory
^^^^^^^^^^^^^^^^^^^^^^^

dev_null.c and dev_zero.c
  These files provide the standard /dev/null and /dev/zero devices.  See
  include/nuttx/drivers/drivers.h for prototypes of functions that should
  be called if you want to register these devices (devnull_register()
  and devzero_register()).

ramdisk.c
  Can be used to set up a block of memory or (read-only) FLASH as
  a block driver that can be mounted as a file system.  See
  include/nuttx/drivers/ramdisk.h.

rwbuffer.c
  A facility that can be used by any block driver in-order to add
  writing buffering and read-ahead buffering.

Subdirectories of this directory:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

analog/
  This directory holds implementations of analog device drivers.
  This includes drivers for Analog to Digital Conversion (ADC) as
  well as drivers for Digital to Analog Conversion (DAC).
  See include/nuttx/analog/*.h for registration information.

audio/
  Audio device drivers.  See include/nuttx/audio/audio.h for interface
  definitions.  See also the audio subsystem at nuttx/audio/.

bch/
  Contains logic that may be used to convert a block driver into
  a character driver.  This is the complementary conversion as that
  performed by loop.c.  See include/nuttx/fs/fs.h for registration
  information.

can/
  This is the CAN drivers and logic support.  See include/nuttx/can/can.h
  for usage information.

contactless/
  Contactless devices are related to wireless devices.  They are not
  communication devices with other similar peers, but couplers/interfaces
  to contactless cards and tags.

crypto/
  Contains crypto drivers and support logic, including the /dev/urandom
  device.

eeprom/
  An EEPROM is a form of Memory Technology Device (see drivers/mtd).
  EEPROMs are non-volatile memory like FLASH, but differ in underlying
  memory technology and differ in usage in many respects: They may not
  be organized into blocks (at least from the standpoint of the user)
  and it is not necessary to erase the EEPROM memory before re-writing
  it.  In addition, EEPROMs tend to be much smaller than FLASH parts,
  usually only a few kilobytes vs megabytes for FLASH.  EEPROM tends to
  be used to retain a small amount of device configuration information;
  FLASH tends to be used for program or massive data storage. For these
  reasons, it may not be convenient to use the more complex MTD
  interface but instead use the simple character interface provided by
  the EEPROM drivers.

i2c/
  I2C drivers and support logic.  See include/nuttx/i2c/i2c_master.h

i2s/
  I2S drivers and support logic.  See include/nuttx/audio/i2s.h

input/
  This directory holds implementations of human input device (HID)
  drivers.  This includes such things as mouse, touchscreen, joystick,
  keyboard and keypad drivers.  See include/nuttx/input/*.h for
  registration information.

  Note that USB HID devices are treated differently.  These can be
  found under usbdev/ or usbhost/.

lcd/
  Drivers for parallel and serial LCD and OLED type devices.  These
  drivers support interfaces as defined in include/nuttx/lcd/lcd.h

leds/
  Various LED-related drivers including discrete as well as PWM-
  driven LEDs.

loop/
  Supports the standard loop device that can be used to export a
  file (or character device) as a block device.  See losetup() and
  loteardown() in include/nuttx/fs/fs.h.

mmcsd/
  Support for MMC/SD block drivers.  MMC/SD block drivers based on
  SPI and SDIO/MCI interfaces are supported.  See include/nuttx/mmcsd.h
  and include/nuttx/sdio.h for further information.

mtd/
  Memory Technology Device (MTD) drivers.  Some simple drivers for
  memory technologies like FLASH, EEPROM, NVRAM, etc.  See
  include/nuttx/mtd/mtd.h

  (Note: This is a simple memory interface and should not be
  confused with the "real" MTD developed at infradead.org.  This
  logic is unrelated; I just used the name MTD because I am not
  aware of any other common way to refer to this class of devices).

net/
  Network interface drivers.  See also include/nuttx/net/net.h

pipes/
  FIFO and named pipe drivers.  Standard interfaces are declared
  in include/unistd.h

power/
  Power management (PM) driver interfaces.  These interfaces are used
  to manage power usage of a platform by monitoring driver activity
  and by placing drivers into reduce power usage modes when the
  drivers are not active.

pwm/
  Provides the "upper half" of a pulse width modulation (PWM) driver.
  The "lower half" of the PWM driver is provided by device-specific
  logic.  See include/nuttx/timers/pwm.h for usage information.

sensors/
  Drivers for various sensors.  A sensor driver differs little from
  other types of drivers other than they are use to provide measurements
  of things in environment like temperature, orientation, acceleration,
  altitude, direction, position, etc.

  DACs might fit this definition of a sensor driver as well since they
  measure and convert voltage levels.  DACs, however, are retained in
  the analog/ sub-directory.

serial/
  Front-end character drivers for chip-specific UARTs.  This provide
  some TTY-like functionality and are commonly used (but not required for)
  the NuttX system console.  See also include/nuttx/serial/serial.h

spi/
  SPI drivers and support logic.  See include/nuttx/spi/spi.h

syslog/
  System logging devices. See include/syslog.h and include/nuttx/syslog/syslog.h

timers/
  Includes support for various timer devices including:

  - An "upper half" for a generic timer driver.  See
    include/nuttx/timers/timer.h for more information.

  - An "upper half" for a generic watchdog driver.  See
    include/nuttx/timers/watchdog.h for more information.

  - RTC drivers

usbdev/
  USB device drivers.  See also include/nuttx/usb/usbdev.h

usbhost/
  USB host drivers.  See also include/nuttx/usb/usbhost.h

video/
  Video-related drivers.  See include/nuttx/video/.

wireless/
  Drivers for various wireless devices.

Skeleton Files
^^^^^^^^^^^^^^

Skeleton files are "empty" frameworks for NuttX drivers.  They are provided to
give you a good starting point if you want to create a new NuttX driver.
The following skeleton files are available:

  drivers/lcd/skeleton.c -- Skeleton LCD driver
  drivers/mtd/skeleton.c -- Skeleton memory technology device drivers
  drivers/net/skeleton.c -- Skeleton network/Ethernet drivers
  drivers/usbhost/usbhost_skeleton.c -- Skeleton USB host class driver