docs: i2c: piix4: Fix typos, add markup, drop link

[JD: Update the subject
One more typo fixed
Drop the link to lm-sensors' README, it's irrelevant]

Signed-off-by: Bruce Duncan <bwduncan@gmail.com>
Reviewed-by: Jean Delvare <jdelvare@suse.de>
Signed-off-by: Wolfram Sang <wsa@kernel.org>

authored by Bruce Duncan and committed by Wolfram Sang 53b77471 92d5d643

Changed files
+5 -8
Documentation
i2c
busses
+5 -8
Documentation/i2c/busses/i2c-piix4.rst
··· 64 64 crashes, data corruption, etc.). Try this only as a last resort (try BIOS 65 65 updates first, for example), and backup first! An even more dangerous 66 66 option is 'force_addr=<IOPORT>'. This will not only enable the PIIX4 like 67 - 'force' foes, but it will also set a new base I/O port address. The SMBus 67 + 'force' does, but it will also set a new base I/O port address. The SMBus 68 68 parts of the PIIX4 needs a range of 8 of these addresses to function 69 69 correctly. If these addresses are already reserved by some other device, 70 70 you will get into big trouble! DON'T USE THIS IF YOU ARE NOT VERY SURE ··· 86 86 to change the SMBus Interrupt Select register so the SMBus controller uses 87 87 the SMI mode. 88 88 89 - 1) Use lspci command and locate the PCI device with the SMBus controller: 89 + 1) Use ``lspci`` command and locate the PCI device with the SMBus controller: 90 90 00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 4f) 91 91 The line may vary for different chipsets. Please consult the driver source 92 - for all possible PCI ids (and lspci -n to match them). Lets assume the 92 + for all possible PCI ids (and ``lspci -n`` to match them). Let's assume the 93 93 device is located at 00:0f.0. 94 94 2) Now you just need to change the value in 0xD2 register. Get it first with 95 - command: lspci -xxx -s 00:0f.0 95 + command: ``lspci -xxx -s 00:0f.0`` 96 96 If the value is 0x3 then you need to change it to 0x1: 97 - setpci -s 00:0f.0 d2.b=1 97 + ``setpci -s 00:0f.0 d2.b=1`` 98 98 99 99 Please note that you don't need to do that in all cases, just when the SMBus is 100 100 not working properly. ··· 109 109 Thinkpad laptops, but desktop systems may also be affected. We have no list 110 110 of all affected systems, so the only safe solution was to prevent access to 111 111 the SMBus on all IBM systems (detected using DMI data.) 112 - 113 - For additional information, read: 114 - http://www.lm-sensors.org/browser/lm-sensors/trunk/README