On Sun, Sep 27, 2015 at 06:05:35PM +0200, Olliver Schinagl wrote:
> Hey Hans,
>
> On 27-09-15 16:57, Hans de Goede wrote:
> >According to the datasheets to n factor for dividing the tclk is
> >2 to the power n on Allwinner SoCs, not 2 to the power n + 1 as it is
> >on other mv64xxx implementations
> It's true that this is something that we might have overlooked. Is it
> expected to maintain that compatibility when moving a driver from one
> framework to another (and this is a real question, not a troll)?
Yes. There will be user space applications reading from the eeprom
file in /sys. In fac
On Mon, Aug 17, 2015 at 03:59:23PM +0100, Srinivas Kandagatla wrote:
>
>
> On 17/08/15 14:09, Andrew Lunn wrote:
> >On Mon, Aug 17, 2015 at 02:01:24PM +0100, Srinivas Kandagatla wrote:
> >>
> >>+Adding Maxime in the loop
> >>
> >>On 16/08/15
On Mon, Aug 17, 2015 at 02:01:24PM +0100, Srinivas Kandagatla wrote:
>
> +Adding Maxime in the loop
>
> On 16/08/15 16:37, Stefan Wahren wrote:
> >>>Another question which spring to mind is, do we want the eeprom to be
> >>>in /sys twice, the old and the new way? Backwards compatibility says
> >>
On Sun, Aug 16, 2015 at 10:28:06AM +0200, Stefan Wahren wrote:
> Hi Andrew,
>
> > Andrew Lunn hat am 16. August 2015 um 04:54 geschrieben:
> >
> >
> > Add a read only regmap for accessing the EEPROM, and then use that
> > with the NVMEM framework
Add a read only regmap for accessing the EEPROM, and then use that
with the NVMEM framework.
Signed-off-by: Andrew Lunn
---
drivers/misc/eeprom/at24.c | 65 ++
1 file changed, 65 insertions(+)
diff --git a/drivers/misc/eeprom/at24.c b/drivers/misc
storing it and having to clear it
> afterwards.
>
> This issue was discovered after the property was removed from all
> sunxi DTs.
>
> Signed-off-by: Chen-Yu Tsai
> Cc: sta...@vger.kernel.org
It would be good to add
Fixes: 4c730a06c19bb ("i2c: mv64xxx: Set b
the removal. Keep
> the
> DEPRECATED flag, so the core can inform users that the behaviour finally
> changed now. After another transition period, this flag can go, too.
Hi Wolfram
Acked-by: Andrew Lunn
As far as i know, none of the arm boards using this driver make use of
class bas
The RobotFuzz device is not compatible with i2c-tiny-usb. Remove its
entry from the USB table so that the new correct driver can be used.
Signed-off-by: Andrew Lunn
CC: Emmanuel Deloget
CC: Barry Carter
---
drivers/i2c/busses/i2c-tiny-usb.c | 1 -
1 file changed, 1 deletion(-)
diff --git a
le mode 100644
index ..ced9c6a308d1
--- /dev/null
+++ b/drivers/i2c/busses/i2c-robotfuzz-osif.c
@@ -0,0 +1,202 @@
+/*
+ * Driver for RobotFuzz OSIF
+ *
+ * Copyright (c) 2013 Andrew Lunn
+ * Copyright (c) 2007 Barry Carter
+ *
+ * Based on the i2c-tiny-usb by
+ *
+ * Copyright (C)
Hi Wolfram
> > Hi Wolfgang
>
> Wolfram
Upps, Sorry.
> > So is this a zero byte transfer? Is that not what i2cdetect does?
>
> Yes, you can enforce it with -q. It will do it for some addresses
> automatically and complain if it is not available. So, seems to work,
> great!
O.K, i will double c
Hi Wolfgang
> > +static u32 usb_func(struct i2c_adapter *adapter)
> > +{
> > + return I2C_FUNC_I2C | I2C_FUNC_SMBUS_EMUL;
>
> Have you tried SMBUS_QUICK by the way?
Nope, not tried it.
Documentation/i2c/smbus-protocol say:
SMBus Quick Command
===
This sends a single bit to t
> Are you saying that FreeBSD has a different set of bindings for the
> same hardware?
Yes. I was not even aware FreeBSD was using DT until somebody
mentioned it in Edinburgh.
As an example:
http://fxr.watson.org/fxr/source/boot/fdt/dts/sheevaplug.dts
compared with
http://lxr.linux.no/linux+v
+= i2c-viperboard.o
diff --git a/drivers/i2c/busses/i2c-robotfuzz-osif.c
b/drivers/i2c/busses/i2c-robotfuzz-osif.c
new file mode 100644
index ..3e03c008775a
--- /dev/null
+++ b/drivers/i2c/busses/i2c-robotfuzz-osif.c
@@ -0,0 +1,201 @@
+/*
+ * Driver for RobotFuzz OSIF
+ *
+ * Copyright
The RobotFuzz device is not compatible with i2c-tiny-usb. Remove its
entry from the USB table so that the new correct driver can be used.
Signed-off-by: Andrew Lunn
CC: Emmanuel Deloget
CC: Barry Carter
---
drivers/i2c/busses/i2c-tiny-usb.c |1 -
1 file changed, 1 deletion(-)
diff --git
> >>Does that power down really disable reading from PCIe controller
> >>registers or is it just PHY power down?
> >
> >I haven't experimented with it, but every block that has a clock gate
> >has a power down, so I doubt it is just a phy power down.
>
> Ok, I see. But it isn't documented in the p
On Sun, Jan 05, 2014 at 08:17:10PM +0100, Arnd Bergmann wrote:
> On Sunday 05 January 2014, Andrew Lunn wrote:
> > That would be rather odd. These nodes are in the top level SoC dtsi
> > file. When they are not used, they have status = "disabled" and are in
> &g
> > +static int __init mvebu_soc_id_init(void)
> > +{
> > + struct device_node *np;
> > + int ret = 0;
> > +
> > + np = of_find_matching_node(NULL, mvebu_pcie_of_match_table);
> > + if (np) {
> > + void __iomem *pci_base;
> > + struct clk *clk;
> > + /*
> > +
> >> Hi Gregory
> >>
> >> I'm away from my hardware at the moment.
> >>
> >> Does this work when all the PCIe ports have status = "disabled";? We
> >> have many kirkwood devices in NAS boxes which don't use PCIe, so all
> >> the ports are disabled. But they still exist in the SoC, so we can
> >> r
On Fri, Jan 03, 2014 at 10:59:44AM +0100, Gregory CLEMENT wrote:
> All the mvebu SoCs have information related to their variant and
> revision that can be read from the PCI control register.
>
> This patch adds support for Armada XP and Armada 370. This reading of
> the revision and the ID are don
On Tue, Dec 31, 2013 at 05:44:50PM +0100, Gregory CLEMENT wrote:
> Hi,
>
> This series is an RFC to fix the i2c bus hang on A0 version of the
> Armada XP SoCs. It occured on the the eraly release of the OpenBlocks
> AX3-4 bords. Indeed the first variants of Armada XP SoCs (A0 stepping)
> have issu
> >We can have this information in the same way that it is currently done
> >by the other mvebu SoC: accessing the PCIE_DEV_REV_OFF register. In
> >arch/arm/plat-orion/pcie.c there were functions named
> >orion_pcie_dev_id() and orion_pcie_dev_id() to retrieve information
> >about the CPU variant a
The RobotFuzz device is not compatible with i2c-tiny-usb. Remove its
entry from the USB table so that the new correct driver can be used.
Signed-off-by: Andrew Lunn
CC: Emmanuel Deloget
CC: Barry Carter
---
drivers/i2c/busses/i2c-tiny-usb.c | 1 -
1 file changed, 1 deletion(-)
diff --git a
ivers/i2c/busses/i2c-osif.c
@@ -0,0 +1,267 @@
+/*
+ * Driver for RobotFuzz OSIF
+ *
+ * Copyright (c) 2007 Barry Carter
+ * Copyright (c) 2013 Andrew Lunn
+ *
+ * Based on the i2c-tiny-usb by
+ *
+ * Copyright (C) 2006 Til Harbaum (t...@harbaum.org)
+ *
+ * This program is free software; you
ivers/i2c/busses/i2c-osif.c
@@ -0,0 +1,267 @@
+/*
+ * Driver for RobotFuzz OSIF
+ *
+ * Copyright (c) 2007 Barry Carter
+ * Copyright (c) 2013 Andrew Lunn
+ *
+ * Based on the i2c-tiny-usb by
+ *
+ * Copyright (C) 2006 Til Harbaum (t...@harbaum.org)
+ *
+ * This program is free software; you
The RobotFuzz device is not compatible with i2c-tiny-usb. Remove its
entry from the USB table so that the new correct driver can be used.
Signed-off-by: Andrew Lunn
CC: Emmanuel Deloget
CC: Barry Carter
---
FYI: I'm away from the net for the next two weeks. So please take your time
le strings, and that holds the various
> registers that might be needed.
>
> Signed-off-by: Maxime Ripard
Hi Maxime
I tested on a Kirkwood QNAP. It has an RTC on the i2c bus. It still
gives the correct time with your patches applied.
Tested-by: Andrew Lunn
Andrew
>
>
On Wed, Jun 12, 2013 at 10:07:13AM +0200, Maxime Ripard wrote:
> Add the compatible string for the Allwinner A10 i2c controller and the
> associated register layout.
>
> Signed-off-by: Maxime Ripard
> ---
> drivers/i2c/busses/Kconfig | 3 ++-
> drivers/i2c/busses/i2c-mv64xxx.c | 1 +
> i
On Wed, Jun 12, 2013 at 10:07:11AM +0200, Maxime Ripard wrote:
> The Allwinner i2c controller uses the same logic as the Marvell one, but
> with slightly different register offsets.
>
> Introduce a structure that will be passed by either the pdata or
> associated to the compatible strings, and tha
On Mon, Jul 23, 2012 at 10:03:59PM +0200, Wolfram Sang wrote:
> On Sun, Jul 22, 2012 at 12:51:35PM +0200, Andrew Lunn wrote:
> > Extends the driver to get properties from device tree. Rather than
> > pass the N & M factors in DT, use the more standard clock-frequency
> >
ate() to determine the tclk rate. Not all platforms
however have CLK, so some #ifdefery is needed to ensure the driver
still compiles when CLK is not available.
Signed-off-by: Andrew Lunn
---
- Replaced the timeout property in DT, with a hard coded 1 second.
- Put all the OF code together.
- Split
ate() to determine the tclk rate. Not all platforms
however have CLK, so some #ifdefery is needed to ensure the driver
still compiles when CLK is not available.
Signed-off-by: Andrew Lunn
---
- Replaced the timeout property in DT, with a hard coded 1 second.
- Put all the OF code together.
- Split
On Fri, Jul 06, 2012 at 08:08:23PM +, Arnd Bergmann wrote:
> On Thursday 05 July 2012, Andrew Lunn wrote:
> > > I think the latter one needs to be
> > >
> > > +static int __initdata gpio1_irqs[4] = {
> > > + IRQ_DOVE_HI
> Something completely different I just noticed in the original patch:
>
> > @@ -90,6 +74,27 @@ static void pmu_irq_handler(unsigned int irq, struct
> > irq_desc *desc)
> > }
> > }
> >
> > +static int __initdata gpio0_irqs[4] = {
> > + IRQ_DOVE_GPIO_0_7,
> > + IRQ_DOVE_GPIO_8_15,
On Thu, Jul 05, 2012 at 04:14:50PM +0200, Sebastian Hesselbarth wrote:
> On 07/05/2012 03:08 PM, Andrew Lunn wrote:
> >The issue is knowing what IRQ number to use for the secondary
> >interrupts.
> >
> >Orion use generic chip interrupts, both for the main interrupts
On Thu, Jul 05, 2012 at 02:58:01PM +0200, Thomas Petazzoni wrote:
> Hello,
>
> Le Thu, 5 Jul 2012 11:48:24 +0200,
> Andrew Lunn a ??crit :
>
> > The biggest problem i had, is the interaction between generic chip
> > interrupts and irqdomain. There has been work to int
> > +Required properties
> > +- compatible : Should be "marvell,orion-intc".
> > +- #interrupt-cells: Specifies the number of cells needed to encode an
> > + interrupt source. Supported value is <1>.
> > +- interrupt-controller : Declare this node to be an interrupt controller.
> > +- reg : Inter
Hi Thomas
> Yes. I am not sure yet how to describe those in the DT, or even if it
> is actually useful to describe them. Wouldn't it be simpler to just
> leave to the user of the GPIO to use a GPIO that's appropriate for its
> usage, i.e not use a GPO when input is needed?
We assume the hardware
> I've looked at the datasheet for the 88F6281, and the GPIO registers
> look fairly similar with Armada 370/XP, except that:
>
> * On 88F6281, there are two GPIO banks, while on Armada 370/XP it's a
>continuous range of registers that control the GPIOs. But it can be
>assimilated as one
On Thu, Jul 05, 2012 at 11:02:51AM +0200, Thomas Petazzoni wrote:
> Hello Andrew,
>
> Le Tue, 3 Jul 2012 16:22:34 +0200,
> Andrew Lunn a ??crit :
>
> > Both IRQ and GPIO controllers can now be represented in DT. The IRQ
> > controllers are setup first, an
On Tue, Jul 03, 2012 at 05:47:57PM +0200, Florian Fainelli wrote:
> Hi Andrew,
>
> On Tuesday 03 July 2012 16:22:41 Andrew Lunn wrote:
> > The two different variants of QNAP TS devices, varying by SoC, put the
> > GPIO keys on different GPIO lines. Hence we need two d
On Tue, Jul 03, 2012 at 05:50:02PM +0200, Florian Fainelli wrote:
> Hello Andrew,
>
> On Tuesday 03 July 2012 16:22:45 Andrew Lunn wrote:
> > Based on work by Michael Waller and Jason Cooper.
> >
> > Added support for getting the interrupt number from DT.
> >
On Tue, Jul 03, 2012 at 10:52:17AM -0400, Josh Coombs wrote:
> On Tue, Jul 3, 2012 at 10:22 AM, Andrew Lunn wrote:
> > Convert boards using DT, but the old way of configuring SATA to now
> > use properties in there DT file.
>
> Andrew, should I be updating my GoFlex patch s
Based on work by Michael Waller and Jason Cooper.
Added support for getting the interrupt number from DT.
Signed-off-by: Andrew Lunn
---
.../devicetree/bindings/crypto/mv_cesa.txt | 18
drivers/crypto/mv_cesa.c | 31 +---
2
Convert boards using DT, but the old way of configuring SATA to now
use properties in there DT file.
Signed-off-by: Andrew Lunn
---
arch/arm/boot/dts/kirkwood-dns320.dts|5 +
arch/arm/boot/dts/kirkwood-dns325.dts|5 +
arch/arm/boot/dts/kirkwood-dreamplug.dts |5
Add support for instantiating this driver from device tree, and add
the necassary DT information to the kirkwood.dtsi file.
This is based on previous work by Michael Walle and Jason Cooper.
Signed-off-by: Andrew Lunn
---
Documentation/devicetree/bindings/ata/marvell.txt | 16
arch
Add device tree support to the Orion watchdog timer, and enable its
use in the kirkwood devices using device tree.
Signed-off-by: Andrew Lunn
---
Documentation/devicetree/bindings/watchdog/marvel.txt | 14 ++
arch/arm/boot/dts/kirkwood.dtsi |6
The two different variants of QNAP TS devices, varying by SoC, put the
GPIO keys on different GPIO lines. Hence we need two different DT
board descriptions, which share the same board-ts219.c file.
Signed-off-by: Andrew Lunn
Acked-by: Jason Cooper
---
arch/arm/boot/dts/kirkwood-ts219-6281.dts
From: Michael Walle
Use the device tree for the SPI driver and partition layout.
Signed-off-by: Michael Walle
Signed-off-by: Andrew Lunn
---
arch/arm/boot/dts/kirkwood-dreamplug.dts | 29 +
arch/arm/mach-kirkwood/board-dreamplug.c | 41
From: Michael Walle
Populate the devices with auxdata to set the device names which are used by
clkdev to lookup the clocks.
Signed-off-by: Michael Walle
Signed-off-by: Andrew Lunn
---
arch/arm/boot/dts/kirkwood.dtsi |9 +
arch/arm/mach-kirkwood/board-dt.c |8 +++-
2
From: Michael Walle
Signed-off-by: Michael Walle
Signed-off-by: Andrew Lunn
Acked-by: Jason Cooper
---
Documentation/devicetree/bindings/spi/spi-orion.txt |5 +
drivers/spi/spi-orion.c |9 +
2 files changed, 14 insertions(+)
create mode 100644
From: Michael Walle
This was formerly used to store the tclk value. This is now discovered
using the clk API, rather than pass it as platform data.
Signed-off-by: Michael Walle
Acked-by: Jason Cooper
Signed-off-by: Andrew Lunn
---
drivers/spi/spi-orion.c |5 -
1 file changed, 5
Both IRQ and GPIO controllers can now be represented in DT. The IRQ
controllers are setup first, and then the GPIO controllers. Interrupts
for GPIO lines are placed directly after the main interrupts in the
interrupt space.
Signed-off-by: Andrew Lunn
---
.../devicetree/bindings/arm/mrvl
Replace the deprecated master->transfer with transfer_one_message()
and allow the SPI subsystem handle all the queuing of messages.
Signed-off-by: Andrew Lunn
Acked-by: Linus Walleij
---
drivers/spi/spi-orion.c | 209 ++-
1 file changed,
rqdomain support. The
GPIO interrupts are also handled using an IRQ generic chip, thus a
similar layering is made. This applies to both DT and none DT IRQ and
GPIO controllers.
White space problem as pointed out by Michael Walle have been
corrected.
Andrew Lunn (8):
ARM: Orion: DT support for
On Wed, Jun 13, 2012 at 09:10:30PM +, Arnd Bergmann wrote:
> On Sunday 10 June 2012, Andrew Lunn wrote:
> > @@ -26,6 +26,11 @@ static struct of_device_id kirkwood_dt_match_table[]
> > __initdata = {
> > { }
> > };
> >
> > +struct of_dev_auxda
On Thu, Jun 14, 2012 at 08:12:34AM +, Arnd Bergmann wrote:
> On Sunday 10 June 2012, Andrew Lunn wrote:
> > +static int __init kirkwood_add_irq_domain(struct device_node *np,
> > + struct device_node
> &
> > + spi@10600 {
> > + compatible = "marvell,orion-spi";
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + cell-index = <0>;
> > + reg = <0x10600 0x28>;
> > + status = "di
The two different variants of QNAP TS devices, varying by SoC, put the
GPIO keys on different GPIO lines. Hence we need two different DT
board descriptions, which share the same board-ts219.c file.
Signed-off-by: Andrew Lunn
---
arch/arm/boot/dts/kirkwood-ts219-6281.dts | 21 +++
arch/arm
The GPIO controllers can now be described in DT. Origionally GPIO
controllers were instantiated during IRQ setup. The origional none-DT
code has been split out, and is only called if no DT GPIO controllers
are found.
Signed-off-by: Andrew Lunn
---
.../devicetree/bindings/gpio/mrvl-gpio.txt
From: Michael Walle
Signed-off-by: Michael Walle
Signed-off-by: Andrew Lunn
---
Documentation/devicetree/bindings/spi/spi-orion.txt |5 +
drivers/spi/spi-orion.c |9 +
2 files changed, 14 insertions(+)
create mode 100644 Documentation
From: Michael Walle
Use the device tree for the SPI driver and partition layout.
Signed-off-by: Michael Walle
Signed-off-by: Andrew Lunn
---
arch/arm/boot/dts/kirkwood-dreamplug.dts | 29 +
arch/arm/mach-kirkwood/board-dreamplug.c | 41
From: Michael Walle
Populate the devices with auxdata to set the device names which are used by
clkdev to lookup the clocks.
Signed-off-by: Michael Walle
Signed-off-by: Andrew Lunn
---
arch/arm/boot/dts/kirkwood.dtsi |9 +
arch/arm/mach-kirkwood/board-dt.c |8 +++-
2
From: Michael Walle
This was formerly used to store the tclk value. This is now discovered
using the clk API, rather than pass it as platform data.
Signed-off-by: Michael Walle
Acked-by: Jason Cooper
Signed-off-by: Andrew Lunn
---
drivers/spi/spi-orion.c |5 -
1 file changed, 5
Signed-off-by: Andrew Lunn
---
.../devicetree/bindings/arm/mrvl/intc.txt | 20 ++
arch/arm/boot/dts/kirkwood.dtsi|9
arch/arm/mach-kirkwood/board-dt.c | 22 +++-
3 files changed, 50 insertions(+), 1
Replace the deprecated master->transfer with transfer_one_message()
and allow the SPI subsystem handle all the queuing of messages.
Signed-off-by: Andrew Lunn
Acked-by: Linus Walleij
---
drivers/spi/spi-orion.c | 209 ++-
1 file changed,
onger needs.
Andrew Lunn (5):
ARM: Kirkwood: Add interrupt controller support for DT boards
SPI: Refactor spi-orion to use SPI framework queue.
I2C: MV64XXX: Add Device Tree support
ARM: Kirkwood: Add DT support for GPIO controllers
Kirkwood: Add basic device tree support for QNAP TS219.
Mi
67 matches
Mail list logo
