IBM DTTA-351010 Hard Drive Specifications - Page 101

DMA Queued Commands

Page 101 highlights

data transfers are performed using the slave-DMA channel no intermediate sector interrupts are issued on multi-sector commands Initiation of the D M A transfer commands is identical to the Read Sector or Write Sector commands except that the host initializes the slave-DMA channel prior to issuing the command. The interrupt handler for D M A transfers is different in that: no intermediate sector interrupts are issued on multi-sector commands the host resets the DMA channel prior to reading status from the device. The DMA protocol allows high performance multi-tasking operating systems to eliminate processor overhead associated with PIO transfers. 1. Host initializes the slave-DMA channel 2. Host writes any required parameters to the Features, Sector Count, Sector Number, Cylinder and Device/Head registers. 3. Host writes command code to the Command Register 4. The device sets D M A R Q when it is ready to transfer any part of the data. 5. Host transfers the data using the DMA transfer protocol currently in effect. 6. When all of the data has been transferred, the device generates an interrupt to the host. 7. Host resets the slave-DMA channel 8. Host reads the Status Register and, optionally, the Error Register 11.5 DMA Queued Commands These commands are: Read DMA Queued Service Write DMA Queued 1. Command Issue a. The host writes any required parameters to the Features, Sector Count, Sector Number, Cylinder and Device/Head registers. b. The host writes command code to the Command Register c. The device sets BSY. d. The device clears or sets REL. e. The device clears BSY. 2. Data Transfer and Command Completion If the device is ready for data transfer (REL is cleared), a. The host transfers the data for the command identified by the Tag number using the DMA transfer protocol currently in effect. b. When all of the data has been transferred, the device generates an interrupt to the host. Command Protocol 93

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188

data transfers are performed using the slave-DMA channel
no intermediate sector interrupts are issued on multi-sector commands
Initiation of the DMA transfer commands is identical to the Read Sector or Write Sector commands except
that the host initializes the slave-DMA channel prior to issuing the command.
The interrupt handler for DMA transfers is different in that:
no intermediate sector interrupts are issued on multi-sector commands
the host resets the DMA channel prior to reading status from the device.
The DMA protocol allows high performance multi-tasking operating systems to eliminate processor over-
head associated with PIO transfers.
1. Host initializes the slave-DMA channel
2. Host
writes any required parameters to
the Features,
Sector Count, Sector Number, Cylinder and
Device/Head registers.
3. Host writes command code to the Command Register
4. The device sets DMARQ when it is ready to transfer any part of the data.
5. Host transfers the data using the DMA transfer protocol currently in effect.
6. When all of the data has been transferred, the device generates an interrupt to the host.
7. Host resets the slave-DMA channel
8. Host reads the Status Register and, optionally, the Error Register
11.5
DMA Queued Commands
These commands are:
Read DMA Queued
Service
Write DMA Queued
1. Command Issue
a. The host writes any required parameters to the Features, Sector Count, Sector Number, Cylinder
and Device/Head registers.
b. The host writes command code to the Command Register
c. The device sets BSY.
d. The device clears or sets REL.
e. The device clears BSY.
2. Data Transfer and Command Completion
If the device is ready for data transfer (REL is cleared),
a. The host transfers the data for the command identified by the Tag number using the DMA transfer
protocol currently in effect.
b. When all of the data has been transferred, the device generates an interrupt to the host.
Command Protocol
93