drivers/comedi/drivers/amplc_dio200.c
Source file repositories/reference/linux-study-clean/drivers/comedi/drivers/amplc_dio200.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/comedi/drivers/amplc_dio200.c- Extension
.c- Size
- 9942 bytes
- Lines
- 267
- Domain
- Driver Families
- Bucket
- drivers/comedi
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/module.hlinux/comedi/comedidev.hamplc_dio200.h
Detected Declarations
function dio200_attach
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0+
/*
* comedi/drivers/amplc_dio200.c
*
* Driver for Amplicon PC212E, PC214E, PC215E, PC218E, PC272E.
*
* Copyright (C) 2005-2013 MEV Ltd. <https://www.mev.co.uk/>
*
* COMEDI - Linux Control and Measurement Device Interface
* Copyright (C) 1998,2000 David A. Schleef <ds@schleef.org>
*/
/*
* Driver: amplc_dio200
* Description: Amplicon 200 Series ISA Digital I/O
* Author: Ian Abbott <abbotti@mev.co.uk>
* Devices: [Amplicon] PC212E (pc212e), PC214E (pc214e), PC215E (pc215e),
* PC218E (pc218e), PC272E (pc272e)
* Updated: Mon, 18 Mar 2013 14:40:41 +0000
*
* Status: works
*
* Configuration options:
* [0] - I/O port base address
* [1] - IRQ (optional, but commands won't work without it)
*
* Passing a zero for an option is the same as leaving it unspecified.
*
* SUBDEVICES
*
* PC212E PC214E PC215E
* ------------- ------------- -------------
* Subdevices 6 4 5
* 0 PPI-X PPI-X PPI-X
* 1 CTR-Y1 PPI-Y PPI-Y
* 2 CTR-Y2 CTR-Z1* CTR-Z1
* 3 CTR-Z1 INTERRUPT* CTR-Z2
* 4 CTR-Z2 INTERRUPT
* 5 INTERRUPT
*
* PC218E PC272E
* ------------- -------------
* Subdevices 7 4
* 0 CTR-X1 PPI-X
* 1 CTR-X2 PPI-Y
* 2 CTR-Y1 PPI-Z
* 3 CTR-Y2 INTERRUPT
* 4 CTR-Z1
* 5 CTR-Z2
* 6 INTERRUPT
*
* Each PPI is a 8255 chip providing 24 DIO channels. The DIO channels
* are configurable as inputs or outputs in four groups:
*
* Port A - channels 0 to 7
* Port B - channels 8 to 15
* Port CL - channels 16 to 19
* Port CH - channels 20 to 23
*
* Only mode 0 of the 8255 chips is supported.
*
* Each CTR is a 8254 chip providing 3 16-bit counter channels. Each
* channel is configured individually with INSN_CONFIG instructions. The
* specific type of configuration instruction is specified in data[0].
* Some configuration instructions expect an additional parameter in
* data[1]; others return a value in data[1]. The following configuration
* instructions are supported:
*
* INSN_CONFIG_SET_COUNTER_MODE. Sets the counter channel's mode and
* BCD/binary setting specified in data[1].
*
* INSN_CONFIG_8254_READ_STATUS. Reads the status register value for the
* counter channel into data[1].
*
* INSN_CONFIG_SET_CLOCK_SRC. Sets the counter channel's clock source as
* specified in data[1] (this is a hardware-specific value). Not
* supported on PC214E. For the other boards, valid clock sources are
* 0 to 7 as follows:
*
* 0. CLK n, the counter channel's dedicated CLK input from the SK1
* connector. (N.B. for other values, the counter channel's CLKn
* pin on the SK1 connector is an output!)
* 1. Internal 10 MHz clock.
* 2. Internal 1 MHz clock.
* 3. Internal 100 kHz clock.
* 4. Internal 10 kHz clock.
* 5. Internal 1 kHz clock.
* 6. OUT n-1, the output of counter channel n-1 (see note 1 below).
* 7. Ext Clock, the counter chip's dedicated Ext Clock input from
* the SK1 connector. This pin is shared by all three counter
Annotation
- Immediate include surface: `linux/module.h`, `linux/comedi/comedidev.h`, `amplc_dio200.h`.
- Detected declarations: `function dio200_attach`.
- Atlas domain: Driver Families / drivers/comedi.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.