>>
>> I'll ask Linus to pull anyway though.
>>
>> Cheers,
>> Ben.
>
> I believe this is fixed in net-next (and possible linus has already
> pulled that in.)
FWIW, I can't reproduce the issue neither in benh/powerpc.git `next'
branch nor i
sg12665.html
I still think that
"fsl,mpc83NN-immr", "fsl,soc", "simple-bus" for 83xx
and
"fsl,mpc85NN-ccsr", "fsl,soc", "simple-bus" for 85xx
would be OK, at least to start with. We can always deprecate "fsl,soc"
compatible in favour of something more elegant, but "fsl,soc" should be
just fine to replace device_type = "soc".
Also, there is another good thing about "fsl,soc" -- U-Boot already
finds it for 83xx CPUs. ;-)
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
ly for
fsl,gianfar-tbi buses.
Signed-off-by: Anton Vorontsov
---
drivers/net/fsl_pq_mdio.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/fsl_pq_mdio.c b/drivers/net/fsl_pq_mdio.c
index b3079a5..d9e1ecf 100644
--- a/drivers/net/fsl_pq_mdio.c
+++ b/d
+0xc0/0x11c
[...]
Fix this by passing of_device's device that specifies DMA ops in its
archdata.
Signed-off-by: Anton Vorontsov
---
drivers/net/ucc_geth.c | 21 +++--
drivers/net/ucc_geth.h |3 ++-
2 files changed, 13 insertions(+), 11 deletions(-)
diff --git a/d
rty "fsl,upm-addr-line-cs-offsets".
>
> Signed-off-by: Wolfgang Grandegger
Acked-by: Anton Vorontsov
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
delay.
>
> Signed-off-by: Wolfgang Grandegger
Acked-by: Anton Vorontsov
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
he old binding for "chip-delay".
>
> Signed-off-by: Wolfgang Grandegger
Acked-by: Anton Vorontsov
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
et/fsl_pq_mdio.c
> @@ -204,6 +204,7 @@ void fsl_pq_mdio_bus_name(char *name, struct
> device_node *np
> snprintf(name, MII_BUS_ID_SIZE, "%...@%llx", np->name,
> (unsigned long long)taddr);
> }
> +EXPORT_SYMBOL_GPL(fsl_pq_mdio_bus_name);
&
something that affects "some mpc85xx" is relevant.
Not some, but *all* mpc85xx. The thing is that U-Boot is searching
for device_type = "soc" to fixup some properties (for example,
bus-frequency) for all mpc85xx parts, so you can't easily remove
the device_type w/o
00644
> --- a/drivers/usb/host/fhci-hcd.c
> +++ b/drivers/usb/host/fhci-hcd.c
> @@ -620,12 +620,21 @@ static int __devinit of_fhci_probe(struct of_device
> *ofdev,
> goto err_pram;
> }
>
> +#ifdef CONFIG_MPC832x_MDS
> + pr
On Thu, Apr 02, 2009 at 10:33:57PM +0400, Anton Vorontsov wrote:
[...]
> > + compatible = "fsl,mpc8360-qe-usb",
>
> Ditto. No need for mpc8360 compatible.
Oh, I was wrong. fsl_qe_udc driver uses mpc8360 compatible for
matching, so you can't remove i
On Thu, Apr 02, 2009 at 01:42:37PM -0500, Timur Tabi wrote:
> Anton Vorontsov wrote:
>
> > Oh, I was wrong. fsl_qe_udc driver uses mpc8360 compatible for
> > matching, so you can't remove it. :-/
>
> Ugh, that's a bug in the driver then.
Yes, but that depe
] [c03d0a50] fsl_diu_init+0x70/0xa4
...
This patch fixes the issue.
Signed-off-by: Anton Vorontsov
---
drivers/video/fsl-diu-fb.c | 34 +-
1 files changed, 21 insertions(+), 13 deletions(-)
diff --git a/drivers/video/fsl-diu-fb.c b/drivers/video/fsl-diu-fb.c
index
c0233164] snd_soc_instantiate_cards+0x2c/0x68
[df02bf30] [c0234704] snd_soc_register_platform+0x60/0x80
[df02bf50] [c03d5664] fsl_soc_platform_init+0x18/0x28
...
This patch fixes the issue by using card's device instead.
Signed-off-by: Anton Vorontsov
---
sound/soc/fsl/fsl
ely not experimental anymore.
Signed-off-by: Anton Vorontsov
---
drivers/spi/Kconfig | 14 ++
1 files changed, 6 insertions(+), 8 deletions(-)
diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
index 83a185d..3c1845c 100644
--- a/drivers/spi/Kconfig
+++ b/drivers/spi/Kconfi
y.
Signed-off-by: Anton Vorontsov
---
drivers/spi/spi_mpc83xx.c | 11 ++-
1 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/spi/spi_mpc83xx.c b/drivers/spi/spi_mpc83xx.c
index f4573a9..08b49d2 100644
--- a/drivers/spi/spi_mpc83xx.c
+++ b/drivers/spi/spi_mpc83xx.c
@@ -
m with the chip select
line, it's probably quite slow because it's routed via PIXIS).
Previously there was a work around: we didn't use chip-select line
at all, but some cards don't like that, so we'd better use the low
frequency.
Signed-off-by: Anton Vorontsov
---
arch/powe
so
this won't work.
> On Sat, Apr 4, 2009 at 12:33 PM, Anton Vorontsov
> wrote:
> > The driver should pass a device that specifies internal DMA ops, but
> > substream->pcm is just a logical device, and thus doesn't have arch-
> > specific dma callbacks, the
tecture
> */
> @@ -105,6 +121,8 @@ static struct of_device_id __initdata
> socrates_of_bus_ids[] = {
> static void __init socrates_init(void)
> {
> of_platform_bus_probe(NULL, socrates_of_bus_ids, NULL);
> + phy_register_fixup_for_uid(0x1410cb0, 0xff0,
> +
On Tue, Apr 07, 2009 at 07:24:12PM +0200, Anatolij Gustschin wrote:
> Anton Vorontsov wrote:
> > On Tue, Apr 07, 2009 at 04:19:48PM +0200, Anatolij Gustschin wrote:
> >> If the firmware missed to initialize the PHY correctly,
> >> Linux may hang up on socrate
On Tue, Apr 07, 2009 at 10:09:57PM +0400, Anton Vorontsov wrote:
[...]
> Still, I think you shouldn't do this in a board-specific fixup.
> Maybe I'm a bit naive, but shouldn't this work too?
Yes, I'm naive. The phydev isn't yet bound to any driver, so we
can't
On Tue, Apr 14, 2009 at 12:42:47PM -0600, Grant Likely wrote:
> Thanks Subrata. I'll look into this.
Whoops. That's my fault, I didn't expect that anyone other
than spi_mpc83xx is using fsl_spi_platform_data. :-/
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://ir
ct fsl_spi_platform_data'
has no member named 'deactivate_cs'
make[2]: *** [drivers/spi/mpc52xx_psc_spi.o] Error 1
This patch simply adds the legacy hooks back for 2.6.30, and for
2.6.31 we'll convert the driver to ->cs_control.
Reported-by: Subrata Modak
Signed-off-by: Anton Vo
#x27;s specified via fixed-link property in the device tree.
The bindings described in Documentation/powerpc/dts-bindings/fsl/tsec.txt.
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Linuxppc-dev mailing list
Linuxppc-
. But can we decide on soc's
compatible scheme and finally remove the device_type = "soc"
for new boards? "fsl,p2020-soc", "fsl,soc", "simple-bus" maybe?
Thanks,
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
On Wed, Apr 15, 2009 at 12:20:14PM -0500, Kumar Gala wrote:
>
> On Apr 15, 2009, at 11:17 AM, Anton Vorontsov wrote:
>
>> On Wed, Apr 15, 2009 at 10:54:40AM -0500, Kumar Gala wrote:
>>> Vitaly, Anton
>>>
>>> You guys have used this code.. I was wonderin
On Wed, Apr 15, 2009 at 12:22:48PM -0500, Kumar Gala wrote:
>
> On Apr 15, 2009, at 11:50 AM, Anton Vorontsov wrote:
>
>>
>> Sorry for bringing this up again... But can we decide on soc's
>> compatible scheme and finally remove the device_type = "soc"
&g
+ * which use a Ali M15x3 south bridge like e.g. Xilinx ML310/410/510.
> > */
> >
> > static void __devinit init_hwif_ali15x3 (ide_hwif_t *hwif)
> > @@ -455,7 +456,7 @@ static void __devinit init_hwif_ali15x3 (ide_hwif_t
> > *hwif)
> > }
> > #else
>
On Thu, Apr 16, 2009 at 11:27:34PM +0200, Roderick Colenbrander wrote:
> On Thu, Apr 16, 2009 at 10:57 PM, Anton Vorontsov
> wrote:
> > On Thu, Apr 16, 2009 at 09:30:00PM +0200, Bartlomiej Zolnierkiewicz wrote:
> >>
> >> Hi,
> >>
> >> On Wednes
Hi Peter,
Sorry for the late response (and don't hesitate to ping me if I
don't answer, some things get lost in my inbox traffic, sorry).
On Wed, Apr 08, 2009 at 11:18:43AM +0200, Peter Korsgaard wrote:
> >>>>> "Anton" == Anton Vorontsov writes:
>
ine.
But they don't. On MPC8610HPCD we have IDE interrupt directly
connected to the MPIC line (through PCI sideband interrupt), and
i8259 is _completely_ disabled in the bridge.
See this commit:
commit 6d1cee44361b8d06ccd1812e80448d86ae60dfe3
Author: Anton Vorontsov
Date: Tue A
; > how the chip is configured by reading said configuration and use
> > either the legacy interrupts or the PCI one...
> >
> > > See this commit:
> > >
> > > commit 6d1cee44361b8d06ccd1812e80448d86ae60dfe3
> > > Author: Anton Voronts
From: Joakim Tjernlund
This will make the system alot more responsive while ping flooding the
ucc_geth ethernet interface.
Also set NAPI weight to 64 as this is a common value.
Signed-off-by: Joakim Tjernlund
Signed-off-by: Anton Vorontsov
---
drivers/net/ucc_geth.c | 31
[ef82be40] [c0234f20] of_platform_device_probe+0x5c/0x84
[...]
---[ end trace 561bb236c800851f ]---
This patch fixes the issue.
Signed-off-by: Anton Vorontsov
---
arch/powerpc/sysdev/fsl_rio.c | 28 +---
1 files changed, 17 insertions(+), 11 deletions(-)
diff --git a/arch
definition.
Sure, there is a completely different story wrt device-tree
changes that might break firmwares. And that I believe we'd
better avoid. For example device_type = "soc", if removed,
most firmwares would not fix-up {clock,bus}-freq
ate your device tree
> > (thus we have .dts in the kernel tree and not somewhere else).
>
> Not always possible. The device tree may be 'softer' than firmware,
> and easier to update, but it is still firmer than the kernel. That is
> why so much effort has been spent to no
On Thu, Apr 23, 2009 at 09:02:49AM -0500, Timur Tabi wrote:
> Anton Vorontsov wrote:
>
> > And note that most developers are using up-to-date firmwares
> > (U-Boots), device trees, and kernels.
>
> Developers? Yes.
> End-users? No.
If end-users upgraded the kernel on
On Thu, Apr 23, 2009 at 11:00:48AM -0500, Scott Wood wrote:
> On Thu, Apr 23, 2009 at 05:50:05PM +0400, Anton Vorontsov wrote:
> > As for Freescale parts, all the reference board I've seen were
> > very friendly wrt upgrading their device-trees, i.e. none of
> > the
On Thu, Apr 23, 2009 at 12:03:06PM -0500, Scott Wood wrote:
> Anton Vorontsov wrote:
>> On Thu, Apr 23, 2009 at 11:00:48AM -0500, Scott Wood wrote:
>>> Even if the given change may not break the firmware, it could force an
>>> update in which a prior change breaks the f
harm, and today some PowerPC targets (Xilinx ML510,
as reported by Roderick Colenbrander) need the init_hwif, so we have
to re-enable it and remove the overwrite.
Reported-by: Roderick Colenbrander
Suggested-by: Bartlomiej Zolnierkiewicz
Signed-off-by: Anton Vorontsov
---
On Mon, Apr 27, 2009 at
d.
It might be late for 2.6.33, but I believe that the patches are
actually quite safe.
Thanks!
[1] http://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg37297.html
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
This patch fixes following warnings:
ehci-fsl.c:43:5: warning: symbol 'usb_hcd_fsl_probe' was not declared. Should
it be static?
ehci-fsl.c:150:6: warning: symbol 'usb_hcd_fsl_remove' was not declared. Should
it be static?
Signed-off-by: Anton Vorontsov
---
drivers/usb/ho
deep sleep.
Based on Dave Liu and Jerry Huang's work[1].
[1]
http://www.bitshrine.org/gpp/linux-fsl-2.6.24.3-MPC8315ERDB-usb-power-mangement.patch
Signed-off-by: Anton Vorontsov
---
drivers/usb/host/ehci-fsl.c | 90 +++---
1 files changed, 83 insertions(
ngs eventually break when
_mpic_irq_read() is trying to use them.
This patch fixes the issue by enabling MPIC_BROKEN_FRR_NIRQS quirk.
Signed-off-by: Anton Vorontsov
---
arch/powerpc/platforms/85xx/mpc85xx_mds.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/powe
, soon there will be an easier way to register I2C/SPI chips
with the OF GPIO infrastructure.
Thanks,
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
and starting it again on resume.
Signed-off-by: Anton Vorontsov
---
drivers/net/phy/mdio_bus.c | 24 ++--
1 files changed, 22 insertions(+), 2 deletions(-)
diff --git a/drivers/net/phy/mdio_bus.c b/drivers/net/phy/mdio_bus.c
index bd4e8d7..49252d3 100644
--- a/drivers/net
Since hibernation assumes power loss, we should fully reinitialize
PHYs (including platform fixups), as if PHYs were just attached.
This patch factors phy_init_hw() out of phy_attach_direct(), then
converts mdio_bus to dev_pm_ops and adds an appropriate restore()
callback.
Signed-off-by: Anton
the issue by properly detaching the device on
suspend, and attaching it back on resume.
Signed-off-by: Anton Vorontsov
---
drivers/net/ucc_geth.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/net/ucc_geth.c b/drivers/net/ucc_geth.c
index afaf088..7225d5d 100644
On Wed, Dec 23, 2009 at 12:40:19PM -0500, Lennart Sorensen wrote:
> We use the ucc_geth for 6 ports (4 100Mbit and 2 Gbit ports) on an
> mpc8360e. Up to 2.6.31 this worked fine. 2.6.32 on the other hand
> crashes very quickly after boot.
Hm. Just curious, what CPU revision you use? So that I cou
On Wed, Dec 23, 2009 at 03:09:48PM -0500, Lennart Sorensen wrote:
[...]
> So there result is:
>
> Unable to handle kernel paging request for data at address 0x0058
> Faulting instruction address: 0xc024f2fc
> Oops: Kernel access of bad area, sig: 11 [#1]
> RC8360 CM
> Modules linked in: rcliba
.31
> and is hopefully an obvious fix.
Yep, will try to get them there.
Thanks a lot for helping to track this down,
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.o
Hi all,
Here are some more fixes and one small enhancement for the ucc_geth
driver.
Thanks,
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https
oving 'netif_queue_stopped() == 0' check.
Reported-by: Lennart Sorensen
Signed-off-by: Anton Vorontsov
Tested-by: Lennart Sorensen
Cc: Stable [2.6.32]
---
drivers/net/ucc_geth.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/ucc_geth.c b/drivers/net/ucc_geth.
_exit+0x7c/0x9c
[c0451e10] [c00640c4] __ipipe_sync_stage+0x248/0x24c
[...]
This patch fixes the issue by detaching the netdev during the
time we change the configuration.
Reported-by: Lennart Sorensen
Signed-off-by: Anton Vorontsov
Tested-by: Lennart Sorensen
Cc: Stable [2.6.32]
---
d
If PHY doesn't have an IRQ, phylib would poll for link changes, and
would call adjust_link() every second. In that case we disable and
enable the controller every second.
Let's better check if there is actually anything changed, and, if so,
change the MAC settings.
Signed-off-by: Anton
It seems there is a thinko in the TLB invalidation code that makes the
tlbie in the loop executed just once. The intended check was probably
'gt', not 'lt'.
Signed-off-by: Anton Vorontsov
---
Btw, 'lis r4,0x1000' seems needlessly too high. e300 core reference
's confine the code to
FSL BookE. (The only FSL-specific parts are 'flush_dcache_L1' and TLB
invalidation code).
Signed-off-by: Anton Vorontsov
---
arch/powerpc/kernel/Makefile |8 +-
arch/powerpc/kernel/swsusp_fsl_booke.S | 196
2 file
NFIG_PM is not always enabled :-)
Ugh, sorry about that, and thanks for catching!
Here are the amended patches + one more fix.
Thanks,
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Linuxppc-dev mailing list
Linuxp
and starting it again on resume.
Signed-off-by: Anton Vorontsov
---
drivers/net/phy/mdio_bus.c | 24 ++--
1 files changed, 22 insertions(+), 2 deletions(-)
diff --git a/drivers/net/phy/mdio_bus.c b/drivers/net/phy/mdio_bus.c
index bd4e8d7..49252d3 100644
--- a/drivers/net
Since hibernation assumes power loss, we should fully reinitialize
PHYs (including platform fixups), as if PHYs were just attached.
This patch factors phy_init_hw() out of phy_attach_direct(), then
converts mdio_bus to dev_pm_ops and adds an appropriate restore()
callback.
Signed-off-by: Anton
the issue by properly detaching the device on
suspend, and attaching it back on resume.
Signed-off-by: Anton Vorontsov
---
drivers/net/ucc_geth.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/net/ucc_geth.c b/drivers/net/ucc_geth.c
index 41ad2f3..96bdc0b 100644
__driver_attach+0xa4/0xa8
Fix this by introducing a proper priv structure (finally!), which
now holds 'regs' and 'map' fields separately.
Signed-off-by: Anton Vorontsov
---
drivers/net/fsl_pq_mdio.c | 30 +++---
1 files changed, 23 insertions
kernel
(it's there since 2.6.26, IIRC).
Or are you looking for the ready to use back-port of that
driver? I don't have one, but it should be relatively easiy
to back-port.
Thanks,
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc:
On Mon, Jan 11, 2010 at 11:47:37AM +0800, Wu Jiajun-B06378 wrote:
>
> 'bd == ugeth->txBd[txQ]' has two possible statuses: 1)full queue.
> 2)empty queue.
> Removing 'netif_queue_stopped() == 0' will make transmitting stopping
> when the queue is full.
>
> I made a new patch for this oops.
[...]
it(), causing the WARN_ON in mpc8xxx_spi_free_dummy_rx() for !CPM.
>
> Fix it by adding the same check in _cpm_free() as well.
>
> Signed-off-by: Peter Korsgaard
Acked-by: Anton Vorontsov
Grant, can you please push it for 2.6.33?
Thanks!
> ---
> drivers/spi/spi_mpc8xxx
On Tue, Jan 12, 2010 at 05:24:10PM +0100, Peter Korsgaard wrote:
> >>>>> Peter Korsgaard writes:
>
> Hi,
>
> Anton, any comments on this?
>
> > Signed-off-by: Peter Korsgaard
Acked-by: Anton Vorontsov
Thanks!
--
Anton Vorontsov
email: cbouatmai.
omes full since 'bd == ugeth->txBd[txQ]' actually checks for
two things: queue empty or full.
Let's better check for NULL skb, which unambiguously signals an empty
queue.
Signed-off-by: Jiajun Wu
Signed-off-by: Anton Vorontsov
Cc: Stable [2.6.32]
---
On Mon, Jan 11, 2010 at 0
On Wed, Dec 16, 2009 at 01:58:09AM +0300, Anton Vorontsov wrote:
> MPC85xx chips report the wrong value in feature reporting register,
> and that causes the following oops:
>
> Unable to handle kernel paging request for data at address 0x0c00
> Faulting instruction addr
GPIO chips that don't need any platform data (e.g.
mcu_mpc8349emitx) or that have OF bindings already (e.g. pca953x).
Thanks,
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Linuxppc-dev mailing list
Linuxppc-dev@l
Some platforms (e.g. OpenFirmware) want to know when a particular chip
added or removed, so that the platforms could add their specifics for
non-platform devices, like I2C or SPI GPIO chips.
This patch implements the notifier for chip addition and removal events.
Signed-off-by: Anton Vorontsov
ructure separately
from the of_gpio_chip. (Since two allocations are separate,
container_of won't work.)
As time goes by we'll kill the first option.
Signed-off-by: Anton Vorontsov
---
arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c |1 +
drivers/of/gpio.c
because some chips still require platform data, and for these
chips OF-glue is still needed, though with this support the glue will
be much smaller.
Signed-off-by: Anton Vorontsov
---
drivers/of/Kconfig |1 +
drivers/of/gpio.c | 100
With the new OF GPIO infrastructure it's much easier to handle I2C
GPIO controllers, i.e. now drivers don't have to deal with the
OF-specific bits.
Signed-off-by: Anton Vorontsov
---
arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c | 68 +---
1 files changed, 14
On Mon, Jan 25, 2010 at 10:34:29PM -0800, David Brownell wrote:
> On Monday 25 January 2010, Anton Vorontsov wrote:
> >
> > +config GPIOLIB_NOTIFIER
> > + bool
> > + help
> > + This symbol is selected by subsystems that need to handle GPIO
On Mon, Jan 25, 2010 at 10:36:15PM -0800, David Brownell wrote:
> On Monday 25 January 2010, Anton Vorontsov wrote:
> > With this patch there are two ways to register OF GPIO controllers:
> >
> > 1. Allocating the of_gpio_chip structure and passing the
> >
Hi all,
FHCI no longer builds after kfifo rework, this patch set is
used to fix the issues.
Thanks,
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https
roach is used in kfifo_alloc() if allocation failed).
Signed-off-by: Anton Vorontsov
---
kernel/kfifo.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/kernel/kfifo.c b/kernel/kfifo.c
index 32c5c15..3b00bf8 100644
--- a/kernel/kfifo.c
+++ b/kernel/kfifo.c
@@ -97,6
alue where scalar is
required
drivers/usb/host/fhci-tds.c:128: error: used struct type value where scalar is
required
This is because kfifos are no longer pointers in the ep struct.
So, instead of checking the pointers, we should now check if kfifo
is initialized.
Reported-by: Josh Boyer
Signed-off
This patch fixes following sparse warnings:
include/linux/kfifo.h:127:25: warning: Using plain integer as NULL pointer
kernel/kfifo.c:83:21: warning: Using plain integer as NULL pointer
Signed-off-by: Anton Vorontsov
---
include/linux/kfifo.h |2 +-
kernel/kfifo.c|2 +-
2 files
patches could go via powerpc
or OF trees, so your Ack would be highly appreciated.
Thanks!
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Some platforms (e.g. OpenFirmware) want to know when a particular chip
added or removed, so that the platforms could add their specifics for
non-platform devices, like I2C or SPI GPIO chips.
This patch implements the notifier for chip addition and removal events.
Signed-off-by: Anton Vorontsov
(Since two allocations are separate,
container_of won't work.)
As time goes by we'll kill the first option.
Signed-off-by: Anton Vorontsov
---
arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c |1 +
drivers/of/gpio.c | 23
because some chips still require platform data, and for these
chips OF-glue is still needed, though with this support the glue will
be much smaller.
Signed-off-by: Anton Vorontsov
---
drivers/of/gpio.c | 100 +
1 files changed, 100 ins
With the new OF GPIO infrastructure it's much easier to handle I2C
GPIO controllers, i.e. now drivers don't have to deal with the
OF-specific bits.
Signed-off-by: Anton Vorontsov
---
arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c | 68 +---
1 files changed, 14
op of
'[PATCH v2 0/4] OF GPIO integration for I2C/SPI GPIO chips'
http://lkml.org/lkml/2010/2/5/243
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://l
So far of_node_init() just initializes a kref, later we'll have to
initialize other fields (for example node->data_lock).
Signed-off-by: Anton Vorontsov
---
arch/microblaze/kernel/prom.c |4 ++--
arch/powerpc/kernel/prom.c|4 ++--
arch/powerpc/p
ips detaching,
so to handle this correctly we have to introduce locking for the
node->data field.
Signed-off-by: Anton Vorontsov
---
drivers/of/base.c | 45 +
include/linux/of.h |5 +
2 files changed, 50 insertions(+), 0 deletions(-)
diff -
d-off-by: Anton Vorontsov
---
drivers/of/gpio.c | 82 ---
include/linux/of_gpio.h |5 +++
2 files changed, 75 insertions(+), 12 deletions(-)
diff --git a/drivers/of/gpio.c b/drivers/of/gpio.c
index 9d8df77..e94c5c8 100644
--- a/drivers/of/g
e last value of the default-state property, which is wrong.
This patch fixes the issue by moving LED's template initialization
into the loop body.
Signed-off-by: Anton Vorontsov
---
drivers/leds/leds-gpio.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/leds/
This patch adds NOR Flash, LEDs and PIB support for MPC8568E-MDS
boards. Plus, move bcsr node into localbus node, and add bcsr5
gpio-controller node.
Some platform code modifications were also needed.
Signed-off-by: Anton Vorontsov
---
arch/powerpc/boot/dts/mpc8568mds.dts | 65
On Mon, Feb 08, 2010 at 01:04:55PM -0800, Andrew Morton wrote:
> On Fri, 5 Feb 2010 23:54:37 +0300
> Anton Vorontsov wrote:
>
> > The driver wrongly sets default state for LEDs that don't specify
> > default-state property.
[...]
> Does this actually happen in any 2
t found any problem. There is only small part of
> code for Microblaze and it is the same with PowerPC. If is Ben OK
> with it, I am ok too.
Thanks for testing!
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Lin
On Tue, Feb 09, 2010 at 10:08:00AM -0700, Grant Likely wrote:
> On Fri, Feb 5, 2010 at 1:32 PM, Anton Vorontsov
> wrote:
> > This patch implements GPIOLIB notifier hooks, and thus makes device-enabled
> > GPIO chips (i.e. the ones that have gpio_chip->dev specified) automati
On Tue, Feb 09, 2010 at 10:25:22AM -0700, Grant Likely wrote:
> On Fri, Feb 5, 2010 at 1:50 PM, Anton Vorontsov
> wrote:
> > Platform code use node->data to store some private information
> > associated with a node.
> >
> > Previously there was no need for any
you also refcount np->data
usage and can drop the devtree/np->data lock, and grab some other
kind of lock, e.g. mutex, but this is silly).
Thanks,
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Linuxppc-dev m
ly control them.
Plus I don't see any reason why we couldn't move
of_gpio_notifier_init() into, say, postcore_initcall, if we ever
need it.
Thanks,
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Linuxppc-dev
> and
> dereferencing the np->data pointer in this way is dangerous
> (what if
> something that is not struct of_gc is stored there).
Not possible with the safe np->data accessors.
--
Anton Vorontsov
email: cbouatmai...@gmail.com
irc://irc.freenode.net/bd2
___
Interrupt controllers' hooks are executed in the atomic context, so
they are not permitted to sleep (with RT kernels non-raw spinlocks are
sleepable). So, qe_ic_lock has to be a real (non-sleepable) spinlock.
Signed-off-by: Anton Vorontsov
---
On Thu, Feb 18, 2010 at 12:22:18PM -, T
Interrupt controllers' hooks are executed in the atomic context, so
they are not permitted to sleep (with RT kernels non-raw spinlocks are
sleepable). So, socrates_fpga_pic_lock has to be a real (non-sleepable)
spinlock.
Signed-off-by: Anton Vorontsov
---
On Thu, Feb 18, 2010 at 12:22
Interrupt controllers' hooks are executed in the atomic context, so
they are not permitted to sleep (with RT kernels non-raw spinlocks are
sleepable). So, gef_pic_lock has to be a real (non-sleepable) spinlock.
Signed-off-by: Anton Vorontsov
---
arch/powerpc/platforms/86xx/gef_pic.c |
401 - 500 of 1893 matches
Mail list logo