- 12 Jun, 2009 40 commits
-
-
Graf Yang authored
For systems where the core cycles are not a usable tick source (like SMP or cycles gets updated), enable gptimer0 as an alternative. Signed-off-by:
Graf Yang <graf.yang@analog.com> Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
Graf Yang authored
Add some notes for anomaly 05000120 to make sure we work around it. Signed-off-by:
-
Graf Yang authored
The two high address lines on the BF51x are not dedicated which means we need to handle them like any other peripheral pin if we want to access the upper 2MB of parallel flash. Signed-off-by:
-
Sonic Zhang authored
Detect and reject operating conditions for anomaly 05000274 since the problem cannot be worked around in software. Signed-off-by:
Sonic Zhang <sonic.zhang@analog.com> Signed-off-by:
-
Mike Frysinger authored
The panic() function already handles newlines for us. Signed-off-by: -
Mike Frysinger authored
Workaround anomaly 05000227 by only using the scratch pad for stack when absolutely necessary. The core code which reprograms clocks really only touches MMRs directly with constants. Signed-off-by: -
Mike Frysinger authored
Signed-off-by: -
Graf Yang authored
Make sure we work around anomaly 05000287 by configuring different port preferences for the data cache. Signed-off-by:
-
Mike Frysinger authored
This init code existed only to dump a printk(), and not even a useful one. Signed-off-by: -
Robin Getz authored
Add a reminder note to avoid the DMA_DONE bit in our DMA core code. Signed-off-by:
Robin Getz <robin.getz@analog.com> Signed-off-by:
-
Robin Getz authored
Note the reason for using CHIPD over DSPID. Signed-off-by:
-
Robin Getz authored
Our early L1 relocate code may implicitly call code which lives in L1 memory. This is due to the dma_memcpy() rewrite that made the DMA code lockless and safe to be used by multiple processes. If we start the early DMA memcpy to relocate things into L1 instruction but then our DMA memcpy code calls a function that lives in L1, things fall apart. As such, create a small dedicated DMA memcpy routine that we can assume sanity at boot time. Reported-by:
Filip Van Rillaer <filip.vanrillaer@oneaccess-net.com> Signed-off-by:
-
Graf Yang authored
Add some defines to make the BF538/BF561 look like most other Blackfin parts in that it has a MDMA0 channel available for low level init. Signed-off-by:
-
Mike Frysinger authored
Make sure our bfin_addr_dcachable() function flags cached L2 SRAM properly else memory easily goes unflushed when working with DMA. Signed-off-by: -
Mike Frysinger authored
Since 90% of this driver can be handled in user space, move it to the corebld user space application. Signed-off-by: -
Sonic Zhang authored
Signed-off-by:
Bryan Wu <cooloney@kernel.org>
-
Mike Frysinger authored
Simplify the do_flush macro now that we don't need to take into account a second instruction being used together. Signed-off-by:
-
Mike Frysinger authored
Update the default revs based on what we actually support (bf54x-0.[01] is too broken to use). Signed-off-by:
-
Michael Hennerich authored
Some drivers expect to be able to request both as GPIO and GPIO IRQ, so allow that use case. Signed-off-by:
Michael Hennerich <michael.hennerich@analog.com> Signed-off-by:
-
Mike Frysinger authored
Signed-off-by:
-
Michael Hennerich authored
Make sure the addresses declared match reality, and make the PATA IRQ code optional. Signed-off-by:
-
Philippe Gerum authored
ipipe-2.6.28.9-blackfin-git95aafe6.patch Singed-off-by:
Philippe Gerum <rpm@xenomai.org> Signed-off-by:
Yi Li <yi.li@analog.com> Signed-off-by:
-
Mike Frysinger authored
The I/O port functions take ints, so we need to cast them up before passing to our read/write funcs to avoid ugly messes of warnings. Signed-off-by:
-
Mariusz Kozlowski authored
Signed-off-by:
Mariusz Kozlowski <m.kozlowski@tuxland.pl> Signed-off-by:
-
Graf Yang authored
The traps test case 21 "exception 0x3f: l1_instruction_access" would make the kernel panic on BF533's because we end up calling show_stack() infinitely. Signed-off-by:
-
Mike Frysinger authored
Make sure we flush all data caches and their write buffers before flushing icache, otherwise random edge cases could crop up where stale data is read into icache from external memory. As fallout, punt the combined icache + dcache flush function since we cannot safely do them back to back -- the SSYNC is needed between the dcache flush and the icache flush. Signed-off-by:
-
Graf Yang authored
Move exception stack mess from entry.S to init.c to fix link failure when CONFIG_EXCEPTION_L1_SCRATCH is in use. Signed-off-by:
-
Robin Getz authored
Signed-off-by:
Robin Getz <rgetz@blackfin.uclinux.org> Signed-off-by:
-
Sonic Zhang authored
By default, it is routed to async memory address. In GPIO case, GPIO peripheral PINs should be requested in advance. Signed-off-by:
-
Yi Li authored
Signed-off-by:
-
Mike Frysinger authored
Signed-off-by:
-
Michael Hennerich authored
Signed-off-by:
-
Randy Dunlap authored
Fix kernel-doc warnings in recently changed block/ source code. Signed-off-by:
Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org>
-
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6Linus Torvalds authored
* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6: (87 commits) nilfs2: get rid of bd_mount_sem use from nilfs nilfs2: correct exclusion control in nilfs_remount function nilfs2: simplify remaining sget() use nilfs2: get rid of sget use for checking if current mount is present nilfs2: get rid of sget use for acquiring nilfs object nilfs2: remove meaningless EBUSY case from nilfs_get_sb function remove the call to ->write_super in __sync_filesystem nilfs2: call nilfs2_write_super from nilfs2_sync_fs jffs2: call jffs2_write_super from jffs2_sync_fs ufs: add ->sync_fs sysv: add ->sync_fs hfsplus: add ->sync_fs hfs: add ->sync_fs fat: add ->sync_fs ext2: add ->sync_fs exofs: add ->sync_fs bfs: add ->sync_fs affs: add ->sync_fs sanitize ->fsync() for affs repair bfs_write_inode(), switch bfs to simple_fsync() ...
-
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommuLinus Torvalds authored
* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu: m68knommu: remove unecessary include of thread_info.h in entry.S m68knommu: enumerate INIT_THREAD fields properly headers_check fix: m68k, swab.h arch/m68knommu: Convert #ifdef DEBUG printk(KERN_DEBUG to pr_debug( m68knommu: remove obsolete reset code m68knommu: move CPU reset code for the 5272 ColdFire into its platform code m68knommu: move CPU reset code for the 528x ColdFire into its platform code m68knommu: move CPU reset code for the 527x ColdFire into its platform code m68knommu: move CPU reset code for the 523x ColdFire into its platform code m68knommu: move CPU reset code for the 520x ColdFire into its platform code m68knommu: add CPU reset code for the 532x ColdFire m68knommu: add CPU reset code for the 5249 ColdFire m68knommu: add CPU reset code for the 5206e ColdFire m68knommu: add CPU reset code for the 5206 ColdFire m68knommu: add CPU reset code for the 5407 ColdFire m68knommu: add CPU reset code for the 5307 ColdFire m68knommu: merge system reset for code ColdFire 523x family m68knommu: fix system reset for ColdFire 527x family
-
Yinghai Lu authored
zalloc_cpumask_var already cleared it. Signed-off-by:
Yinghai Lu <yinghai@kernel.org> Signed-off-by:
-
Yinghai Lu authored
So we make sure MAXSMP gets a cleared cpumask Signed-off-by:
-
Stephen Rothwell authored
Commit 925d519a ("perf_counter: unify and fix delayed counter wakeup") added global definitions. Signed-off-by:
Stephen Rothwell <sfr@canb.auug.org.au> Acked-by:
Paul Mackerras <paulus@samba.org> Acked-by:
Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Ryusuke Konishi authored
This will remove every bd_mount_sem use in nilfs. The intended exclusion control was replaced by the previous patch ("nilfs2: correct exclusion control in nilfs_remount function") for nilfs_remount(), and this patch will replace remains with a new mutex that this inserts in nilfs object. Signed-off-by:Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> Cc: Christoph Hellwig <hch@infradead.org> Signed-off-by:
Al Viro <viro@zeniv.linux.org.uk>
-
Ryusuke Konishi authored
nilfs_remount() changes mount state of a superblock instance. Even though nilfs accesses other superblock instances during mount or remount, the mount state was not properly protected in nilfs_remount(). Moreover, nilfs_remount() has a lock order reversal problem; nilfs_get_sb() holds: 1. bdev->bd_mount_sem 2. sb->s_umount (sget acquires) and nilfs_remount() holds: 1. sb->s_umount (locked by the caller in vfs) 2. bdev->bd_mount_sem To avoid these problems, this patch divides a semaphore protecting super block instances from nilfs->ns_sem, and applies it to the mount state protection in nilfs_remount(). With this change, bd_mount_sem use is removed from nilfs_remount() and the lock order reversal will be resolved. And the new rw-semaphore, nilfs->ns_super_sem will properly protect the mount state except the modification from nilfs_error function. Signed-off-by:
-
