From: Tao Ren
Fix hardware timeout calculation in aspeed_wdt_set_timeout function to
ensure the reload value does not exceed the hardware limit.
Fixes: efa859f7d786 ("watchdog: Add Aspeed watchdog driver")
Reported-by: Amithash Prasad
Signed-off-by: Tao Ren
---
drivers/watchdog/aspeed_wdt.c
From: Tao Ren
Fix the time comparison (timeout vs. max_hw_heartbeat_ms) in set_timeout
handler to avoid potential integer overflow when the supplied timeout is
greater than aspeed's maximum allowed timeout (4294 seconds).
Fixes: efa859f7d786 ("watchdog: Add Aspeed watchdog driver")
Reported-by:
From: Tao Ren
Fix the time comparison (timeout vs. max_hw_heartbeat_ms) in set_timeout
handler to avoid potential integer overflow when the supplied timeout is
greater than aspeed's maximum allowed timeout (4294 seconds).
Fixes: efa859f7d786 ("watchdog: Add Aspeed watchdog driver")
Reported-by:
From: Tao Ren
Currently the virtual port_dev device is passed to DMA API, and this is
wrong because the device passed to DMA API calls must be the actual
hardware device performing the DMA.
The patch replaces usb_gadget_map_request/usb_gadget_unmap_request APIs
with
From: Tao Ren
Set aspeed-usb vhub port_dev's dma mask to pass the dma_mask test in
"dma_map_page_attrs" function, and the dma_mask test was added in
'commit f959dcd6ddfd ("dma-direct: Fix potential NULL pointer
dereference")'.
Below is the backtrace without the patch:
[<80106550>]
From: Tao Ren
Add hardware monitoring driver for the Maxim MAX127 chip.
MAX127 min/max range handling code is inspired by the max197 driver.
Signed-off-by: Tao Ren
---
Changes in v5:
- fix i2c_transfer() error handling.
Changes in v4:
- delete unnecessary "#include" lines.
-
From: Tao Ren
The patch series adds hardware monitoring driver for the Maxim MAX127
chip.
Patch #1 adds the max127 hardware monitoring driver, and patch #2 adds
documentation for the driver.
Tao Ren (2):
hwmon: (max127) Add Maxim MAX127 hardware monitoring driver
docs: hwmon: Document
From: Tao Ren
Add documentation for the max127 hardware monitoring driver.
Signed-off-by: Tao Ren
Reviewed-by: Guenter Roeck
---
Changes in v5:
- None.
Changes in v4:
- None.
Changes in v3:
- no code change. xdp maintainers were removed from to/cc list.
Changes in v2:
- add
From: Tao Ren
Add hardware monitoring driver for the Maxim MAX127 chip.
MAX127 min/max range handling code is inspired by the max197 driver.
Signed-off-by: Tao Ren
---
Changes in v4:
- delete unnecessary "#include" lines.
- simplify i2c_transfer() error handling.
- add mutex to
From: Tao Ren
Add documentation for the max127 hardware monitoring driver.
Signed-off-by: Tao Ren
Reviewed-by: Guenter Roeck
---
Changes in v4:
- None.
Changes in v3:
- no code change. xdp maintainers were removed from to/cc list.
Changes in v2:
- add more description for min/max
From: Tao Ren
The patch series adds hardware monitoring driver for the Maxim MAX127
chip.
Patch #1 adds the max127 hardware monitoring driver, and patch #2 adds
documentation for the driver.
Tao Ren (2):
hwmon: (max127) Add Maxim MAX127 hardware monitoring driver
docs: hwmon: Document
From: Tao Ren
Add documentation for the max127 hardware monitoring driver.
Signed-off-by: Tao Ren
---
Changes in v3:
- no code change. xdp maintainers were removed from to/cc list.
Changes in v2:
- add more description for min/max sysfs nodes.
- convert values from volt to millivolt
From: Tao Ren
Add hardware monitoring driver for the Maxim MAX127 chip.
MAX127 min/max range handling code is inspired by the max197 driver.
Signed-off-by: Tao Ren
---
Changes in v3:
- no code change. xdp maintainers were removed from to/cc list.
Changes in v2:
- replace
From: Tao Ren
The patch series adds hardware monitoring driver for the Maxim MAX127
chip.
Patch #1 adds the max127 hardware monitoring driver, and patch #2 adds
documentation for the driver.
Resending the patch series (v3) with XDP maintainers removed from to/cc
list to reduce noise.
Tao Ren
From: Tao Ren
Add documentation for the max127 hardware monitoring driver.
Signed-off-by: Tao Ren
---
Changes in v2:
- add more description for min/max sysfs nodes.
- convert values from volt to millivolt in the document.
Documentation/hwmon/index.rst | 1 +
From: Tao Ren
Add hardware monitoring driver for the Maxim MAX127 chip.
MAX127 min/max range handling code is inspired by the max197 driver.
Signed-off-by: Tao Ren
---
Changes in v2:
- replace devm_hwmon_device_register_with_groups() with
devm_hwmon_device_register_with_info() API.
From: Tao Ren
The patch series adds hardware monitoring driver for the Maxim MAX127
chip.
Patch #1 adds the max127 hardware monitoring driver, and patch #2 adds
documentation for the driver.
Tao Ren (2):
hwmon: (max127) Add Maxim MAX127 hardware monitoring driver
docs: hwmon: Document
From: Tao Ren
Add documentation for max127 hardware monitoring driver.
Signed-off-by: Tao Ren
---
Documentation/hwmon/index.rst | 1 +
Documentation/hwmon/max127.rst | 43 ++
2 files changed, 44 insertions(+)
create mode 100644 Documentation/hwmon/max127.rst
From: Tao Ren
The patch series adds hardware monitoring driver for the Maxim MAX127
chip.
Patch #1 adds the max127 hardware monitoring driver, and patch #2 adds
documentation for the driver.
Tao Ren (2):
hwmon: (max127) Add Maxim MAX127 hardware monitoring driver
docs: hwmon: Document
From: Tao Ren
Add hardware monitoring driver for the Maxim MAX127 chip.
MAX127 min/max range handling code is inspired by the max197 driver.
Signed-off-by: Tao Ren
---
drivers/hwmon/Kconfig | 9 ++
drivers/hwmon/Makefile | 1 +
drivers/hwmon/max127.c | 286
From: Tao Ren
Simplify the Wedge40 device tree by using the common dtsi.
Signed-off-by: Tao Ren
---
.../boot/dts/aspeed-bmc-facebook-wedge40.dts | 112 +-
1 file changed, 1 insertion(+), 111 deletions(-)
diff --git a/arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts
From: Tao Ren
Simplify the Wedge100 device tree by using the common dtsi.
In addition this enables the second firmware flash, and turns on the
"i2c-mux-idle-disconnect" flag for I2C switch 7-0070.
Signed-off-by: Tao Ren
---
.../boot/dts/aspeed-bmc-facebook-wedge100.dts | 120
From: Tao Ren
This common descirption is included by all Facebook AST2400 Network BMC
platforms to minimize duplicated device entries across Facebook Network
BMC device trees.
Signed-off-by: Tao Ren
---
.../dts/ast2400-facebook-netbmc-common.dtsi | 117 ++
1 file changed,
From: Tao Ren
Add initial version of device tree for Facebook Galaxy100 (AST2400) BMC.
Signed-off-by: Tao Ren
---
arch/arm/boot/dts/Makefile| 1 +
.../dts/aspeed-bmc-facebook-galaxy100.dts | 57 +++
2 files changed, 58 insertions(+)
create mode 100644
From: Tao Ren
The patch series adds the initial version of device tree for Facebook
Galaxy100 (AST2400) BMC.
Patch #1 adds common dtsi to minimize duplicated device entries across
Facebook Network AST2400 BMC device trees.
Patch #2 simplfies Wedge40 device tree by using the common dtsi.
Patch
From: Tao Ren
Create all the i2c switches in device tree and use aliases to assign
child channels with consistent bus numbers.
Besides, "i2c-mux-idle-disconnect" is set for all the i2c switches to
avoid potential conflicts when multiple devices (beind the switches) use
the same device address.
From: Tao Ren
Update "data0" partition's size from 8MB to 4MB to fix "partition data0
extends beyond the end of device" warning at bootup time.
Signed-off-by: Tao Ren
---
arch/arm/boot/dts/aspeed-bmc-facebook-wedge400.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Tao Ren
GPIO_U is mapped to the least significant byte of input/output mask, and
the byte in "output" mask should be 0 because GPIO_U is input only. All
the other bits need to be 1 because GPIO_V/W/X support both input and
output modes.
Similarly, GPIO_Y/Z are mapped to the 2 least
From: Tao Ren
Remove FMC flash layout from ast2500-facebook-netbmc-common.dtsi because
flash size and layout varies across different Facebook AST2500 OpenBMC
platforms.
Signed-off-by: Tao Ren
---
.../boot/dts/ast2500-facebook-netbmc-common.dtsi| 13 -
1 file changed, 13
From: Tao Ren
Set 32MB FMC flash layout in CMM device tree explicitly because the flash
layout settings were removed from "ast2500-facebook-netbmc-common.dtsi".
Signed-off-by: Tao Ren
---
arch/arm/boot/dts/aspeed-bmc-facebook-cmm.dts | 17 +
1 file changed, 17 insertions(+)
From: Tao Ren
The patch series adds Facebook Wedge400 (AST2500) BMC device tree, and
FMC flash layout is re-structured because flash size and layout varies
across different Facebook AST2500 OpenBMC platforms.
Patch #1 removes flash layout from ast2500-facebook-netbmc-common.dtsi
because now we
From: Tao Ren
Set 64Mb FMC flash layout in Minipack device tree explicitly because the
flash layout was removed from "ast2500-facebook-netbmc-common.dtsi".
Please note "data0" partition' size is updated to 4MB to be consistent
with other Facebook OpenBMC platforms.
Signed-off-by: Tao Ren
---
From: Tao Ren
Set 32MB FMC flash layout in Yamp device tree explicitly because flash
layout settings were removed from "ast2500-facebook-netbmc-common.dtsi".
Signed-off-by: Tao Ren
---
arch/arm/boot/dts/aspeed-bmc-facebook-yamp.dts | 17 +
1 file changed, 17 insertions(+)
From: Tao Ren
Add initial version of device tree for Facebook Wedge400 (AST2500) BMC.
Signed-off-by: Tao Ren
---
arch/arm/boot/dts/Makefile| 1 +
.../boot/dts/aspeed-bmc-facebook-wedge400.dts | 420 ++
2 files changed, 421 insertions(+)
create mode
From: Tao Ren
Update FMC flash0's label to "spi0.0" so it's consistent with all the
other Facebook OpenBMC platforms.
Signed-off-by: Tao Ren
---
arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Tao Ren
Enable UART4's NRTS4 (A19) pin because the pin is used for RS485
software emulation.
Signed-off-by: Tao Ren
---
arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
From: Tao Ren
This patch series fixes a few nits in wedge40 device tree.
Patch #1 updates FMC flash label so it's consistent with other Facebook
OpenBMC platforms.
Patch #2 updates UART4 pin settings for the purpose of RS485 software
emulation.
Tao Ren (2):
ARM: dts: aspeed: wedge40: Update
From: Tao Ren
Create all the i2c switches in device tree and use aliases to assign
child channels with consistent bus numbers.
Besides, "i2c-mux-idle-disconnect" is set for all the i2c switches to
avoid potential conflicts when multiple devices (beind the switches)
use the same device address.
From: Tao Ren
The patch series update several devices' settings in Facebook Wedge40
device tree.
Patch #1 disables a few i2c controllers as they are not being used at
present.
Patch #2 enables adc device for voltage monitoring.
Patch #3 enables pwm_tacho device for fan control and monitoring.
From: Tao Ren
Enable pwm_tacho device for fan control and monitoring in Wedge40.
Signed-off-by: Tao Ren
---
Changes in v2:
- Nothing changed. Resending the patch just in case the previous
email was not delivered.
.../boot/dts/aspeed-bmc-facebook-wedge40.dts | 29 +++
From: Tao Ren
Disable i2c bus #9, #10 and #13 as these i2c controllers are not used on
Wedge40.
Signed-off-by: Tao Ren
---
Changes in v2:
- Nothing changed. Resending the patch just in case the previous
email was not delivered.
arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts | 12
From: Tao Ren
Enable adc controller and corresponding voltage sensoring channels for
Wedge40.
Signed-off-by: Tao Ren
---
Changes in v2:
- Nothing changed. Resending the patch just in case the previous
email was not delivered.
arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts | 9
From: Tao Ren
Fix a typo in SENSORS_IR35221 option: module name should be "ir35221"
instead of "ir35521".
Fixes: 8991ebd9c9a6 ("hwmon: (pmbus) Add client driver for IR35221")
Cc: Samuel Mendoza-Jonas
Signed-off-by: Tao Ren
---
drivers/hwmon/pmbus/Kconfig | 2 +-
1 file changed, 1
From: Tao Ren
Create all the i2c switches in device tree and use aliases to assign
child channels with consistent bus numbers.
Besides, "i2c-mux-idle-disconnect" is set for all the i2c switches to
avoid potential conflicts when multiple devices (beind the switches)
use the same device address.
From: Tao Ren
Enable adc controller and corresponding voltage sensoring channels for
Wedge40.
Signed-off-by: Tao Ren
---
arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts
From: Tao Ren
Disable i2c bus #9, #10 and #13 as these i2c controllers are not used on
Wedge40.
Signed-off-by: Tao Ren
---
arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts | 12
1 file changed, 12 deletions(-)
diff --git a/arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts
From: Tao Ren
Enable pwm_tacho device for fan control and monitoring in Wedge40.
Signed-off-by: Tao Ren
---
.../boot/dts/aspeed-bmc-facebook-wedge40.dts | 29 +++
1 file changed, 29 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts
From: Tao Ren
The patch series update several devices' settings in Facebook Wedge40
device tree.
Patch #1 disables a few i2c controllers as they are not being used at
present.
Patch #2 enables adc device for voltage monitoring.
Patch #3 enables pwm_tacho device for fan control and monitoring.
From: Tao Ren
Replace assignment "=" with OR "|=" for "phy->dev_flags" so "dev_flags"
configured in phy probe() function can be preserved.
The idea is similar to commit e7312efbd5de ("net: phy: modify assignment
to OR for dev_flags in phy_attach_direct").
Signed-off-by: Tao Ren
---
From: Tao Ren
This is a follow-on patch for commit a23be4ed8f48 ("usb: gadget: aspeed:
improve vhub port irq handling"): for_each_set_bit() is replaced with
simple for() loop because for() loop runs faster on ASPEED BMC.
Signed-off-by: Tao Ren
---
drivers/usb/gadget/udc/aspeed-vhub/core.c |
From: Heiner Kallweit
This patch adds support for clause 37 1000Base-X auto-negotiation.
Signed-off-by: Heiner Kallweit
Signed-off-by: Tao Ren
Tested-by: René van Dorst
Reviewed-by: Andrew Lunn
---
No change in v9/v10.
Changes in v8:
- Rebased the patch on top of net-next HEAD.
Changes
From: Tao Ren
Modify the assignment to OR when dealing with phydev->dev_flags in
phy_attach_direct function, and this is to make sure dev_flags set in
driver's probe callback won't be lost.
Suggested-by: Andrew Lunn
CC: Heiner Kallweit
CC: Vladimir Oltean
Signed-off-by: Tao Ren
Reviewed-by:
From: Tao Ren
The BCM54616S PHY cannot work properly in RGMII->1000Base-X mode, mainly
because genphy functions are designed for copper links, and 1000Base-X
(clause 37) auto negotiation needs to be handled differently.
This patch enables 1000Base-X support for BCM54616S by customizing 3
driver
From: Tao Ren
This patch series aims at supporting auto negotiation when BCM54616S is
running in 1000Base-X mode: without the patch series, BCM54616S PHY driver
would report incorrect link speed in 1000Base-X mode.
Patch #1 (of 3) modifies assignment to OR when dealing with dev_flags in
54 matches
Mail list logo
