Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
linux
Commits
be48113b
Commit
be48113b
authored
Jul 05, 2004
by
David S. Miller
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[TG3]: Delay both before and after PCI cfg space readback after reset.
parent
07f0a148
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
17 additions
and
1 deletion
+17
-1
drivers/net/tg3.c
drivers/net/tg3.c
+17
-1
No files found.
drivers/net/tg3.c
View file @
be48113b
...
@@ -3630,9 +3630,25 @@ static int tg3_chip_reset(struct tg3 *tp)
...
@@ -3630,9 +3630,25 @@ static int tg3_chip_reset(struct tg3 *tp)
/* restore 5701 hardware bug workaround flag */
/* restore 5701 hardware bug workaround flag */
tp
->
tg3_flags
=
flags_save
;
tp
->
tg3_flags
=
flags_save
;
/* Unfortunately, we have to delay before the PCI read back.
* Some 575X chips even will not respond to a PCI cfg access
* when the reset command is given to the chip.
*
* How do these hardware designers expect things to work
* properly if the PCI write is posted for a long period
* of time? It is always necessary to have some method by
* which a register read back can occur to push the write
* out which does the reset.
*
* For most tg3 variants the trick below was working.
* Ho hum...
*/
udelay
(
120
);
/* Flush PCI posted writes. The normal MMIO registers
/* Flush PCI posted writes. The normal MMIO registers
* are inaccessible at this time so this is the only
* are inaccessible at this time so this is the only
* way to make this reliably. I tried to use indirect
* way to make this reliably (actually, this is no longer
* the case, see above). I tried to use indirect
* register read/write but this upset some 5701 variants.
* register read/write but this upset some 5701 variants.
*/
*/
pci_read_config_dword
(
tp
->
pdev
,
PCI_COMMAND
,
&
val
);
pci_read_config_dword
(
tp
->
pdev
,
PCI_COMMAND
,
&
val
);
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment