On Fri, 26 Jul 2013 09:18:03 +0200 Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
Hi Wei,
thanks for the link. I didn't search for processor BKDG, only for chipset BKDG. That's why I missed the Family 16h BKDG which includes the SPI controller documentation.
On Thu, Jul 25, 2013 at 7:21 PM, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
Am 27.06.2013 02:34 schrieb Wei Hu:
A quick hack to support AMD Family 16h SOC (Kabini). This patch is just a proof of concept and incompatible with previous generations of AMD chipset. Tested reading and writing on ASRock IMB-A180.
Signed-off-by: Wei Hu wei@aristanetworks.com
I have tried to change the patch in a way which keeps compatibility with older AMD chipsets. Please test with and without USE_THE_EXTENDED_SPIDataFifoPtr_REGISTER #defined. If any errors crop up, please send them to the mailing list in reply to this mail.
I still have to search/replace Hudson with Yangtze, but this patch will help a lot finding out more about the various FIFO related registers.
The code names are complicated.
Jaguar describes the CPU(APU) architecture (succeeding Bobcat), while Kabini (embedded, htpc, laptops) and Temash (tablets) describe SoC families with those cores.
Hudson seems to be the generic code name(!?) for all FCH aka southbridges since sb9xx which came to be when they started with their fusion aka APU development, hence there are multiple generations of Hudson (3 AFAIK, where Yangtze/Salton are #3).
The integrated FCH for Kabini and Temash are codenamed "Yangtze" and "Salton" respectively. I am not aware of the previous code names... The only other FCH name i could find is Yuba but that was never released because it was cancelled together with Krishna/Wichita.
Martin Roth sent me a table matching Hudson generations with model names a few weeks ago:
"FCH Codename A50M Hudson-M1 A45 Hudson-D1 A55E Hudson-E1 A60M Hudson-M2 A68M Hudson-M3L A70M Hudson-M3 A55 Hudson-D2 A68 Hudson-D3L A75 Hudson-D3 A85X Hudson-D4
The last number is the Hudson revision that you want."
Hope that explains at least a bit. No idea (yet) regarding PCI IDs.