[go: nahoru, domu]

History log of /drivers/thunderbolt/eeprom.c
Revision Date Author Comments
e0f550141be3d4c401ae15a0cd1877d4d9665f16 20-Jun-2014 Andreas Noever <andreas.noever@gmail.com> thunderbolt: Make tb_eeprom_get_drom_offset static

tb_eeprom_get_drom_offset is local to this file.

Signed-off-by: Andreas Noever <andreas.noever@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
e7120778a4518a1c8f188ef9865058f7f5a36919 20-Jun-2014 Andreas Noever <andreas.noever@gmail.com> thunderbolt: Make enum tb_drom_entry_type unsigned

Force enum tb_drom_entry_type to unsigned to fix the following error:

drivers/thunderbolt/eeprom.c:202:39: error: dubious one-bit signed bitfield

Signed-off-by: Andreas Noever <andreas.noever@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
3543fb776d8e63934615bf7070ee5fa5a6a7382d 20-Jun-2014 Arnd Bergmann <arnd@arndb.de> thunderbolt: fix format string for size_t

The result of "sizeof(struct tb_drom_entry_port)" is a size_t, which
is not necessarily the same as 'long', so we should use the appropriate
%z format string instead of %l.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Andreas Noever <andreas.noever@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2b35404ef7762af15ce138281c91b4cc0e2d0124 20-Jun-2014 Sachin Kamat <sachin.kamat@samsung.com> thunderbolt: Fix build error in eeprom.c

Fixes the below error:
drivers/thunderbolt/eeprom.c:407:2: error: implicit declaration of function ‘kzalloc’ [-Werror=implicit-function-declaration]
drivers/thunderbolt/eeprom.c:444:2: error: implicit declaration of function ‘kfree’ [-Werror=implicit-function-declaration]

Signed-off-by: Sachin Kamat <sachin.kamat@samsung.com>
Acked-by: Andreas Noever <andreas.noever@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
cd22e73bdf5eff7e68a0f8bdfbce123ad43651f6 12-Jun-2014 Andreas Noever <andreas.noever@gmail.com> thunderbolt: Read port configuration from eeprom.

All Thunderbolt switches (except the root switch) contain a drom which
contains information about the device. Right now we only read the UID.

Add code to read and parse this drom. For now we are only interested in
which ports are disabled and which ports are "dual link ports" (a
physical thunderbolt port/socket contains two such ports).

Signed-off-by: Andreas Noever <andreas.noever@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
c90553b3c4ac2389a71a5c012b6e5bb1160d48a7 03-Jun-2014 Andreas Noever <andreas.noever@gmail.com> thunderbolt: Read switch uid from EEPROM

Add eeprom access code and read the uid during switch initialization.
The UID will be used to check device identity after suspend.

Signed-off-by: Andreas Noever <andreas.noever@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>