nvidia-tegra-modules.git/drivers/net/usb, branch gpu-paging NVIDIA's kernel modules to support tegra chips (used in Jetson boards) driver: net: usb: Add kconfig & makefile for r8152 2018-02-15T06:03:09+00:00 Vladislav Zhurba vzhurba@nvidia.com 2018-02-12T19:36:52+00:00 ecd7b21e34895a03214ffffeb0eea6053639dcdf Bug 2054909 Change-Id: I5246129f9bf2541933d87c5d876f6fe31b231a3f Signed-off-by: Vladislav Zhurba <vzhurba@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1656103 GVS: Gerrit_Virtual_Submit Reviewed-by: Sachin Nikam <snikam@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Bug 2054909

Change-Id: I5246129f9bf2541933d87c5d876f6fe31b231a3f
Signed-off-by: Vladislav Zhurba <vzhurba@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1656103
GVS: Gerrit_Virtual_Submit
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
r8152: use mac address from DTB entry or OTP 2018-02-01T21:58:01+00:00 Zheng Liu zhliu@nvidia.com 2015-07-01T17:47:06+00:00 02192066749f4afda443a4ce9dd75c54a48e568b Search for MAC address in this order: 1. For built-in device, look in DTB (populated from EEPROM) 2. For add-on device or if DTB does not contain valid entry, look in OTP The factory default setting has the same Nvidia-assigned address in both OTP and EEPROM. Either location can be overwritten to override the default address. The bootloader will add a DTB entry for the address found in EEPROM. Rationale for this approach: - Some customers may not have the tools to reprogram OTP, so EEPROM/DTB needs to have higher precedence than Nvidia OTP setting. - In case there is an add-on device that also uses this driver, it must use its own OTP setting, and not steal the address in EEPROM. - The upstream driver has no knowledge of EEPROM/DTB, so OTP needs to contain a valid address. Bug 1655596 Change-Id: Icb62e2d7a31dbd6b350ec5076e83862929b841f3 Signed-off-by: Zheng Liu <zhliu@nvidia.com> Reviewed-on: http://git-master/r/758238 (cherry picked from commit 8751b8cb32f6664c5f530e10c347956aa25b7c41) Reviewed-on: http://git-master/r/793409 GVS: Gerrit_Virtual_Submit Reviewed-by: Allen Martin <amartin@nvidia.com> 
Search for MAC address in this order:
1. For built-in device, look in DTB (populated from EEPROM)
2. For add-on device or if DTB does not contain valid entry,
   look in OTP

The factory default setting has the same Nvidia-assigned address
in both OTP and EEPROM.
Either location can be overwritten to override the default address.
The bootloader will add a DTB entry for the address found in EEPROM.

Rationale for this approach:
- Some customers may not have the tools to reprogram OTP, so EEPROM/DTB
needs to have higher precedence than Nvidia OTP setting.
- In case there is an add-on device that also uses this driver, it must
use its own OTP setting, and not steal the address in EEPROM.
- The upstream driver has no knowledge of EEPROM/DTB, so OTP needs to
contain a valid address.

Bug 1655596

Change-Id: Icb62e2d7a31dbd6b350ec5076e83862929b841f3
Signed-off-by: Zheng Liu <zhliu@nvidia.com>
Reviewed-on: http://git-master/r/758238
(cherry picked from commit 8751b8cb32f6664c5f530e10c347956aa25b7c41)
Reviewed-on: http://git-master/r/793409
GVS: Gerrit_Virtual_Submit
Reviewed-by: Allen Martin <amartin@nvidia.com>
r8152: add support for nvidia vid/pid for rtl8153 2018-02-01T21:58:01+00:00 Zheng Liu zhliu@nvidia.com 2015-06-27T00:23:50+00:00 dc8c086b555e00bf3f582c9c14bf62883234ac33 Add the following VID/PID pair to the supported devices list: VID: 0x0955 PID: 0x09FF These are the USB IDs assigned to the RTL8153 part on tegra boards. Bug 1655596 Change-Id: Ida74181b268bd4feee0ba2a9a5d62805782ad365 Signed-off-by: Zheng Liu <zhliu@nvidia.com> Reviewed-on: http://git-master/r/763199 (cherry picked from commit 15bd40e232479bb8c97e107871545d83fb9759a5) Reviewed-on: http://git-master/r/764888 Reviewed-by: Allen Martin <amartin@nvidia.com> 
Add the following VID/PID pair to the supported devices list:
VID: 0x0955
PID: 0x09FF

These are the USB IDs assigned to the RTL8153 part on tegra boards.

Bug 1655596

Change-Id: Ida74181b268bd4feee0ba2a9a5d62805782ad365
Signed-off-by: Zheng Liu <zhliu@nvidia.com>
Reviewed-on: http://git-master/r/763199
(cherry picked from commit 15bd40e232479bb8c97e107871545d83fb9759a5)
Reviewed-on: http://git-master/r/764888
Reviewed-by: Allen Martin <amartin@nvidia.com>
r8152: Disable random mac address 2018-02-01T21:58:01+00:00 Aly Hirani ahirani@nvidia.com 2015-02-13T23:57:30+00:00 7f7cb2472fab0d69d77e5f17494824fd607f93e9 We want to explicitly hard fail if we've never fused a mac address. If the mac address is not fused, there is a chance that the stability bits for ethernet is also not fused. In that scenario, with the random mac address, we'll get a user who thinks his ethernet is fine (because of the random address), but ethernet will quickly fail within minutes. Bug 1611325 Change-Id: I79767fe05fa2fd40bf3fc5292d9e17a36e2d6151 Signed-off-by: Aly Hirani <ahirani@nvidia.com> Reviewed-on: http://git-master/r/707984 (cherry picked from commit 4860367055ac347a7c75540b4cc5f379ff99a8ce) Reviewed-on: http://git-master/r/716077 GVS: Gerrit_Virtual_Submit Reviewed-by: Zheng Liu <zhliu@nvidia.com> Reviewed-by: Mitch Luban <mluban@nvidia.com> 
We want to explicitly hard fail if we've never fused a mac address. If
the mac address is not fused, there is a chance that the stability bits
for ethernet is also not fused.

In that scenario, with the random mac address, we'll get a user who
thinks his ethernet is fine (because of the random address), but
ethernet will quickly fail within minutes.

Bug 1611325

Change-Id: I79767fe05fa2fd40bf3fc5292d9e17a36e2d6151
Signed-off-by: Aly Hirani <ahirani@nvidia.com>
Reviewed-on: http://git-master/r/707984
(cherry picked from commit 4860367055ac347a7c75540b4cc5f379ff99a8ce)
Reviewed-on: http://git-master/r/716077
GVS: Gerrit_Virtual_Submit
Reviewed-by: Zheng Liu <zhliu@nvidia.com>
Reviewed-by: Mitch Luban <mluban@nvidia.com>
net: usb: r8152: disable autosuspend 2018-02-01T21:58:01+00:00 Aly Hirani ahirani@nvidia.com 2015-02-05T20:37:11+00:00 0c5070d8a60089394da57beb364e9379a4476970 We've seen some issues with the Tegra XUSB controller resuming from autosuspend. This change disables autosuspend until the XUSB team can understand the issue Bug 1604791 Bug 200091204 Change-Id: I9e7b4b85fe31a1a88e1f9e19d856c52f69dbb1b0 Signed-off-by: Aly Hirani <ahirani@nvidia.com> Reviewed-on: http://git-master/r/681672 (cherry picked from commit fb40b49a54b23e3d592f69170172000d3a08e6b7) Reviewed-on: http://git-master/r/744734 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Tested-by: Bharat Nihalani <bnihalani@nvidia.com> 
We've seen some issues with the Tegra XUSB controller resuming from
autosuspend. This change disables autosuspend until the XUSB team can
understand the issue

Bug 1604791
Bug 200091204

Change-Id: I9e7b4b85fe31a1a88e1f9e19d856c52f69dbb1b0
Signed-off-by: Aly Hirani <ahirani@nvidia.com>
Reviewed-on: http://git-master/r/681672
(cherry picked from commit fb40b49a54b23e3d592f69170172000d3a08e6b7)
Reviewed-on: http://git-master/r/744734
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
drivers: net: usb: Update to r8152.53-2.03.3 2018-02-01T21:58:01+00:00 Aly Hirani ahirani@nvidia.com 2014-12-27T07:03:15+00:00 2d8c32f92fae5783a41d1326f7424247baaaf775 This commit adds the latest Realtek's recommended RTL8153 vendor driver. This fixes the packet loss issue on top of the v2.03.0 (which was breaking GameStream). Bug 1604791 Change-Id: I46926b984a6252a27492f824200b7f3b5e9acb58 Signed-off-by: Aly Hirani <ahirani@nvidia.com> Reviewed-on: http://git-master/r/681275 (cherry picked from commit 904cb4c43d17bf4a6fd94c800e814194c661f138) Reviewed-on: http://git-master/r/716075 Reviewed-by: Mitch Luban <mluban@nvidia.com> 
This commit adds the latest Realtek's recommended RTL8153
vendor driver. This fixes the packet loss issue on top of the v2.03.0
(which was breaking GameStream).

Bug 1604791

Change-Id: I46926b984a6252a27492f824200b7f3b5e9acb58
Signed-off-by: Aly Hirani <ahirani@nvidia.com>
Reviewed-on: http://git-master/r/681275
(cherry picked from commit 904cb4c43d17bf4a6fd94c800e814194c661f138)
Reviewed-on: http://git-master/r/716075
Reviewed-by: Mitch Luban <mluban@nvidia.com>
r8152: fix setting RTL8152_UNPLUG 2018-02-01T21:58:01+00:00 hayeswang hayeswang@realtek.com 2014-09-30T08:48:01+00:00 f2f8e8656c90d7f43e5ce540ed70c0db05f46666 The flag of RTL8152_UNPLUG should only be set when the device is unplugged, not each time the rtl8152_disconnect() is called. Otherwise, the device wouldn't be stopped normally. From http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=f561de33d63aefb97fb0c3653a36fb32d4e8c74a Change-Id: I7dbc931baa65efa46d572ebd7b93209e6fe01751 Signed-off-by: Hayes Wang <hayeswang@realtek.com> Signed-off-by: David S. Miller <davem@davemloft.net> (cherry picked from upstream commit f561de33d63aefb97fb0c3653a36fb32d4e8c74a) Signed-off-by: Aly Hirani <ahirani@nvidia.com> Reviewed-on: http://git-master/r/553398 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
The flag of RTL8152_UNPLUG should only be set when the device is
unplugged, not each time the rtl8152_disconnect() is called.
Otherwise, the device wouldn't be stopped normally.

From http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=f561de33d63aefb97fb0c3653a36fb32d4e8c74a

Change-Id: I7dbc931baa65efa46d572ebd7b93209e6fe01751
Signed-off-by: Hayes Wang <hayeswang@realtek.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
(cherry picked from upstream commit f561de33d63aefb97fb0c3653a36fb32d4e8c74a)
Signed-off-by: Aly Hirani <ahirani@nvidia.com>
Reviewed-on: http://git-master/r/553398
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
r8152: fix the carrier off when autoresuming 2018-02-01T21:58:01+00:00 hayeswang hayeswang@realtek.com 2014-09-23T08:31:47+00:00 8c28a723551869ae40d25be8e000d10c606a1e10 netif_carrier_off would be called when autoresuming, even though the cable is plugged. This causes some applications do relative actions when detecting the carrier off. Keep the status of the carrier, and let it be modified when the linking change occurs. From http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=445f7f4d62628cb2971db884084d162ecb622ec7 Change-Id: I4998c7585e5e707387242d5fbac6d6b5f1654ba7 Signed-off-by: Hayes Wang <hayeswang@realtek.com> Signed-off-by: David S. Miller <davem@davemloft.net> (cherry picked from upstream commit 445f7f4d62628cb2971db884084d162ecb622ec7) Signed-off-by: Aly Hirani <ahirani@nvidia.com> Reviewed-on: http://git-master/r/552185 Reviewed-by: Vinayak Pane <vpane@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
netif_carrier_off would be called when autoresuming, even though
the cable is plugged. This causes some applications do relative
actions when detecting the carrier off. Keep the status of the
carrier, and let it be modified when the linking change occurs.

From http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=445f7f4d62628cb2971db884084d162ecb622ec7

Change-Id: I4998c7585e5e707387242d5fbac6d6b5f1654ba7
Signed-off-by: Hayes Wang <hayeswang@realtek.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
(cherry picked from upstream commit 445f7f4d62628cb2971db884084d162ecb622ec7)
Signed-off-by: Aly Hirani <ahirani@nvidia.com>
Reviewed-on: http://git-master/r/552185
Reviewed-by: Vinayak Pane <vpane@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
r8152: disable ALDPS 2018-02-01T21:58:01+00:00 hayeswang hayeswang@realtek.com 2014-09-19T07:17:18+00:00 c5c5705cbad0378713704ace15c3f2b6c90e8955 If the hw is in ALDPS mode, the hw may have no response for accessing the most registers. Therefore, the ALDPS should be disabled before accessing the hw in rtl_ops.init(), rtl_ops.disable(), rtl_ops.up(), and rtl_ops.down(). Regardless of rtl_ops.enable(), because the hw wouldn't enter ALDPS mode when linking on. The hw would enter the ALDPS mode after several seconds when link down occurs and the ALDPS is enabled. From http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=d70b1137233836be1d71bd53ae60bec6c9e7203c Change-Id: I29cc1307178e02b2f00df6b1fa9f316ad3b7a0d8 Signed-off-by: Hayes Wang <hayeswang@realtek.com> Signed-off-by: David S. Miller <davem@davemloft.net> (cherry picked from upstream commit d70b1137233836be1d71bd53ae60bec6c9e7203c) Signed-off-by: Aly Hirani <ahirani@nvidia.com> Reviewed-on: http://git-master/r/553397 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
If the hw is in ALDPS mode, the hw may have no response for accessing
the most registers. Therefore, the ALDPS should be disabled before
accessing the hw in rtl_ops.init(), rtl_ops.disable(), rtl_ops.up(),
and rtl_ops.down(). Regardless of rtl_ops.enable(), because the hw
wouldn't enter ALDPS mode when linking on. The hw would enter the
ALDPS mode after several seconds when link down occurs and the ALDPS
is enabled.

From http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=d70b1137233836be1d71bd53ae60bec6c9e7203c

Change-Id: I29cc1307178e02b2f00df6b1fa9f316ad3b7a0d8
Signed-off-by: Hayes Wang <hayeswang@realtek.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
(cherry picked from upstream commit d70b1137233836be1d71bd53ae60bec6c9e7203c)
Signed-off-by: Aly Hirani <ahirani@nvidia.com>
Reviewed-on: http://git-master/r/553397
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
r8152: fix the checking of the usb speed 2018-02-01T21:58:01+00:00 hayeswang hayeswang@realtek.com 2014-07-24T08:37:43+00:00 7ea400d17c7befc07881f52d289242df0c366e81 When the usb speed of the RTL8152 is not high speed, the USB_DEV_STAT[2:1] should be equal to [0 1]. That is, the STAT_SPEED_FULL should be equal to 2. There is a easy way to check the usb speed by the speed field of the struct usb_device. Use it to replace the original metheod. From http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=a3cc465d95c32bfb529f69dee7841ecd67525561 Change-Id: I681d5daed3590845003d82faa923de129483ffa6 Signed-off-by: Hayes Wang <hayeswang@realtek.com> Spotted-by: Andrey Utkin <andrey.krieger.utkin@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net> (cherry picked from upstream commit a3cc465d95c32bfb529f69dee7841ecd67525561) Signed-off-by: Aly Hirani <ahirani@nvidia.com> Reviewed-on: http://git-master/r/553396 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
When the usb speed of the RTL8152 is not high speed, the USB_DEV_STAT[2:1]
should be equal to [0 1]. That is, the STAT_SPEED_FULL should be equal
to 2.

There is a easy way to check the usb speed by the speed field of the
struct usb_device. Use it to replace the original metheod.

From http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=a3cc465d95c32bfb529f69dee7841ecd67525561

Change-Id: I681d5daed3590845003d82faa923de129483ffa6
Signed-off-by: Hayes Wang <hayeswang@realtek.com>
Spotted-by: Andrey Utkin <andrey.krieger.utkin@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
(cherry picked from upstream commit a3cc465d95c32bfb529f69dee7841ecd67525561)
Signed-off-by: Aly Hirani <ahirani@nvidia.com>
Reviewed-on: http://git-master/r/553396
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>