Add the proximity rate optional option and handling of it for
vishay vcnl3020.
Signed-off-by: Ivan Mikhaylov
---
drivers/iio/proximity/vcnl3020.c | 97 +++-
1 file changed, 96 insertions(+), 1 deletion(-)
diff --git a/drivers/iio/proximity/vcnl3020.c b/drivers/iio
Add the runtime control of proximity rate for vcnl3020 proximity
sensor.
Changes from v1:
1. add .read_avail method
2. remove dts and parse of it
Ivan Mikhaylov (1):
iio: proximity: vcnl3020: add proximity rate
drivers/iio/proximity/vcnl3020.c | 97 +++-
1
On Sun, 2021-02-21 at 22:34 +0200, Andy Shevchenko wrote:
>
>
> On Tuesday, February 16, 2021, Ivan Mikhaylov wrote:
> > Add the proximity rate optional option and handling of it for
> > vishay vcnl3020.
> >
> > Signed-off-by: Ivan Mikhaylov
> > ---
>
On Sun, 2021-02-21 at 15:20 +, Jonathan Cameron wrote:
> On Tue, 16 Feb 2021 17:53:45 +0300
> Ivan Mikhaylov wrote:
>
> > Add the proximity rate optional option and handling of it for
> > vishay vcnl3020.
> >
> > Signed-off-by: Ivan Mikhaylov
> Hi Ivan,
Describe the possible proximity values in herzes for vcnl3020.
Signed-off-by: Ivan Mikhaylov
---
.../devicetree/bindings/iio/proximity/vishay,vcnl3020.yaml | 6 ++
1 file changed, 6 insertions(+)
diff --git
a/Documentation/devicetree/bindings/iio/proximity/vishay,vcnl3020.yaml
b
Add the proximity rate optional option and handling of it for
vishay vcnl3020.
Signed-off-by: Ivan Mikhaylov
---
drivers/iio/proximity/vcnl3020.c | 123 ++-
1 file changed, 120 insertions(+), 3 deletions(-)
diff --git a/drivers/iio/proximity/vcnl3020.c b/drivers/iio
Add the control of proximity rate from runtime and DTS for vcnl3020
proximity sensor.
Ivan Mikhaylov (2):
iio: proximity: vcnl3020: add proximity rate
dt-bindings: vcnl3020: add proximity rate in hz
.../iio/proximity/vishay,vcnl3020.yaml| 6 +
drivers/iio/proximity/vcnl3020.c
e properly?
Ivan Mikhaylov (2):
net: phy: micrel: add LED control on KSZ9131
dt-bindings: net: phy: micrel: add LED mode behavior and select
properties
.../devicetree/bindings/net/micrel.txt| 7 ++
drivers/net/phy/micrel.c | 69 ++-
2 files c
Add LED mode behavior and LED mode select properties which can be used
in KSZ9131 PHY.
Signed-off-by: Ivan Mikhaylov
---
Documentation/devicetree/bindings/net/micrel.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/micrel.txt
b/Documentation
Add the possibility to read the LED configuration via DTS properties from
KSZ9131 PHY node. Add the new proprties and handle for them:
micrel,led-mode-behavior
micrel,led-mode-select
Signed-off-by: Ivan Mikhaylov
---
drivers/net/phy/micrel.c | 69 +++-
1 file
t label.
3. split ftgmac100_destroy_mdio into ftgmac100_phy_disconnect and
ftgmac100_destroy_mdio.
4. remove unneeded mdio_np checks.
Changes from v1:
1. split one patch into two.
Ivan Mikhaylov (3):
net: ftgmac100: move phy connect out from ftgmac100_setup_mdio
net: ftgmac100: add handling of md
phy-handle can't be handled well for ast2400/2500 which has an embedded
MDIO controller. Add ftgmac100_mdio_setup for ast2400/2500 and initialize
PHYs from mdio child node with of_mdiobus_register.
Signed-off-by: Ivan Mikhaylov
---
drivers/net/ethernet/faraday/ftgmac100.c
Split MDIO registration and PHY connect into ftgmac100_setup_mdio and
ftgmac100_mii_probe.
Reviewed-by: Andrew Lunn
Signed-off-by: Ivan Mikhaylov
---
drivers/net/ethernet/faraday/ftgmac100.c | 104 ---
1 file changed, 54 insertions(+), 50 deletions(-)
diff --git a/drivers
Add the phy-handle and MDIO description and add the example with
PHY and MDIO nodes.
Signed-off-by: Ivan Mikhaylov
---
.../devicetree/bindings/net/ftgmac100.txt | 25 +++
1 file changed, 25 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/ftgmac100.txt
b
On Tue, 2020-10-27 at 19:23 +0100, Andrew Lunn wrote:
> On Tue, Oct 27, 2020 at 05:49:24PM +0300, Ivan Mikhaylov wrote:
> > phy-handle can't be handled well for ast2400/2500 which has an embedded
> > MDIO controller. Add ftgmac100_mdio_setup for ast2400/2500 and initialize
>
unneeded mdio_np checks.
Changes from v1:
1. split one patch into two.
Ivan Mikhaylov (2):
net: ftgmac100: move phy connect out from ftgmac100_setup_mdio
net: ftgmac100: add handling of mdio/phy nodes for ast2400/2500
drivers/net/ethernet/faraday/ftgmac100.c | 122 +--
phy-handle can't be handled well for ast2400/2500 which has an embedded
MDIO controller. Add ftgmac100_mdio_setup for ast2400/2500 and initialize
PHYs from mdio child node with of_mdiobus_register.
Signed-off-by: Ivan Mikhaylov
---
drivers/net/ethernet/faraday/ftgmac100.c
Split MDIO registration and PHY connect into ftgmac100_setup_mdio and
ftgmac100_mii_probe.
Signed-off-by: Ivan Mikhaylov
---
drivers/net/ethernet/faraday/ftgmac100.c | 104 ---
1 file changed, 54 insertions(+), 50 deletions(-)
diff --git a/drivers/net/ethernet/faraday
phy-handle can't be handled well for ast2400/2500 which has an embedded
MDIO controller. Add ftgmac100_mdio_setup for ast2400/2500 and initialize
PHYs from mdio child node with of_mdiobus_register.
Signed-off-by: Ivan Mikhaylov
---
drivers/net/ethernet/faraday/ftgmac100.c
Split MDIO registration and PHY connect into ftgmac100_setup_mdio and
ftgmac100_mii_probe.
Signed-off-by: Ivan Mikhaylov
---
drivers/net/ethernet/faraday/ftgmac100.c | 92
1 file changed, 47 insertions(+), 45 deletions(-)
diff --git a/drivers/net/ethernet/faraday
#address-cells = <1>;
#size-cells = <0>;
phy: ethernet-phy@0 {
compatible = "ethernet-phy-id.";
reg = <0>;
};
};
};
The patch fixes it and gets possible PHYs a
On Wed, 2020-10-14 at 05:23 +, Joel Stanley wrote:
> Hi Ivan,
>
> On Tue, 13 Oct 2020 at 12:38, Ivan Mikhaylov wrote:
> > phy-handle can't be handled well for ast2400/2500 which has an embedded
> > MDIO controller. Add ftgmac100_mdio_setup for ast2400/2500 and ini
phy-handle can't be handled well for ast2400/2500 which has an embedded
MDIO controller. Add ftgmac100_mdio_setup for ast2400/2500 and initialize
PHYs from mdio child node with of_mdiobus_register.
Signed-off-by: Ivan Mikhaylov
---
drivers/net/ethernet/faraday/ftgmac100.c
#address-cells = <1>;
#size-cells = <0>;
phy: ethernet-phy@0 {
compatible = "ethernet-phy-id.";
reg = <0>;
};
};
};
The patch fixes it and gets possible PHYs a
On Wed, 2020-09-30 at 19:30 +0530, Vignesh Raghavendra wrote:
>
> On 9/30/20 6:37 PM, Ivan Mikhaylov wrote:
> > On Wed, 2020-09-30 at 15:06 +0530, Vignesh Raghavendra wrote:
> > > On 9/21/20 4:54 PM, Ivan Mikhaylov wrote:
> > > > Some chips like macronix do
On Wed, 2020-09-30 at 15:10 +0530, Vignesh Raghavendra wrote:
> Hi,
>
> On 9/21/20 4:54 PM, Ivan Mikhaylov wrote:
> > Add locks for whole macronix chip series with BP0-2 and BP0-3 bits.
> >
> > Tested with mx25l51245g(BP0-3).
>
> Since you have only tested o
On Wed, 2020-09-30 at 15:06 +0530, Vignesh Raghavendra wrote:
>
> On 9/21/20 4:54 PM, Ivan Mikhaylov wrote:
> > Some chips like macronix don't have TB(Top/Bottom protection)
> > bit in the status register. Do not write tb_mask inside status
> > register, unless SPI_
Add locks for whole macronix chip series with BP0-2 and BP0-3 bits.
Tested with mx25l51245g(BP0-3).
Signed-off-by: Ivan Mikhaylov
---
drivers/mtd/spi-nor/macronix.c | 75 ++
1 file changed, 50 insertions(+), 25 deletions(-)
diff --git a/drivers/mtd/spi-nor
Some chips like macronix don't have TB(Top/Bottom protection)
bit in the status register. Do not write tb_mask inside status
register, unless SPI_NOR_HAS_TB is present for the chip.
Signed-off-by: Ivan Mikhaylov
---
drivers/mtd/spi-nor/core.c | 22 --
1 file change
TB(Top/Bottom protection bit) is not present in the status register for
macronix chips, do not touch TB bit in status register in this case.
Enable lock interface for most of macronix chips which are suitable for it.
Tested only mx25l51245g (BP0-3).
Ivan Mikhaylov (2):
mtd: spi-nor: do not
On Thu, 2020-09-03 at 13:13 +0200, Christophe Leroy wrote:
> You want to start the watchdog just before calling 'reboot' but want to
> make sure that the watchdog will not reset the board before all
> userspace has shut down correctly ?
Yes, just for an example, in the nature exists some aspeed
On Wed, 2020-09-02 at 06:36 -0700, Guenter Roeck wrote:
> On 9/2/20 6:02 AM, Ivan Mikhaylov wrote:
> > Hello everyone. Currently, the watchdog interface only has "stop watchdog on
> > restart" but lacks a "start watchdog on restart" one. Is there a way to
On Wed, 2020-09-02 at 15:19 +0200, Christophe Leroy wrote:
> Isn't it the default expected behaviour for a watchdog ?
It depends on hardware and system requirements. You may have not just one
watchdog device.
> "stop watchdog on restart" is there to keep things under control during
> a wanted
Hello everyone. Currently, the watchdog interface only has "stop watchdog on
restart" but lacks a "start watchdog on restart" one. Is there a way to achieve
such functionality?
I'd like to know why "stop watchdog on restart" wasn't implemented via ioctl
interface? It would be more convenient from
On Mon, 2020-08-31 at 12:55 +0200, Rasmus Villemoes wrote:
> On 12/08/2020 17.18, Ivan Mikhaylov wrote:
> > Add locks for whole macronix chip series with BP0-2 and BP0-3 bits.
> >
> > Tested with mx25l51245g(BP0-3).
>
> Hmm. I've tried adding support for locking o
On Wed, 2020-08-12 at 18:18 +0300, Ivan Mikhaylov wrote:
> TB(Top/Bottome protection bit) is not present in the status register for
> macronix chips, do not touch TB bit in status register in this case.
> Enable lock interface for most of macronix chips which are suitable for it.
>
&
TB(Top/Bottome protection bit) is not present in the status register for
macronix chips, do not touch TB bit in status register in this case.
Enable lock interface for most of macronix chips which are suitable for it.
Tested only mx25l51245g (BP0-3).
Ivan Mikhaylov (2):
mtd: spi-nor: do not
Some chips like macronix don't have TB(Top/Bottom protection)
bit in the status register. Do not write tb_mask inside status
register, unless SPI_NOR_HAS_TB is present for the chip.
Signed-off-by: Ivan Mikhaylov
---
drivers/mtd/spi-nor/core.c | 22 --
1 file change
Add locks for whole macronix chip series with BP0-2 and BP0-3 bits.
Tested with mx25l51245g(BP0-3).
Signed-off-by: Ivan Mikhaylov
---
drivers/mtd/spi-nor/macronix.c | 75 ++
1 file changed, 50 insertions(+), 25 deletions(-)
diff --git a/drivers/mtd/spi-nor
processing IC and features standard I2C communication
interface. It features an interrupt function.
Datasheet: http://www.vishay.com/docs/84150/vcnl3020.pdf
Signed-off-by: Ivan Mikhaylov
Reviewed-by: Andy Shevchenko
---
drivers/iio/proximity/Kconfig| 11 ++
drivers/iio/proximity/Makefile | 1
e_new.
3. s32/int32_t -> int
Ivan Mikhaylov (2):
dt-bindings: proximity: provide vcnl3020 device tree binding document
iio: proximity: Add driver support for vcnl3020 proximity sensor
.../iio/proximity/vishay,vcnl3020.yaml| 62 +
drivers/iio/proximity/Kconfig |
Mostly standard i2c driver with some additional led-current option
for vcnl3020.
Signed-off-by: Ivan Mikhaylov
---
.../iio/proximity/vishay,vcnl3020.yaml| 62 +++
1 file changed, 62 insertions(+)
create mode 100644
Documentation/devicetree/bindings/iio/proximity/vishay
On Fri, 2020-05-08 at 15:51 +0100, Jonathan Cameron wrote:
> On Thu, 7 May 2020 16:25:59 +0300
> Ivan Mikhaylov wrote:
>
> > Mostly standard i2c driver with some additional led-current option
> > for vcnl3020.
> >
> > Signed-off-by: Ivan Mikhaylov
> > ---
e in measurement
function.
2. change struct i2client* in vcnl3020_data to struct dev*
3. enable REGMAP_I2C in Kconfig
Changes from v1:
1. using regmap interface instead of i2c_smbus_* calls.
2. switch from probe to probe_new.
3. s32/int32_t -> int
Ivan Mikhaylov (2):
dt-
processing IC and features standard I2C communication
interface. It features an interrupt function.
Datasheet: http://www.vishay.com/docs/84150/vcnl3020.pdf
Signed-off-by: Ivan Mikhaylov
Reviewed-by: Andy Shevchenko
---
drivers/iio/proximity/Kconfig| 11 ++
drivers/iio/proximity/Makefile | 1
Mostly standard i2c driver with some additional led-current option
for vcnl3020.
Signed-off-by: Ivan Mikhaylov
---
.../iio/proximity/vishay,vcnl3020.yaml| 65 +++
1 file changed, 65 insertions(+)
create mode 100644
Documentation/devicetree/bindings/iio/proximity/vishay
Mostly standard i2c driver with some additional led-current option
for vcnl3020.
Signed-off-by: Ivan Mikhaylov
---
.../iio/proximity/vishay,vcnl3020.yaml| 65 +++
1 file changed, 65 insertions(+)
create mode 100644
Documentation/devicetree/bindings/iio/proximity/vishay
in vcnl3020_data to struct dev*
3. enable REGMAP_I2C in Kconfig
Changes from v1:
1. using regmap interface instead of i2c_smbus_* calls.
2. switch from probe to probe_new.
3. s32/int32_t -> int
Ivan Mikhaylov (2):
dt-bindings: proximity: provide vcnl3020 device tree binding docume
processing IC and features standard I2C communication
interface. It features an interrupt function.
Datasheet: http://www.vishay.com/docs/84150/vcnl3020.pdf
Signed-off-by: Ivan Mikhaylov
Reviewed-by: Andy Shevchenko
---
drivers/iio/proximity/Kconfig| 11 ++
drivers/iio/proximity/Makefile | 1
On Sun, 2020-04-26 at 10:34 +0100, Jonathan Cameron wrote:
> On Wed, 22 Apr 2020 19:05:08 +0300
> Ivan Mikhaylov wrote:
>
> > Mostly standard i2c driver with some additional led-current option
> > for vcnl3020.
> >
> > Signed-off-by: Ivan Mikhaylov
> Hm. I
would be
re-directed to CS1#. And CS0# is not accessible under this mode. To access
CS0#, firmware should clear the 2nd boot mode register in the WDT2 status
register WDT30.bit[1]."
Signed-off-by: Ivan Mikhaylov
---
drivers/watchdog/aspeed_wdt.c | 65 ++-
1 fi
Adds wdt2 section with 'alt-boot' option into dts for vesnin.
Signed-off-by: Ivan Mikhaylov
---
arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
b/arch/arm/boot/dts/aspeed-bmc-opp-vesnin
The option for the ast2400/2500 to get access to CS0 at runtime.
Signed-off-by: Ivan Mikhaylov
---
.../ABI/testing/sysfs-class-watchdog | 34 +++
1 file changed, 34 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-class-watchdog
b/Documentation/ABI/testing
Adds secondary SPI flash chip into dts for vesnin.
Signed-off-by: Ivan Mikhaylov
---
arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
b/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
index
ess to the primary flash chip in order
to allow for recovery of its contents.
Ivan Mikhaylov (4):
vesnin: add wdt2 section with alt-boot option
vesnin: add secondary SPI flash chip
watchdog/aspeed: add support for dual boot
aspeed/watchdog: Add access_cs0 option for alt-boot
.../ABI/tes
Adds wdt2 section with 'alt-boot' option into dts for vesnin.
Signed-off-by: Ivan Mikhaylov
---
arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
b/arch/arm/boot/dts/aspeed-bmc-opp-vesnin
would be
re-directed to CS1#. And CS0# is not accessable under this mode. To access
CS0#, firmware should clear the 2nd boot mode register in the WDT2 status
register WDT30.bit[1]."
Signed-off-by: Ivan Mikhaylov
---
drivers/watchdog/aspeed_wdt.c | 65 ++-
1 fi
Adds secondary SPI flash chip into dts for vesnin.
Signed-off-by: Ivan Mikhaylov
---
arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
b/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
index
The option for the ast2400/2500 to get access to CS0 at runtime.
Signed-off-by: Ivan Mikhaylov
---
.../ABI/testing/sysfs-class-watchdog | 34 +++
1 file changed, 34 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-class-watchdog
b/Documentation/ABI/testing
ess to the primary flash chip in order
to allow for recovery of its contents.
Ivan Mikhaylov (4):
vesnin: add wdt2 section with alt-boot option
vesnin: add secondary SPI flash chip
watchdog/aspeed: add support for dual boot
aspeed/watchdog: Add access_cs0 option for alt-boot
.../ABI/tes
On Mon, 2019-08-26 at 17:14 -0700, Guenter Roeck wrote:
> > +/*
> > + * At alternate side the 'access_cs0' sysfs node provides:
> > + * ast2400: a way to get access to the primary SPI flash chip at CS0
> > + *after booting from the alternate chip at CS1.
> > + * ast2500: a way to re
Adds secondary SPI flash chip into dts for vesnin.
Signed-off-by: Ivan Mikhaylov
---
arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
b/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
index
ess to the primary flash chip in order
to allow for recovery of its contents.
Ivan Mikhaylov (4):
vesnin: add wdt2 section with alt-boot option
vesnin: add secondary SPI flash chip
watchdog/aspeed: add support for dual boot
dt-bindings/watchdog: Add access_cs0 option for alt-boot
..
Adds wdt2 section with 'alt-boot' option into dts for vesnin.
Signed-off-by: Ivan Mikhaylov
---
arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
b/arch/arm/boot/dts/aspeed-bmc-opp-vesnin
would be
re-directed to CS1#. And CS0# is not accessable under this mode. To access
CS0#, firmware should clear the 2nd boot mode register in the WDT2 status
register WDT30.bit[1]."
Signed-off-by: Ivan Mikhaylov
---
drivers/watchdog/aspeed_wdt.c | 62 ++-
1 fi
The option for the ast2400/2500 to get access to CS0 at runtime.
Signed-off-by: Ivan Mikhaylov
---
Documentation/devicetree/bindings/watchdog/aspeed-wdt.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/watchdog/aspeed-wdt.txt
b/Documentation
On Fri, 2019-08-23 at 07:19 -0700, Guenter Roeck wrote:
> >
> > +/* access_cs0 shows if cs0 is accessible, hence the reverted bit */
> > +static ssize_t access_cs0_show(struct device *dev,
> > + struct device_attribute *attr, char *buf)
> > +{
> > + struct aspeed_wdt *wdt = dev_get_dr
would be
re-directed to CS1#. And CS0# is not accessable under this mode. To access
CS0#, firmware should clear the 2nd boot mode register in the WDT2 status
register WDT30.bit[1]."
Signed-off-by: Ivan Mikhaylov
---
drivers/watchdog/aspeed_wdt.c | 44 ++-
1 fi
Adds secondary SPI flash chip into dts for vesnin.
Signed-off-by: Ivan Mikhaylov
---
arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
b/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
index
Adds wdt2 section with 'alt-boot' option into dts for vesnin.
Signed-off-by: Ivan Mikhaylov
---
arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
b/arch/arm/boot/dts/aspeed-bmc-opp-vesnin
ess to the primary flash chip in order
to allow for recovery of its contents.
Ivan Mikhaylov (3):
vesnin: add wdt2 section with alt-boot option
vesnin: add secondary SPI flash chip
watchdog/aspeed: add support for dual boot
arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts | 12 +
driver
On Thu, 2019-08-22 at 06:55 -0700, Guenter Roeck wrote:
> On Thu, Aug 22, 2019 at 12:15:20PM +0300, Ivan Mikhaylov wrote:
> > On Wed, 2019-08-21 at 09:32 -0700, Guenter Roeck wrote:
> > > > + writel(WDT_CLEAR_TIMEOUT_AND_BOOT_CODE_SELECTION,
> > > >
On Wed, 2019-08-21 at 09:32 -0700, Guenter Roeck wrote:
>
> > + writel(WDT_CLEAR_TIMEOUT_AND_BOOT_CODE_SELECTION,
> > + wdt->base + WDT_CLEAR_TIMEOUT_STATUS);
> > + wdt->wdd.bootstatus |= WDIOF_EXTERN1;
>
> The variable reflects the _boot status_. It should not change after
would be
re-directed to CS1#. And CS0# is not accessable under this mode. To access
CS0#, firmware should clear the 2nd boot mode register in the WDT2 status
register WDT30.bit[1]."
Signed-off-by: Ivan Mikhaylov
---
drivers/watchdog/aspeed_wdt.c | 30 ++
1 file c
Adds secondary SPI flash chip into dts for vesnin.
Signed-off-by: Ivan Mikhaylov
---
arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
b/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
index
Adds wdt2 section with 'alt-boot' option into dts for vesnin.
Signed-off-by: Ivan Mikhaylov
---
arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
b/arch/arm/boot/dts/aspeed-bmc-opp-vesnin
ess to the primary flash chip in order
to allow for recovery of its contents.
Ivan Mikhaylov (3):
vesnin: add wdt2 section with alt-boot option
vesnin: add secondary SPI flash chip
watchdog/aspeed: add support for dual boot
arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts | 12 +
driver
>From 1687adb615ceb7a4013712604f177dc906059667 Mon Sep 17 00:00:00 2001
From: Ivan Mikhaylov
Date: Wed, 21 Aug 2019 18:21:05 +
Subject: [PATCH 0/3] add dual-boot support
ASPEED SoCs support dual-boot feature for SPI Flash.
When strapped appropriately, the SoC starts wdt2 (/dev/watchdog1)
and
emac4syn chips has availability to use 8192 rx/tx fifo buffer sizes,
in current state if we set it up in dts 8192 as example, we will get
only 2048 which may impact on network speed.
Signed-off-by: Ivan Mikhaylov
---
drivers/net/ethernet/ibm/emac/core.c |6 ++
drivers/net/ethernet/ibm
/MDIO mode
with 19 bit and write operation is set into 18 bit which is mode selection,
not a write operation. To correlate write with read we set it into 20 bit.
All those bit operations are MSB 0 based.
Signed-off-by: Ivan Mikhaylov
---
drivers/net/ethernet/ibm/emac/emac.h |2 +-
1 files
/MDIO mode
with 19 bit and write operation is set into 18 bit which is mode selection,
not a write operation. To correlate write with read we set it into 20 bit.
All those bit operations are MSB 0 based.
Signed-off-by: Ivan Mikhaylov
---
drivers/net/ethernet/ibm/emac/emac.h |2 +-
1 files
> So if someone tries to #define EMAC_STACR_STAC_WRITE BIT(18) it would be
> 0x4 instead. This is where the confusion is coming from. Can you please
> at least mention this somewhere that all the bits in the commit message are
> in "MSB 0" format? It's confusing enough as it is ;).
Yeap, sure,
>Something looks wrong here?! The commit message talks about bit 18, 19 and 20.
>However, 0x0800, 0x1000, 0x2000 and are like bit 11, 12 and 13? Furthermore,
>what about the EMAC_STACR_STAC_MASK? shouldn't it be 0x1800 now (or delete it
>since it doesn't look like it's used anywhere?).
Christian, n
/MDIO mode
with 19 bit and write operation is set into 18 bit which is mode selection,
not a write operation. To correlate write with read we set it into 20 bit.
Signed-off-by: Ivan Mikhaylov
---
drivers/net/ethernet/ibm/emac/emac.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
di
emac4syn chips has availability to use 8192 rx/tx fifo buffer sizes,
in current state if we set it up in dts 8192 as example, we will get
only 2048 which may impact on network speed.
Signed-off-by: Ivan Mikhaylov
---
drivers/net/ethernet/ibm/emac/core.c |6 ++
drivers/net/ethernet/ibm
add irq error handlers for cmu, plb, opb, mcue, conf
with debug information output in case of problems.
Signed-off-by: Ivan Mikhaylov
---
arch/powerpc/platforms/44x/fsp2.c | 198 -
1 files changed, 197 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc
* clear out any possible plb6 errors
* board interrupt handling setup within l2 reg set
* fsp2 parity error setup
All those points are needed for correct interrupt
handling on board level including error handling report.
Reviewed-by: Alistair Popple
Signed-off-by: Ivan Mikhaylov
---
arch
once the CMU interrupt is unmasked.
Purpose of this to set up CMU in working state in any cases even
in case of parity errors.
Reviewed-by: Alistair Popple
Signed-off-by: Ivan Mikhaylov
---
arch/powerpc/platforms/44x/fsp2.c | 17 +
1 files changed, 17 insertions(+), 0 deletions
add irq error handlers for cmu, plb, opb, mcue, conf
with debug information output in case of problems.
Signed-off-by: Ivan Mikhaylov
---
arch/powerpc/platforms/44x/fsp2.c | 205 -
1 files changed, 204 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc
add cmu, plbX, l2, ddr3/4, crcs register definitions.
add mfcmu, mtcmu functions for indirect access to cmu.
add mtl2, mfl2 same for l2 cache core reg set.
Signed-off-by: Ivan Mikhaylov
---
arch/powerpc/platforms/44x/fsp2.h | 272 +
1 files changed, 272
Signed-off-by: Ivan Mikhaylov
---
arch/powerpc/platforms/44x/fsp2.c | 37 +
1 files changed, 37 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/platforms/44x/fsp2.c
b/arch/powerpc/platforms/44x/fsp2.c
index 92e9804..9585725 100644
--- a/arch
* tvsense(temperature and voltage sensors) may provide
erratic sense values which may result in parity errors
on CMU.
Signed-off-by: Ivan Mikhaylov
---
arch/powerpc/platforms/44x/fsp2.c | 17 +
1 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc
* add irq error handlers for cmu, plb, opb, mcue, conf
with debug information output in case of problem.
Signed-off-by: Ivan Mikhaylov
---
arch/powerpc/platforms/44x/fsp2.c | 204 -
1 files changed, 203 insertions(+), 1 deletions(-)
diff --git a/arch
* add cmu, plbX, l2 register definitions
Signed-off-by: Ivan Mikhaylov
---
arch/powerpc/include/asm/fsp2_reg.h | 272 +++
1 files changed, 272 insertions(+), 0 deletions(-)
create mode 100644 arch/powerpc/include/asm/fsp2_reg.h
diff --git a/arch/powerpc
fsp2 board setup with l2 setup and irq handlers
for some critical exceptions.
Ivan Mikhaylov (4):
44x/fsp2: add fsp2 headers
44x/fsp2: l2 setup with error clear
44x/fsp2: tvsense workaround for dd1
44x/fsp2: add irq error handlers
arch/powerpc/include/asm/fsp2_reg.h | 272
Add mmc0 changes for enabling arasan emmc and change
defconfig appropriately.
Signed-off-by: Ivan Mikhaylov
---
arch/powerpc/boot/dts/fsp2.dts | 33 +-
arch/powerpc/configs/44x/fsp2_defconfig |2 +
2 files changed, 21 insertions(+), 14 deletions
Hi Ian,
>Building the split device-tree tree[0] highlighted that upstream commit
>9eec6cb142bd ("powerpc/44x/fsp2: Add device tree for FSP2 board") introduced
>this warning when building the device tree:
>
>$ make CROSS_COMPILE=powerpc-linux-gnu- ARCH=powerpc fsp2.dtb
> CHK scripts/mod/devicet
Add mmc0 changes for enabling arasan emmc and change
defconfig appropriately.
Signed-off-by: Ivan Mikhaylov
---
arch/powerpc/boot/dts/fsp2.dts | 33 +-
arch/powerpc/configs/44x/fsp2_defconfig |2 +
2 files changed, 21 insertions(+), 14 deletions
shdci-st driver can be used for ppc476 fsp2 soc.
Signed-off-by: Ivan Mikhaylov
---
drivers/mmc/host/Kconfig |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
index 2eb9701..edf5787 100644
--- a/drivers/mmc/host/Kconfig
fsp2 based on powerpc 476fpe using eMMC arasan, so we added support
of this inside our dts and also enabled via additional
dependence for sdhci-st driver in Kconfig.
this code depends on commit c4b56b023daa91953e9ebe91143e6ca156f0bcb7
which is located in powerpc linux tree in 'next' bra
1 - 100 of 134 matches
Mail list logo
