* Re: [PATCH 0/5] Review request: Cypress c67x00 OTG controller
From: David Brownell @ 2007-11-24 17:57 UTC (permalink / raw)
To: Grant Likely; +Cc: akpm, linuxppc-dev, gregkh, linux-usb-devel
In-Reply-To: <20071124001203.25361.99294.stgit@trillian.cg.shawcable.net>
On Friday 23 November 2007, Grant Likely wrote:
>
> This patch series is based on the c67x00 work done by Peter Korsgaard and
> posted back in April this year.
What's changed since that version? Were the comments sent
at that time addressed?
^ permalink raw reply
* Re: [PATCH 4/5] PowerPC 74xx: Katana Qp base support
From: Arnd Bergmann @ 2007-11-24 18:51 UTC (permalink / raw)
To: linuxppc-dev
In-Reply-To: <20071116163116.GE25062@ru.mvista.com>
On Friday 16 November 2007, Andrei Dolnikov wrote:
> +static int __init katanaqp_is_monarch(void)
> +{
> + return !(in_8((volatile char *)(cpld_base + KATANAQP_CPLD_PSR)) &
> + KATANAQP_CPLD_PSR_PMCM);
> +}
The pointer here needs to be __iomem, not volatile. Same in other places.
Please use 'sparse' to check your code for bugs like this.
> +
> +static void __init katanaqp_setup_arch(void)
> +{
> + struct device_node *cpld;
> + const unsigned int *reg;
> +
> + /*
> + * ioremap cpld registers in case they are later
> + * needed by katanaqp_reset_board().
> + */
> + cpld = of_find_node_by_path("/mv64x60@f8100000/cpld@f8200000");
It doesn't sounds good to hardcode the path for this device.
Instead, it would be much better to look for the 'compatible' property
here.
> +static int __init katanaqp_of_init(void)
> +{
> + struct device_node *np;
> +
> + np = of_find_compatible_node(NULL, NULL, "cfi-flash");
> + if (np)
> + of_platform_device_create(np, "of-flash", NULL);
> +
> + return 0;
> +}
> +
> +device_initcall(katanaqp_of_init);
This should be done automatically using of_platform_bus_probe().
Arnd <><
^ permalink raw reply
* Re: [RFC/PATCH] powerpc: Move CPM command handling into the cpm drivers
From: Jochen Friedrich @ 2007-11-24 17:53 UTC (permalink / raw)
To: Vitaly Bordug; +Cc: linuxppc-dev
In-Reply-To: <20071123005121.4d38d877@kernel.crashing.org>
Hi Vitaly,
>>> + printk(KERN_ERR "%s(): Not able to issue CPM command\n",
>>> + __FUNCTION__);
>>> + return -EIO;
>>>
>> Do these need to be protected with a spin lock?
>>
> Even that might be not enough - we may have simultaneous call of this func in non-smp case...
> I was thinking of some kind of refcount, so one that is going to issue CPM command, must do say pq_cpmp_get()
> and another driver won't be able to mangle with cpcr while it's not done with previous request.
>
> Yet I am not telling it was better the way it used to be - this approach looks okay but needs some efforts to defend against
> deadlocks while we are at it
Wouldn't spin_lock_irqsave() prevent a deadlock?
Thanks,
Jochen
^ permalink raw reply
* Re: [linux-usb-devel] [PATCH 1/5] USB: Make usb_hcd_irq work for multi-role USB controllers w/ shared irq
From: David Brownell @ 2007-11-24 17:50 UTC (permalink / raw)
To: Alan Cox; +Cc: akpm, Greg KH, linux-usb-devel, linuxppc-dev
In-Reply-To: <20071124170307.773d7317@the-village.bc.nu>
On Saturday 24 November 2007, Alan Cox wrote:
> >
> > What about for platforms where irq 0 is a valid irq?
>
> There are no such platforms. Linus made that absolutely clear every time
> this came up before
>
> 0 - No IRQ
>
> A platform with a physical or bus IRQ of 0 needs to remap it to a
> different constant.
However it's also common practice to use negative numbers to
flag "this is no IRQ" ... avoiding all confusions with zero.
- platform_get_irq(), platform_get_irq_byname() ... never
return zero, they return irq (positive) or errno
- PNP initializes invalid IRQs to "-1", and pnp_check_irq()
handles irq zero as in-range
- I'm sure I've seen negative numbers used elsewhere too
Something like
#define is_valid_irq(x) ((x) >= 0)
would work better than expecting sudden agreement everywhere
about a single number representing "this is not an IRQ".
- Dave
^ permalink raw reply
* Re: [linux-usb-devel] [PATCH 1/5] USB: Make usb_hcd_irq work for multi-role USB controllers w/ shared irq
From: Grant Likely @ 2007-11-24 17:15 UTC (permalink / raw)
To: Alan Cox; +Cc: akpm, linuxppc-dev, Greg KH, linux-usb-devel, dbrownell
In-Reply-To: <20071124170307.773d7317@the-village.bc.nu>
On 11/24/07, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Fri, 23 Nov 2007 21:10:39 -0800
> Greg KH <gregkh@suse.de> wrote:
>
> > On Fri, Nov 23, 2007 at 05:24:31PM -0700, Grant Likely wrote:
> > > From: Peter Korsgaard <peter.korsgaard@barco.com>
> > >
> > > Some multi-role (host/peripheral) USB controllers use a shared interrupt
> > > line for all parts of the chip. Export usb_hcd_irq so drivers can call it
> > > from their interrupt handler instead of duplicating code.
> > > Drivers pass an irqnum of 0 to usb_add_hcd to signal that the interrupt handler
> > > shouldn't be registerred by the core.
> >
> > What about for platforms where irq 0 is a valid irq?
>
> There are no such platforms. Linus made that absolutely clear every time
> this came up before
>
> 0 - No IRQ
>
> A platform with a physical or bus IRQ of 0 needs to remap it to a
> different constant.
Regardless, I should probably use the NO_IRQ macro instead.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
^ permalink raw reply
* Re: [linux-usb-devel] [PATCH 1/5] USB: Make usb_hcd_irq work for multi-role USB controllers w/ shared irq
From: Alan Cox @ 2007-11-24 17:03 UTC (permalink / raw)
To: Greg KH; +Cc: akpm, dbrownell, linux-usb-devel, linuxppc-dev
In-Reply-To: <20071124051039.GA11029@suse.de>
On Fri, 23 Nov 2007 21:10:39 -0800
Greg KH <gregkh@suse.de> wrote:
> On Fri, Nov 23, 2007 at 05:24:31PM -0700, Grant Likely wrote:
> > From: Peter Korsgaard <peter.korsgaard@barco.com>
> >
> > Some multi-role (host/peripheral) USB controllers use a shared interrupt
> > line for all parts of the chip. Export usb_hcd_irq so drivers can call it
> > from their interrupt handler instead of duplicating code.
> > Drivers pass an irqnum of 0 to usb_add_hcd to signal that the interrupt handler
> > shouldn't be registerred by the core.
>
> What about for platforms where irq 0 is a valid irq?
There are no such platforms. Linus made that absolutely clear every time
this came up before
0 - No IRQ
A platform with a physical or bus IRQ of 0 needs to remap it to a
different constant.
Alan
^ permalink raw reply
* Re: Xilinx devicetrees
From: Grant Likely @ 2007-11-24 17:12 UTC (permalink / raw)
To: David H. Lynch Jr.; +Cc: linuxppc-embedded
In-Reply-To: <47480CF0.7090105@dlasys.net>
On 11/24/07, David H. Lynch Jr. <dhlii@dlasys.net> wrote:
> I am following developments regarding device trees for xilinx boards
> both here and on the microblaze list.
>
> I am trying to get a grasp on what they will really do for me and
> what using them will demand.
>
> Please correct any misperceptions:
>
> As I understand it devicetrees are basically just a tree structured
> binary database describing the hardware.
> They have some heritage in OpenFirmware.
> There are tools to convert some human readable representations into
> the binary form.
> There appear to be tools to take xilinx firmware projects and create
> a devicetree database from it
> A BSP using devicetree's configures its hardware, drivers etc, by
> querying the devicetree database.
> It it possible to pass the device tree database independent of the
> kernel itself some what similar to the way many bootloaders pass initrd
> filesystems.
Yes, you are correct in all of the above.
One more point; it is also possible to bind the device tree up with
the kernel so you've got a single image just like old times. :-)
>
> So in the end I write a BSP that could support a wide variety of
> hardware and compile a single kernel that could be passed different
> devicetree databases representing different xilinx firmware, and still
> hope to work.
> But in return for making the BSP more generic (sort of), I now have
> to somehow get the correct devicetree database passed for each different
> firmware set that I load.
Yes; either by changes the device tree blob; or having a different
kernel+device tree image for each FPGA bitstream. In the later case,
the kernel can be compiled once and then bound to multiple dt blobs
(creating multiple images)
>
> I am having some difficulty grasping the significant advantages to
> this.
> If the firmware for a given target is not fairly static - and I load
> different firmware depending on what I am doing all the time, then I
> know have to manage both a bit file for the firmware, and a devicetree
> file describing it to the kernel.
> Currently for base hardware we maintain as much design consistancy
> as possible accross all our different cards/firmware.
> particular hardware/firmware blocks/IP's may or may not be present -
> but if present they are always the same - the Same Uartlite at the same
> location, on the same irq, same for PIC's, TEMAC's ...
> For the most part it makes the most sense for us to use code to
> detect the presence/absence of specific baseline hardware and then to
> load non-base custom drivers after boot.
The board description has to live *somewhere*. For powerpc (and
microblaze) we've decided that for generic stuff, it makes sense to
use the device tree data structure to describe the hardware. It makes
the platform code simpler because the platform code no longer needs to
explicitly instantiate drivers for each device on the board. Instead
it registers part of the device tree with the of_platform bus and lets
the drivers handle binding themselves.
That being said, using the device tree does not preclude using
platform code to setup devices *where it makes sense to do so*. Many
things are one-off board specific things that are not well described
with the device tree. For example, we've been debating how to handle
on board sound which use common codec chips, but have custom wireup.
The codec chip can use a common driver, but the wireup is handled with
an ALSA 'fabric' driver that is pretty much a one-off for the board.
It probably makes more sense for the fabric driver to be instantiated
by the platform code rather than trying to do a full device tree
representation.
>
> What am missing about devicetrees that would make me more
> interested in them ?
To put it all in perspective, for Virtex support in arch/ppc
registration of devices is data driven. Look at
arch/ppc/syslib/virtex_devices.c which contains a table of platform
devices which the Virtex platform code iterates over. In arch/powerpc
we're *still* data driven; it's just that the data is no longer
compiled into a static structure. Plus, in the transition we've moved
from needed per-device platform data structures to a more expressive
format. Also, per-board platform support code has become much simpler
(compare ml300.c in arch/ppc with platforms/40x/virtex.c)
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
^ permalink raw reply
* shekr06@lzu.cn;puyq@lzu.cn;zhang_wei@lzu.cn
From: Bai Shuwei @ 2007-11-24 15:19 UTC (permalink / raw)
To: linuxppc-embedded, linuxppc-dev
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
hi, all
I bought a SMC1500 stepper motor card. And it can connect with host
through parallel port. My target board is PowerPC 440, which hasn't
parrallel port. So I bought a PCI to Parallel line for SMC1500. But when I
run the stepper motor, I find it's not stable. I doubt there are somthing
wrong with my PCI to Parallel line. So I beg somebody can tell me where I
can bought the appropriate conversion line from PCI to parallel, and does
somebody give me some idea about how to control my stepper motor
through PowerPC 440? thx all
Best Regards!
Buroc
--
Add: Tianshui South Road 222, Lanzhou, P.R.China
Tel: +86-931-8912025
Zip Code: 730000
URL: oss.lzu.edu.cn
Email: baishuwei@gmail.com, buroc@126.com
[-- Attachment #2: Type: text/html, Size: 1016 bytes --]
^ permalink raw reply
* Re: oops trying to execute sh
From: John Tyner @ 2007-11-24 14:26 UTC (permalink / raw)
To: linuxppc-dev
In-Reply-To: <Pine.LNX.4.64.0711211149210.3338@eon.cs.ucr.edu>
This is ppc. I'm in the midst of trying to get powerpc to boot, but our
boards are running an old version of ppcboot that can't be upgraded, so
I'm having to figure out the translation to the open firmware stuff.
By the way, this is an 860t, not c... typo.
Do you have any suggestions about getting ppc to boot? I'd like to try to
at least get the board booting so I can hand the user space stuff off to
someone else while I do the powerpc port.
Thanks,
John
> On Wed, 21 Nov 2007 11:54:01 -0800 (PST)
> John Charles Tyner wrote:
>
> > I'm trying to boot linux 2.6.22.9 on an mpc860c rev d4.
> >
> ppc or powerpc?
>
>
> > When init trys to spawn sh, during the exec, the kernel oopses as
> > seen below:
> This looks like coherency problem, or kernel picks wrong entry off
> cputable.
> I think I recall something similar when I lost a hunk applying patch for
> new e300 core.
> ... or not. The game across that ff8.. value is very confusing.
>
> --
> Sincerely, Vitaly
On Wed, Nov 21, 2007 at 11:54:01AM -0800, John Charles Tyner wrote:
> I'm trying to boot linux 2.6.22.9 on an mpc860c rev d4.
>
> When init trys to spawn sh, during the exec, the kernel oopses as seen
> below:
>
> ## Starting application at 0x00400000 ...
>
> loaded at: 00400000 004EF15C
> board data at: 03F9FBC0 03F9FBFC
> relocated to: 00404044 00404080
> zimage at: 00404E74 004EC662
> avail ram: 004F0000 04000000
>
> Linux/PPC load: console=ttyCPM,38400
> Uncompressing Linux...done.
> Now booting the kernel
> Linux version 2.6.22.9 (jtyner@johnnyedge) (gcc version 4.2.1) #113 Wed Nov
> 21 10:49:36 PST 2007
> Zone PFN ranges:
> DMA 0 -> 16384
> Normal 16384 -> 16384
> early_node_map[1] active PFN ranges
> 0: 0 -> 16384
> Built 1 zonelists. Total pages: 16256
> Kernel command line: console=ttyCPM,38400
> PID hash table entries: 256 (order: 8, 1024 bytes)
> Decrementer Frequency = 183750000/60
> Console: colour dummy device 80x25
> cpm_uart: console: compat mode
> Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
> Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
> Memory: 63244k available (880k kernel code, 268k data, 444k init, 0k
> highmem)
> Mount-cache hash table entries: 512
> ADDSI: Init
> io scheduler noop registered (default)
> Serial: CPM driver $Revision: 0.02 $
> ttyCPM0 at MMIO 0xc5000a80 (irq = 20) is a CPM UART
> mice: PS/2 mouse device common for all mice
> Freeing unused kernel memory: 444k init
> init started: BusyBox v1.8.0 (2007-11-16 14:24:51 PST)
> starting pid 103, tty '': '/bin/sh'
> Oops: kernel access of bad area, sig: 11 [#1]
> NIP: c0044ed0 LR: c0044ff0 CTR: 00000001
> REGS: c3c0bd00 TRAP: 0300 Not tainted (2.6.22.9)
> MSR: 00009032 <EE,ME,IR,DR> CR: 30099099 XER: a0008c7f
> DAR: ff80103f, DSISR: c0000000
> TASK = c0288070[103] 'init' THREAD: c3c0a000
> GPR00: c0044ff0 c3c0bdb0 c0288070 ff800fff 00000000 7faf8000 00000000
> 00000000
> GPR08: c01a8f58 c017d91c 00000002 c0179cd0 30099093 1007687c 00000002
> c00f8744
> GPR16: 00000000 c00f0a64 c011d1ac c00f0aa4 c00f0a90 c0120000 00000001
> 00000003
> GPR24: c3c1ce00 00000000 c0180000 c0247550 00000000 c3c0bdc8 c0179cd0
> ff800fff
> NIP [c0044ed0] remove_vma+0x14/0x70
> LR [c0044ff0] exit_mmap+0xc4/0xf0
> Call Trace:
> [c3c0bdb0] [c3c0bdc8] 0xc3c0bdc8 (unreliable)
> [c3c0bdc0] [c0044ff0] exit_mmap+0xc4/0xf0
> [c3c0bdf0] [c000f74c] mmput+0x50/0xd4
> [c3c0be00] [c00591f4] flush_old_exec+0x3b8/0x7a8
> [c3c0be50] [c0086cc0] load_elf_binary+0x2e8/0x1454
> [c3c0bee0] [c005892c] search_binary_handler+0x58/0x12c
> [c3c0bf00] [c0059d64] do_execve+0x13c/0x1f0
> [c3c0bf20] [c00089b4] sys_execve+0x50/0x90
> [c3c0bf40] [c0002a40] ret_from_syscall+0x0/0x38
> Instruction dump:
> 7d808120 38210040 4e800020 83c30000 4bffff18 38a00000 4bffff9c 7c0802a6
> 9421fff0 bfc10008 90010014 7c7f1b78 <81230040> 83c3000c 2f890000 419e0018
>
> The interesting thing is that r3 points to something funny. While tracing
> this problem down, I replaced the remove_vma function with the following:
>
> /*
> * Close a vm structure and free it, returning the next.
> */
> static struct vm_area_struct * __attribute__((__noinline__))
> __remove_vma(struct vm_area_struct *vma)
> {
>
> struct vm_area_struct *next = vma->vm_next;
>
> might_sleep();
> if (vma->vm_ops && vma->vm_ops->close)
> vma->vm_ops->close(vma);
> if (vma->vm_file)
> fput(vma->vm_file);
> mpol_free(vma_policy(vma));
> kmem_cache_free(vm_area_cachep, vma);
> return next;
> }
>
> static struct vm_area_struct *remove_vma(struct vm_area_struct *vma)
> {
> asm volatile (
> "lis 4,-128\n"
> "ori 4,4,4095\n"
> "tweq 3,4\n"
> "lwz 5,0(1)\n"
> "tweq 3,4\n"
> );
> return __remove_vma( vma );
> }
>
> With this code, the kernel oopses on the *second* tweq instruction:
>
> Kernel BUG at c0045fd4 [verbose debug info unavailable]
> Oops: Exception in kernel mode, sig: 5 [#1]
> NIP: c0045fd4 LR: c00460a0 CTR: 00000001
> REGS: c3c0bd10 TRAP: 0700 Not tainted (2.6.22.9)
> MSR: 00029032 <EE,ME,IR,DR> CR: 30099099 XER: a0008c7f
> TASK = c0292b40[103] 'init' THREAD: c3c0a000
> GPR00: 00000001 c3c0bdc0 c0292b40 ff800fff ff800fff c3c0bdf0 00000000
> 00000000
> GPR08: c0219398 c017d91c 00000002 c0179cd0 30099093 1007687c 00000002
> c00f8744
> GPR16: 00000000 c00f0a64 c011d1ac c00f0aa4 c00f0a90 c0120000 00000001
> 00000003
> GPR24: c3c32e00 00000000 c0180000 c0247080 00000000 c3c0bdc8 c0179cd0
> c017641c
> NIP [c0045fd4] remove_vma+0x10/0x18
> LR [c00460a0] exit_mmap+0xc4/0xf0
> Call Trace:
> [c3c0bdc0] [c0046074] exit_mmap+0x98/0xf0 (unreliable)
> [c3c0bdf0] [c000f74c] mmput+0x50/0xd4
> [c3c0be00] [c005920c] flush_old_exec+0x3b8/0x7a8
> [c3c0be50] [c0086cd8] load_elf_binary+0x2e8/0x1454
> [c3c0bee0] [c0058944] search_binary_handler+0x58/0x12c
> [c3c0bf00] [c0059d7c] do_execve+0x13c/0x1f0
> [c3c0bf20] [c00089b4] sys_execve+0x50/0x90
> [c3c0bf40] [c0002a40] ret_from_syscall+0x0/0x38
> Instruction dump:
> 7fe4fb78 4800a0ed 80010014 7fc3f378 7c0803a6 bbc10008 38210010 4e800020
> 3c80ff80 60840fff 7c832008 80a10000 <7c832008> 4bffff7c 7c0802a6 9421ffd0
>
> The access of memory through r1 seems to corrupt r3, and always with the
> same value. The problem isn't necessarily here, though. If I modify my
> remove_vma function to cause and correct the problem (by saving r3 prior
> to the memory access and restoring it afterwards), I just get the same
> problem in some other part of the code, but the oops is always caused
> because the base register for some memory access is set to ff800fff.
>
> I applied a recent patch I found that corrects the address returned by
> cpm_dpram_addr and its use in cpu_uart_cpm1.h, and I've created my own
> platform setup file by copying the mpc866ads setup enough to get the
> console uart (SMC1) to work.
>
> If there is any other information I can or need to provide, let me
> know. Any help would be greatly appreciated.
>
> Thanks,
> John
--
John Tyner
jtyner@cs.ucr.edu
^ permalink raw reply
* Xilinx devicetrees
From: David H. Lynch Jr. @ 2007-11-24 11:37 UTC (permalink / raw)
To: linuxppc-embedded
I am following developments regarding device trees for xilinx boards
both here and on the microblaze list.
I am trying to get a grasp on what they will really do for me and
what using them will demand.
Please correct any misperceptions:
As I understand it devicetrees are basically just a tree structured
binary database describing the hardware.
They have some heritage in OpenFirmware.
There are tools to convert some human readable representations into
the binary form.
There appear to be tools to take xilinx firmware projects and create
a devicetree database from it
A BSP using devicetree's configures its hardware, drivers etc, by
querying the devicetree database.
It it possible to pass the device tree database independent of the
kernel itself some what similar to the way many bootloaders pass initrd
filesystems.
So in the end I write a BSP that could support a wide variety of
hardware and compile a single kernel that could be passed different
devicetree databases representing different xilinx firmware, and still
hope to work.
But in return for making the BSP more generic (sort of), I now have
to somehow get the correct devicetree database passed for each different
firmware set that I load.
I am having some difficulty grasping the significant advantages to
this.
If the firmware for a given target is not fairly static - and I load
different firmware depending on what I am doing all the time, then I
know have to manage both a bit file for the firmware, and a devicetree
file describing it to the kernel.
Currently for base hardware we maintain as much design consistancy
as possible accross all our different cards/firmware.
particular hardware/firmware blocks/IP's may or may not be present -
but if present they are always the same - the Same Uartlite at the same
location, on the same irq, same for PIC's, TEMAC's ...
For the most part it makes the most sense for us to use code to
detect the presence/absence of specific baseline hardware and then to
load non-base custom drivers after boot.
What am missing about devicetrees that would make me more
interested in them ?
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
^ permalink raw reply
* Re: [RFC][PATCH 0/3] OF-platform PATA driver
From: Paul Mundt @ 2007-11-24 7:26 UTC (permalink / raw)
To: Jeff Garzik; +Cc: linuxppc-dev, linux-ide
In-Reply-To: <4747751D.4060802@garzik.org>
On Fri, Nov 23, 2007 at 07:49:33PM -0500, Jeff Garzik wrote:
> Anton Vorontsov wrote:
> >Here is the PATA Platform driver using OF infrastructure.
> >
> >Mostly it's just a wrapper around a bit modified pata_platform
> >driver.
> >
> >Patches are well split for the easier review:
> >
> >First one factors out platform_device specific bits and modifies
> >pata_platform to be a library-alike driver (with platform_device
> >default binding).
> >
The only issue I have here is that this library-like version has subtle
semantic changes that will break existing drivers.
irq_flags exists in struct pata_platform_info precisely for the IRQ
resource IRQ flags (as opposed to the IORESOURCE flags, which are what
the IRQ resource flags refer to instead). This change takes that for
granted and just assumes we're going to be using the res->flags, which is
both an invalid assumption, and will utterly break blackfin and others
that depend on it.
Incidentally, we already have an include/linux/pata_platform.h. If this
is going to be library-like, through the prototypes in there, rather than
splitting them up betewen include/linux and drivers/ata. We don't need
two headers.
These patches basically look fine to me otherwise, though it would be
nice if the semantic-changing bits had been abstracted. So as long as the
old irq_flags behaviour is maintained and that irq_res->flags stuff is
ripped out, I'll add my Acked-by as well.
^ permalink raw reply
* RE: Xilinx Linux git server available
From: Stephen Neuendorffer @ 2007-11-24 5:54 UTC (permalink / raw)
To: Peter Korsgaard, Grant Likely; +Cc: linuxppc-dev, Wolfgang Reissnegger
In-Reply-To: <87wssae11t.fsf@macbook.be.48ers.dk>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
It was the edk-derived driver for the uartlite.. The functionality is now provided by the open source driver.
Steve
-----Original Message-----
From: linuxppc-dev-bounces+stephen.neuendorffer=xilinx.com@ozlabs.org on behalf of Peter Korsgaard
Sent: Thu 11/22/2007 7:45 AM
To: Grant Likely
Cc: linuxppc-dev@ozlabs.org; Wolfgang Reissnegger
Subject: Re: Xilinx Linux git server available
>>>>> "Grant" == Grant Likely <grant.likely@secretlab.ca> writes:
Hi,
>> Ok, I had a quick look at the tree and saw a uartlite-alternative.c -
>> What's that about?
Grant> What directory is that in? I had looked in drivers/serial and only
Grant> saw uartlite.c:
It's gone now (I accidently ended up browsing an earlier version
before):
http://git.xilinx.com/cgi-bin/gitweb.cgi?p=linux-2.6-xlnx.git;a=commit;h=9912d5bf98f969324e1d4f12210adccd1530de68
--
Bye, Peter Korsgaard
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
[-- Attachment #2: Type: text/html, Size: 1849 bytes --]
^ permalink raw reply
* Re: [PATCH 1/5] USB: Make usb_hcd_irq work for multi-role USB controllers w/ shared irq
From: Greg KH @ 2007-11-24 5:10 UTC (permalink / raw)
To: Grant Likely; +Cc: akpm, linuxppc-dev, dbrownell, linux-usb-devel
In-Reply-To: <20071124002431.25361.23974.stgit@trillian.cg.shawcable.net>
On Fri, Nov 23, 2007 at 05:24:31PM -0700, Grant Likely wrote:
> From: Peter Korsgaard <peter.korsgaard@barco.com>
>
> Some multi-role (host/peripheral) USB controllers use a shared interrupt
> line for all parts of the chip. Export usb_hcd_irq so drivers can call it
> from their interrupt handler instead of duplicating code.
> Drivers pass an irqnum of 0 to usb_add_hcd to signal that the interrupt handler
> shouldn't be registerred by the core.
What about for platforms where irq 0 is a valid irq?
thanks,
greg k-h
^ permalink raw reply
* Re: [linux-usb-devel] [PATCH 4/5] USB: add Cypress c67x00 OTG controller HCD driver
From: Alan Stern @ 2007-11-24 3:56 UTC (permalink / raw)
To: Grant Likely; +Cc: akpm, linuxppc-dev, dbrownell, linux-usb-devel, gregkh
In-Reply-To: <20071124002446.25361.88850.stgit@trillian.cg.shawcable.net>
On Fri, 23 Nov 2007, Grant Likely wrote:
> From: Grant Likely <grant.likely@secretlab.ca>
>
> This patch adds HDC support for the Cypress c67x00 family of devices.
>
> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> +static void c67x00_sched_done(unsigned long __c67x00)
> +{
> + struct c67x00_hcd *c67x00 = (struct c67x00_hcd *)__c67x00;
> + struct c67x00_urb_priv *urbp, *tmp;
> + struct usb_hcd *hcd = c67x00_hcd_to_hcd(c67x00);
> + struct urb *urb;
> + int status;
> +
> + spin_lock(&c67x00->lock);
> +
> + /* Loop over the done list and give back all the urbs */
> + list_for_each_entry_safe(urbp, tmp, &c67x00->done_list, hep_node) {
> + urb = urbp->urb;
> + status = urbp->status;
> +
> + c67x00_release_urb(c67x00, urb);
> +
> + usb_hcd_unlink_urb_from_ep(hcd, urb);
> + usb_hcd_giveback_urb(hcd, urb, status);
> + }
> + spin_unlock(&c67x00->lock);
> +}
You need to release the spinlock around the call to
usb_hcd_giveback_urb(). Otherwise you will deadlock if the completion
routine submits another URB.
Alan Stern
^ permalink raw reply
* Re: [PATCH 1/2][2.6.24] ehea: Improve tx packets counting
From: Jeff Garzik @ 2007-11-24 3:09 UTC (permalink / raw)
To: Thomas Klein
Cc: Jan-Bernd Themann, netdev, linux-kernel, linux-ppc,
Christoph Raisch, Marcus Eder, Stefan Roscher
In-Reply-To: <200711211737.58789.osstklei@de.ibm.com>
Thomas Klein wrote:
> Using own tx_packets counter instead of firmware counters.
>
> Signed-off-by: Thomas Klein <tklein@de.ibm.com>
>
> ---
> drivers/net/ehea/ehea.h | 2 +-
> drivers/net/ehea/ehea_main.c | 9 +++++++--
> 2 files changed, 8 insertions(+), 3 deletions(-)
applies 1-2 to #upstream-fixes
^ permalink raw reply
* Re: [PATCH] e1000: Fix for 32 bits platforms with 64 bits resources
From: Jeff Garzik @ 2007-11-24 2:52 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: netdev, auke-jan.h.kok, linuxppc-dev
In-Reply-To: <20071116073821.548CCDDDF4@ozlabs.org>
Benjamin Herrenschmidt wrote:
> The e1000 driver stores the content of the PCI resources into
> unsigned long's before ioremapping. This breaks on 32 bits
> platforms that support 64 bits MMIO resources such as ppc 44x.
>
> This fixes it by removing those temporary variables and passing
> directly the result of pci_resource_start/len to ioremap.
>
> The side effect is that I removed the assignments to the netdev
> fields mem_start, mem_end and base_addr, which are totally useless
> for PCI devices.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> --
>
> drivers/net/e1000/e1000_main.c | 18 +++++-------------
> 1 file changed, 5 insertions(+), 13 deletions(-)
Looks good to me. auke?
^ permalink raw reply
* Re: [RFC][PATCH 0/3] OF-platform PATA driver
From: Vitaly Bordug @ 2007-11-24 2:35 UTC (permalink / raw)
To: avorontsov; +Cc: Benjamin, linuxppc-dev, linux-ide
In-Reply-To: <20071123175229.GA27143@localhost.localdomain>
On Fri, 23 Nov 2007 20:52:29 +0300
Anton Vorontsov wrote:
> Hi all,
>
> Here is the PATA Platform driver using OF infrastructure.
>
> Mostly it's just a wrapper around a bit modified pata_platform
> driver.
>
> Patches are well split for the easier review:
>
> First one factors out platform_device specific bits and modifies
> pata_platform to be a library-alike driver (with platform_device
> default binding).
>
> Second patch is OF-driver itself which is using pata_platform
> "library".
>
> Third patch is PowerPC specific, but I'm still Cc'ing linux-ide,
> just to show how we're using it.
>
>
> As an alternative approach we can use plain pata_platform
> driver, but I'm not sure how Linux OF bindings' ideologists will
> or will not like it.
>
> So, these patches are strongly Request For Comments. Feel free
> to train your nitpicking skills ;-), and/or vote for the option
> you most pleased about (or suggest another?).
>
I vote for of_platform_device, since we seem to dodge the clash
with platform_device here.
The code looks good, so I'm going to ack all 3 patches and if there will
be no more nagging, I'm inclined to ask Kumar to queue this for the next merge window.
--
Sincerely, Vitaly
^ permalink raw reply
* Re: [PATCH] ibm_newemac: Fix possible lockup on close
From: Jeff Garzik @ 2007-11-24 1:52 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: linuxppc-dev, netdev
In-Reply-To: <20071120035134.970DCDDE9E@ozlabs.org>
Benjamin Herrenschmidt wrote:
> It's a bad idea to call flush_scheduled_work from within a
> netdev->stop because the linkwatch will occasionally take the
> rtnl lock from a workqueue context, and thus that can deadlock.
>
> This reworks things a bit in that area to avoid the problem.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
>
applied #upstream-fixes (2.6.24-rc)
^ permalink raw reply
* Re: [PATCH 0/8] ibm_newemac: Candidate patches for 2.6.25
From: Jeff Garzik @ 2007-11-24 1:43 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: netdev, linuxppc-dev
In-Reply-To: <1195625198.76200.922309668615.qpush@grosgo>
Benjamin Herrenschmidt wrote:
> Here are the patches I have pending for EMAC. With some non-released
> patches from Hugh Blemings, I get a taishan (440GX) booting now,
> in addition to Ebony (440GP) and various 405GP boards.
>
> This is 2.6.25 material except for patch #1 which has already been
> posted separately and is candidate for 2.6.24 (and possibly stable)
dropping (waiting for resend), as requested
^ permalink raw reply
* Re: [PATCH 0/3] PowerPC: ibm_newemac minor fixes.
From: Benjamin Herrenschmidt @ 2007-11-24 1:31 UTC (permalink / raw)
To: Jeff Garzik; +Cc: linuxppc-dev, netdev
In-Reply-To: <47477C55.8090209@garzik.org>
On Fri, 2007-11-23 at 20:20 -0500, Jeff Garzik wrote:
> Benjamin Herrenschmidt wrote:
> > On Fri, 2007-11-23 at 22:07 +0300, Valentine Barshak wrote:
> >
> >> These patches have some minor ibm_newemac fixes.
> >
> > All 3 patches look good, thanks. I'll sign them off and forward them
> > to Jeff in my next batch.
> >
> > Jeff, did you already pick up my previous drop of EMAC patches from last
> > week for .25 or not ? If not, I will resend the whole lot along with
> > Valentine's patches sometime next week.
>
> Just got back from Thanksgiving holiday, and am about to go through the
> lot that's sitting in my inbox.
>
> Just let me know what you would prefer me to do, starting from today.
Then wait for my next batch and ignore previous patches, except the
one titled "ibm_newemac: Fix possible lockup on close" which is a 2.6.24
bug fix.
Thanks !
Cheers,
Ben.
^ permalink raw reply
* Re: [RFC][PATCH 0/3] OF-platform PATA driver
From: Benjamin Herrenschmidt @ 2007-11-24 1:23 UTC (permalink / raw)
To: avorontsov; +Cc: linuxppc-dev, linux-ide
In-Reply-To: <20071123175229.GA27143@localhost.localdomain>
On Fri, 2007-11-23 at 20:52 +0300, Anton Vorontsov wrote:
> As an alternative approach we can use plain pata_platform
> driver, but I'm not sure how Linux OF bindings' ideologists will
> or will not like it.
>
> So, these patches are strongly Request For Comments. Feel free
> to train your nitpicking skills ;-), and/or vote for the option
> you most pleased about (or suggest another?).
>
>
> Thanks.
>
> ---
> Down here is "alternative approach".
>
> Probably board-neutral version may be placed somewhere in
> the drivers/of/...? But who will call it: board file, or
> device_initcall for all boards?
.../...
I'm fine with either approaches in fact. I think it's fair enough when
there is existing platform devices to avoid duplicating the whole thing
for an of_platform_device (unless you find a nice way to split to a
library like you just did) and instead, have a "constructor" that
constructs the platform device based on the OF node.
Now, as you pointed out, the question is where to call it... the
initcall has the problem of potentially being called for the wrong board
and the thing having duplicate OF device and platform device created for
it...
One of the thing I've been brewing in my mind is the idea of reworking
the current code that create OF platform devices when walking busses
down, and have it instead call registered constructor functions. The
default ones would then create OF platform devices but one could
override that with constructors creating something else (such as a
platform device).
Now, it's not trivial, as there is a bit of a mixup on whether a "bus"
should create all children and thus define their type (PCI would do such
a thing) or whether the type is defined by the device object itself
which typically would be the case for "generic" busses such as SoCs or
PLBs when creating platform devices. I haven't quite found out a nice
way to enable both possibilities... if you have ideas, please share.
In the meantime, maybe it's best to merge the of_platform_device
approach since Jeff agrees with it.
Cheers,
Ben.
^ permalink raw reply
* Re: [PATCH 0/3] PowerPC: ibm_newemac minor fixes.
From: Jeff Garzik @ 2007-11-24 1:20 UTC (permalink / raw)
To: benh; +Cc: linuxppc-dev, netdev
In-Reply-To: <1195867102.7195.31.camel@pasglop>
Benjamin Herrenschmidt wrote:
> On Fri, 2007-11-23 at 22:07 +0300, Valentine Barshak wrote:
>
>> These patches have some minor ibm_newemac fixes.
>
> All 3 patches look good, thanks. I'll sign them off and forward them
> to Jeff in my next batch.
>
> Jeff, did you already pick up my previous drop of EMAC patches from last
> week for .25 or not ? If not, I will resend the whole lot along with
> Valentine's patches sometime next week.
Just got back from Thanksgiving holiday, and am about to go through the
lot that's sitting in my inbox.
Just let me know what you would prefer me to do, starting from today.
Jeff
^ permalink raw reply
* Re: [PATCH 0/3] PowerPC: ibm_newemac minor fixes.
From: Benjamin Herrenschmidt @ 2007-11-24 1:18 UTC (permalink / raw)
To: Valentine Barshak; +Cc: linuxppc-dev, jgarzik, netdev
In-Reply-To: <20071123190747.GA25654@ru.mvista.com>
On Fri, 2007-11-23 at 22:07 +0300, Valentine Barshak wrote:
> These patches have some minor ibm_newemac fixes.
All 3 patches look good, thanks. I'll sign them off and forward them
to Jeff in my next batch.
Jeff, did you already pick up my previous drop of EMAC patches from last
week for .25 or not ? If not, I will resend the whole lot along with
Valentine's patches sometime next week.
Cheers,
Ben.
^ permalink raw reply
* Re: [RFC][PATCH 0/3] OF-platform PATA driver
From: Jeff Garzik @ 2007-11-24 0:49 UTC (permalink / raw)
To: avorontsov; +Cc: linuxppc-dev, Paul Mundt, linux-ide
In-Reply-To: <20071123175229.GA27143@localhost.localdomain>
Anton Vorontsov wrote:
> Hi all,
>
> Here is the PATA Platform driver using OF infrastructure.
>
> Mostly it's just a wrapper around a bit modified pata_platform
> driver.
>
> Patches are well split for the easier review:
>
> First one factors out platform_device specific bits and modifies
> pata_platform to be a library-alike driver (with platform_device
> default binding).
>
> Second patch is OF-driver itself which is using pata_platform
> "library".
>
> Third patch is PowerPC specific, but I'm still Cc'ing linux-ide,
> just to show how we're using it.
>
>
> As an alternative approach we can use plain pata_platform
> driver, but I'm not sure how Linux OF bindings' ideologists will
> or will not like it.
>
> So, these patches are strongly Request For Comments. Feel free
> to train your nitpicking skills ;-), and/or vote for the option
> you most pleased about (or suggest another?).
Seems reasonable from a libata point of view...
(pata_platform maintainer CC'd)
Jeff
^ permalink raw reply
* [PATCH 5/5] USB: Add Cypress c67x00 OTG controller driver to Kconfig and Makefiles
From: Grant Likely @ 2007-11-24 0:24 UTC (permalink / raw)
To: linux-usb-devel, akpm, dbrownell, gregkh, linuxppc-dev
In-Reply-To: <20071124001203.25361.99294.stgit@trillian.cg.shawcable.net>
From: Grant Likely <grant.likely@secretlab.ca>
add c67x00 driver to build
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
---
drivers/usb/Kconfig | 2 ++
drivers/usb/Makefile | 2 ++
drivers/usb/c67x00/Kconfig | 22 ++++++++++++++++++++++
drivers/usb/c67x00/Makefile | 14 ++++++++++++++
4 files changed, 40 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/Kconfig b/drivers/usb/Kconfig
index 7580aa5..a497f96 100644
--- a/drivers/usb/Kconfig
+++ b/drivers/usb/Kconfig
@@ -91,6 +91,8 @@ source "drivers/usb/core/Kconfig"
source "drivers/usb/host/Kconfig"
+source "drivers/usb/c67x00/Kconfig"
+
source "drivers/usb/class/Kconfig"
source "drivers/usb/storage/Kconfig"
diff --git a/drivers/usb/Makefile b/drivers/usb/Makefile
index 516a640..a1ae51d 100644
--- a/drivers/usb/Makefile
+++ b/drivers/usb/Makefile
@@ -17,6 +17,8 @@ obj-$(CONFIG_USB_SL811_HCD) += host/
obj-$(CONFIG_USB_U132_HCD) += host/
obj-$(CONFIG_USB_R8A66597_HCD) += host/
+obj-$(CONFIG_USB_C67X00_DRV) += c67x00/
+
obj-$(CONFIG_USB_ACM) += class/
obj-$(CONFIG_USB_PRINTER) += class/
diff --git a/drivers/usb/c67x00/Kconfig b/drivers/usb/c67x00/Kconfig
new file mode 100644
index 0000000..efd7923
--- /dev/null
+++ b/drivers/usb/c67x00/Kconfig
@@ -0,0 +1,22 @@
+#
+# Cypress C67x00 USB controller
+#
+config USB_C67X00_DRV
+ tristate "Cypress C67x00 support"
+ # only allowed to be =y if both USB!=m and USB_GADGET!=m
+ depends on (!USB && USB_GADGET) || (!USB_GADGET && USB) || (USB && USB_GADGET)
+ default n
+ help
+ The Cypress C67x00 (EZ-Host/EZ-OTG) chips are dual-role
+ host/peripheral USB controllers.
+
+ To compile this driver as a module, choose M here: the
+ module will be called c67x00.
+
+config USB_C67X00_HCD
+ bool "Cypress C67X00 Host support"
+ depends on USB_C67X00_DRV
+ depends on USB
+ default y
+ help
+ This enables the host functionality of the Cypress C67X00.
diff --git a/drivers/usb/c67x00/Makefile b/drivers/usb/c67x00/Makefile
new file mode 100644
index 0000000..8ff5cd0
--- /dev/null
+++ b/drivers/usb/c67x00/Makefile
@@ -0,0 +1,14 @@
+#
+# Makefile for Cypress C67X00 USB Controller
+#
+
+ifeq ($(CONFIG_USB_DEBUG),y)
+ EXTRA_CFLAGS += -DDEBUG
+endif
+
+obj-$(CONFIG_USB_C67X00_DRV) += c67x00.o
+
+c67x00-y += c67x00-drv.o
+c67x00-y += c67x00-ll-hpi.o
+
+c67x00-$(CONFIG_USB_C67X00_HCD) += c67x00-hcd.o c67x00-sched.o
^ permalink raw reply related
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox