The currently interrupts are configured after the channel was enabled.
Signed-off-by: Andrew Jeffery
Reviewed-by: Joel Stanley
Reviewed-by: Haiyue Wang
---
drivers/char/ipmi/kcs_bmc_aspeed.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/char/ipmi/kcs_bmc_as
The v2 bindings allow us to extract the resources from the devicetree.
The table in the driver is retained to derive the channel index, which
removes the need for kcs_chan property from the v1 bindings. The v2
bindings allow us to reduce the number of warnings generated by the
existing devicetree n
Hello,
This is a short series reworking the devicetree binding and driver for the
ASPEED BMC KCS devices. With the number of supported ASPEED BMC devicetrees the
changes enable removal of more than 100 lines of warning output from dtc.
These changes are extracted from an RFC series posted previou
The v2 binding utilises reg and renames some of the v1 properties.
Signed-off-by: Andrew Jeffery
---
Documentation/devicetree/bindings/ipmi/aspeed-kcs-bmc.txt | 20 +---
1 file changed, 14 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/ipmi/aspeed-kcs-bmc.txt
On Tue, Dec 03, 2019 at 11:08:24PM +1030, Andrew Jeffery wrote:
> The currently interrupts are configured after the channel was enabled.
How about:
The interrupts were configured after the channel was enabled, configure
them before so they will work.
-corey
>
> Signed-off-by: Andrew Jeffery
>
On Tue, Dec 3, 2019 at 6:36 AM Andrew Jeffery wrote:
>
> The v2 binding utilises reg and renames some of the v1 properties.
>
> Signed-off-by: Andrew Jeffery
> ---
> Documentation/devicetree/bindings/ipmi/aspeed-kcs-bmc.txt | 20 +---
> 1 file changed, 14 insertions(+), 6 deletions(-)
>
> di
