...But then again, maybe it wasn't the cable. It's acting up again.
On Tue, Jan 1, 2019 at 3:14 PM Nathan Royce wrote:
>
> Looks like this particular issue may have been due to a touchy/finicky
> connection.
>
> I removed my tuner from my hub and removed the hub from my
> motherboard's USB and pu
On 30.12.2018 18:34, Philip Langdale wrote:
This fixes a regression since: 2815ef7fe4d43072b9eda448d04fbc184f2aa513
This motherboard is a strange beast, with an Alpine Ridge thunderbolt
controller configured to only do USB with no actual thunderbolt
capabilities (Apparently due to the wiring not
On 01.01.2019 20:57, Nathan Royce wrote:
Kernel 4.19.13
00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB
xHCI Controller
Around 400 "unknown event type 37" messages logged in a 2 second span.
*
Jan 01 02:08:07 computername tvheadend[2370]: linuxdvb: Auvitek AU8522
QAM/8
To match the Corsair Strafe RGB, the Corsair K70 RGB also requires
USB_QUIRK_DELAY_CTRL_MSG to completely resolve boot connection issues
discussed here: https://github.com/ckb-next/ckb-next/issues/42.
Otherwise roughly 1 in 10 boots the keyboard will fail to be detected.
Signed-off-by: Jack Stocke
You're referring to this patch
cb88a0588717 ("usb: quirks: add control message delay for 1b1c:1b20")
I guess. Maybe you want to name it explicitly for better reference.
Acked-by: Danilo Krummrich
On 2019-01-02 19:37, Jack Stocker wrote:
To match the Corsair Strafe RGB, the Corsair K70 RGB als
The information whether the SMSC95xx is in_pm or not can be derived from
the usbdev->suspend_count. First thing called in smsc95xx_suspend() is
usbnet_suspend(), which increments the usbdev->suspend_count and since
then the driver only calls _nopm() functions and functions with in_pm
set to 1. The
Register MII bus so that a phydev can attach to it. This works in
parallel with the existing MII bus accessors within the driver,
however the existing accessors will be removed in subsequent patch.
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Use bit operations provided by bit.h instead of reimplementing them.
No functional change.
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Florian Fainelli
Cc: linux-usb@vger.kernel.org
To: net...@vger.kernel.org
---
drivers/net/usb/smsc95x
Replace the function with genphy_update_link(), since that's really
all that it is.
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Florian Fainelli
Cc: linux-usb@vger.kernel.org
To: net...@vger.kernel.org
---
drivers/net/usb/smsc95xx.c | 1
Replace generic_mii_ioctl() with phydev compatible phy_mii_ioctl().
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Florian Fainelli
Cc: linux-usb@vger.kernel.org
To: net...@vger.kernel.org
---
drivers/net/usb/smsc95xx.c | 3 ++-
1 file cha
The mii_check_media() is called to read out the PHY status registers
and update the internal status reported by mii_ethtool_gset(), just
replace it with phydev compatible phy_read_status().
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Flor
Just replace smsc95xx_mdio_write() with generic phy_write() to reduce
usage of the ad-hoc accessors.
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Florian Fainelli
Cc: linux-usb@vger.kernel.org
To: net...@vger.kernel.org
---
drivers/net/u
This is in fact genphy_restart_aneg(), just use the generic
phydev function.
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Florian Fainelli
Cc: linux-usb@vger.kernel.org
To: net...@vger.kernel.org
---
drivers/net/usb/smsc95xx.c | 5 -
Just replace smsc95xx_mdio_read() with generic phy_read() to reduce
usage of the ad-hoc accessors.
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Florian Fainelli
Cc: linux-usb@vger.kernel.org
To: net...@vger.kernel.org
---
drivers/net/usb
The smsc95xx_reset() is called either during bind or later during
the driver operation. However, the MII structure can be populated
only once, when the smsc95xx_reset() is called from the drivers
bind function.
Split the reset function to allow filling the MII structure only
once. This is done in
These functions are now equal to smsc95xx_{read,write}_reg(),
deduplicate them.
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Florian Fainelli
Cc: linux-usb@vger.kernel.org
To: net...@vger.kernel.org
---
drivers/net/usb/smsc95xx.c | 78 ++
These functions are now equal to smsc95xx_mdio_{read,write}(),
deduplicate them.
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Florian Fainelli
Cc: linux-usb@vger.kernel.org
To: net...@vger.kernel.org
---
drivers/net/usb/smsc95xx.c | 30 +
Inline those functions into smsc95xx_{read,write}_reg() to get
rid of the wrapper.
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Florian Fainelli
Cc: linux-usb@vger.kernel.org
To: net...@vger.kernel.org
---
drivers/net/usb/smsc95xx.c | 32
Inline those functions into smsc95xx_mdio_{read,write}() to get
rid of the wrapper.
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Florian Fainelli
Cc: linux-usb@vger.kernel.org
To: net...@vger.kernel.org
---
drivers/net/usb/smsc95xx.c | 1
In case reading of PHY register fails in smsc95xx_bind(), the private
data allocated earlier are not free()d. Free them before bailing out.
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Florian Fainelli
Cc: linux-usb@vger.kernel.org
To: ne
This series first cleans up the in_pm variable and _nopm() functions,
in preparations for conversion to phy_device instead of ad-hoc PHY
configuration.
This is followed by a registration of an MDIO bus, attaching a PHY
device to it and conversion and cleanup of assorted functions to use
the new PH
The carrier checking code is completely handled by the internal phydev
state machine, remove it.
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Florian Fainelli
Cc: linux-usb@vger.kernel.org
To: net...@vger.kernel.org
---
drivers/net/usb/s
Replace the ad-hoc reimplementation of genphy_soft_reset() and
genphy_config_aneg() with the generic functions.
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Florian Fainelli
Cc: linux-usb@vger.kernel.org
To: net...@vger.kernel.org
---
dr
Add code to detect and connect to PHY. The internal PHY of the SMSC95xx
is a regular SMSC LAN8700 and the driver only supports the internal PHY,
so just use the SMSC PHY driver to configure the PHY. Note that the
driver does a lot of extra configuration of the PHY, which is left in
to avoid breakag
Replace mii_ethtool_gset() with a phydev compatible function and
update the code to match.
Signed-off-by: Marek Vasut
Cc: David S. Miller
Cc: Nisar Sayed
Cc: Woojung Huh
Cc: Andrew Lunn
Cc: Florian Fainelli
Cc: linux-usb@vger.kernel.org
To: net...@vger.kernel.org
---
drivers/net/usb/smsc95x
SMI SM3350 UFS-USB bridge controller cannot handle REQUEST SENSE command
with long sense (96-bytes) well, and will even trap the controller into
a state that refuses to do read/write command.
Currently Linux uncondintionally set US_FL_SANE_SENSE for devices
claiming SPC3+, which makes simply add U
The SMI SM3350 USB-UFS bridge controller cannot handle long sense request
correctly and will make the chip refuse to do read/write when requested
long sense.
Add a bad sense quirk for it.
Signed-off-by: Icenowy Zheng
---
drivers/usb/storage/unusual_devs.h | 12
1 file changed, 12 i
Currently the code will set US_FL_SANE_SENSE flag unconditionally if
device claims SPC3+, however we should allow US_FL_BAD_SENSE flag to
prevent this behavior, because SMI SM3350 UFS-USB bridge controller,
which claims SPC4, will show strange behavior with 96-byte sense
(put the chip into a wrong
On Wed, 2 Jan 2019 13:23:51 +0200
Mathias Nyman wrote:
> On 30.12.2018 18:34, Philip Langdale wrote:
> > This fixes a regression since:
> > 2815ef7fe4d43072b9eda448d04fbc184f2aa513
> >
> > This motherboard is a strange beast, with an Alpine Ridge
> > thunderbolt controller configured to only do
29 matches
Mail list logo
