Android samsung 2.6.35 #1

fascinate has much smaller nand than epic does match it to other sgs devices, with a nice healthy sized radio partition Change-Id: I2c781149b8dbb488f9726bb12373b4eb77e7b0cf

use cdma modemctl drivers, configurable with CONFIG_PHONE_ARIES_CDMA modemctl gpio fixes so modem will actually try to init needs mucho more work Change-Id: I13c08e472a58a3341182eef794e9ed752694c170

Change-Id: Id287eab340ade995727e6ac25d324f5f32c268fb

This reverts commit 8aa8fd1.

Change-Id: I3d114a550d10ec681ffb5c3d85854910114e8bd1

Change-Id: I99daa6e19d7f6cb0db64e192e2fd2115324c54ed

Change-Id: Ie4e5e9e913381d373f79a7ee1e319504a8d01337

Change-Id: I71b8b80c8c1fde8080d858c0e13e67108ba3cb83

Change-Id: I6efdadede02154f11c78d5179687b95fbe63e49e

Change-Id: Icc6f3008393cc2dee2112145a973f0254cc5c862

…g/android_kernel_samsung_aries into HEAD

Fix build.sh shebang

Fascinate merge.

Change-Id: I7dc808f49cbe8ffd77bfaa27137f83abce30bee0

Change-Id: Id74073a865d66051dd9a54f8772e738cad5c7ebd

Change-Id: I9a1ba582e1f9e2eb97f36a897326063f614fc4c1

Change-Id: Ieb8f51a89ab73a0cfcbcfd075cc2c1442c269024

use cdma modemctl drivers, configurable with CONFIG_PHONE_ARIES_CDMA modemctl gpio fixes so modem will actually try to init needs mucho more work Change-Id: I13c08e472a58a3341182eef794e9ed752694c170

This reverts commit 8aa8fd1.

Change-Id: I3d114a550d10ec681ffb5c3d85854910114e8bd1

Change-Id: Ibe06634cf0d4aca761954ac660a0cdb1b42bf5a1

…g/android_kernel_samsung_aries into android-samsung-2.6.35

Change-Id: Iaf8cd08535e9be21a0c4d1d7e938a7018fa289ca

Making sure that Rx pkt is acknowledged and sent to network interface by wifi driver before system goes in suspend. BUG ID 767438 Change-Id: Ie88176ec11aa1d2fe4253d9b0472d13a4742d300 Reviewed-on: http://git-master/r/12703 Reviewed-by: Rakesh Kumar <[email protected]> Reviewed-by: Bharat Nihalani <[email protected]> Tested-by: Bharat Nihalani <[email protected]>

Change-Id: Ic4b75bb874ecb31aa56bec330739bf6ea61c637e

remove other modem drivers, and fix dpram irq settings I screwed up Change-Id: Icf42e2942d18c10263c6617ac68be3679c319c3d

additional ppp options for cdma kill ubernoisy debug in dpram Change-Id: I8f46e0ed11f937498a2c891bac6268ffbf1830bd

Change-Id: Ia3fc856a7d321ee68058f0baf2229e4cfbab3860

Change-Id: I6325ea7ced0efb77115a3e703508da91d2df35f0

Change-Id: Ib0cd1f624eb8565ac414a49fb4050990f61b7307

Change-Id: I3131862164349cbc504d652adc1ffe05c8025889

…g/android_kernel_samsung_aries into android-samsung-2.6.35

…e to /cache and /system Change-Id: I06c13697230cff5c7dd58bd90f0dfa2286e99d55

Change-Id: Icfaba0f835cae6be4d6619c5d216ab7c63a89f88

Change-Id: I47572a68f0106c260e7f719139ce3087c8c6d70d

Change-Id: I2820ef250e55fe963b4d491545917fe392373dd0

Change-Id: I0162960c24f20e2ce1ce1c76f47b261552205cb1

Cpuidle menu governor is using u32 as a temporary datatype for storing nanosecond values which wrap around at 4.294 seconds. This causes errors in predicted sleep times resulting in higher than should be C state selection and increased power consumption. This also breaks cpuidle state residency statistics.

DOH! fix bonehead typo

Change-Id: Ieec151c3be8a6511299c6bc49c1973b9ccae3f91

Wifi

The ashmem flush function ashmem_flush_cache_range was calling dmac_clean_range and dmac_flush_range with a user virtual address which is not allowed. Instead of calling dmac_clean_range or dmac_flush_range use flush_cache_user_range which can be called with a user vitual address. Change-Id: I5dd137fb248b45ef2c7ea5f7bdb4b540b8310af9 Signed-off-by: Shubhraprakash Das <[email protected]>

This reverts commit 9213a89.

…ung/android_kernel_samsung_aries into HEAD

Change-Id: Ib2ec6067df3bf81de18ba938b98b1d6ae81a2eaa

…751bcc fascinate: fix in-call audio

This reverts commit 78d6f3d.

…ung/android_kernel_samsung_aries into HEAD

This reverts commit 28bf4cf. Conflicts: arch/arm/mach-s5pv210/cpuidle.c Change-Id: I212c070a6ebde86133a3b4fd80310cadd23e3fb5

This reverts commit 35e80ed.

…msung_aries into android-samsung-2.6.35

Change-Id: Icb4d2a3df1161dedc7da50c3e4cacf12a003f54a

cleanup =)

Change-Id: I86c093866597572105b4a83a37af0109b55bd563

Change-Id: I299ceeabd5a712bcdc75223d5a6c15b18e411556

fixes for fascinate

Change-Id: I728c49ef2b4259edd67def9d5c25a72c89a63f34

fix permissions

sec_jack: headphone detection at boot. video: updated bootsplash. Change-Id: I3b45b907dc5793ba9e8d4d8905b31362e5881c49

…ent light sensor will behave properly

additional fixes for fascinate

When system is low on memory, allocating memory while holding the ashmem_mutex may try to directly reclaim memory. Then ashmem_shrink() is called in same thread. It will deadlock at acquiring ashmem_mutex. This change lets ashmem_shrink() return failure if ashmem_mutex is not available. Memory will be reclaimed from others. Change-Id: I3b6024d5477d37245f4ebde6d7069fb77af789ee Signed-off-by: Yuanyuan Zhong <[email protected]>

Pmem ashmem

Change-Id: Iffc5f8d5d4958952b04cfdc892f1db7fdac606db

…g/android_kernel_samsung_aries into android-samsung-2.6.35

Set CONFIG_TIMER_STATS to 'y' so powertop will work.

Change-Id: I5fd1b70b0f80bf376463d1726643b24dc120c4dc

…msgs when in deep sleep

Build FUSE module.

Enable CONFIG_TIMER_STATS

Build fuse.ko

This patch adds support for regulator API to sdhci core driver. Regulators can be used to disable power in suspended state to reduce dissipated energy. Signed-off-by: Marek Szyprowski <[email protected]> Signed-off-by: Kyungmin Park <[email protected]> Acked-by: Mark Brown <[email protected]> Cc: <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]> Conflicts: drivers/mmc/host/sdhci.c

Requires libcamera.so from newer ROMs.

…c" consumer. Fixes broken external SD when using Samsung Gingerbread bootloader.

External SD card fix for Gingerbread bootloader

…oid_kernel_samsung_aries into android-samsung-2.6.35

Updated camera driver from GT-I9000_OpenSource_GB_Update.tar.gz (Fixes front camera orientation).

Chroboczek); Remove stub tcf function from sfb (by Jan Steffens)

…nel_samsung_aries into android-samsung-2.6.35

This change reconfigures the CPU to allow CPU-supported unaligned accesses, which are generally faster than software-only fixups, resulting in fewer alignment exceptions. Signed-off-by: Brent DeGraaf <[email protected]>

…l the task closest in size to the amount of memory we actually need to free to satisfy the minfree threshold. (courtesy of kodos96)

This reverts commit 9b05a44.

This reverts commit 86efa84.

…ions." This reverts commit 385396a.

Improvement: - HW EQ support: smooth activation/deactivation and gain changes Bugfixes: - HP volume smoothing loop on low levels with negative digital offsets - wm8994_write logging on Nexus S New supported devices: - Galaxy Tab 7" Gingerbread Kernels support (based on M180S) - Galaxy Tab 10.1 - beta

…at-on. Appropriate changes have been made to releastools and the buildscript.

(Signed-off-on-by: Nikhil Rao; granularity improvements by Peter Ziljstra)

(upstream improvements) (Signed-off-by: Rafael J. Wysocki)

[ upstream commit af0e5d5 ] Disable the new -Wunused-but-set-variable that was added in gcc 4.6.0 It produces more false positives than useful warnings. This can still be enabled using W=1 [AK: dropped W=1 support in backport] Signed-off-by: Dave Jones <[email protected]> Acked-by: Sam Ravnborg <[email protected]> Tested-by: Sam Ravnborg <[email protected]> Signed-off-by: Michal Marek <[email protected]> Signed-off-by: Andi Kleen <[email protected]>

[ upstream commit 8417da6 ] Starting with 4.4, gcc will happily accept -Wno-<anything> in the cc-option test and complain later when compiling a file that has some other warning. This rather unexpected behavior is intentional as per http://gcc.gnu.org/PR28322, so work around it by testing for support of the opposite option (without the no-). Introduce a new Makefile function cc-disable-warning that does this and update two uses of cc-option in the toplevel Makefile. Reported-and-tested-by: Stephen Rothwell <[email protected]> Signed-off-by: Michal Marek <[email protected]> Signed-off-by: Andi Kleen <[email protected]>

Using as a replacement for BLN until I or someone else gets BLN working satisfactorily.

This reverts commit 1ac14a4.

The scheduler was causing the device to hard reboot after toggling airplane mode on. This reverts commit 4dacc92.

This reverts commit 248bd42.

…s to come on with the screen.

This patch fixes bug on gpio drive strength helper function. The offset should be like follwoing. - off = chip->chip.base - pin; + off = pin - chip->chip.base; In the s5p_gpio_get_drvstr(), the second line is unnecessary, because overwrite drvstr. drvstr = __raw_readl(reg); - drvstr = 0xffff & (0x3 << shift); And need 2bit masking before return the drvstr value. drvstr = drvstr >> shift; + drvstr &= 0x3; In the s5p_gpio_set_drvstr(), need relevant bit clear. tmp = __raw_readl(reg); + tmp &= ~(0x3 << shift); tmp |= drvstr << shift; Reported-by: Jaecheol Lee <[email protected]> Signed-off-by: Kukjin Kim <[email protected]>

This patch fixes on defined drive strength value for GPIO. According to data sheet, if we want drive strength 1x, the value should be 00(b), if 2x should be 10(b), if 3x should be 01(b), and if 4x should be 11(b). Also fixes comment(from S5C to S5P). Reported-by: Janghyuck Kim <[email protected]> Signed-off-by: Kukjin Kim <[email protected]>

[cjb: fix line-wrapped patch] Signed-off-by: Jiri Pinkava <[email protected]> Signed-off-by: Chris Ball <[email protected]> Cc: Matt Fleming <[email protected]> Cc: Russell King <[email protected]> Cc: Ben Dooks <[email protected]> Cc: <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>

FIMC driver uses DMA_coherent allocator, which requires proper dma mask to be set. Signed-off-by: Marek Szyprowski <[email protected]> Signed-off-by: Kyungmin Park <[email protected]> [[email protected]: minor title fix] Signed-off-by: Kukjin Kim <[email protected]>

IO registers region size of all FIMC versions is less than 1kB so there is no need to reserve 1M. Signed-off-by: Sylwester Nawrocki <[email protected]> Signed-off-by: Kyungmin Park <[email protected]> Signed-off-by: Marek Szyprowski <[email protected]> [[email protected]: minor title fix] Signed-off-by: Kukjin Kim <[email protected]>

CLK_GATE_IP3[8] is RESERVED. The port "I2C_HDMI_DDC" of CLK_GATE_IP3[10] is used as another I2C port. Therefore, defined the unused I2C-1 as another I2C there was left undefined but used. Signed-off-by: MyungJoo Ham <[email protected]> Signed-off-by: Kyungmin Park <[email protected]> Signed-off-by: Kukjin Kim <[email protected]>

These clocks enables FIMC driver to operate on machines, which bootloader power gated FIMC devices to save power on boot. Signed-off-by: Marek Szyprowski <[email protected]> Signed-off-by: Kyungmin Park <[email protected]> [[email protected]: minor title fix] Signed-off-by: Kukjin Kim <[email protected]>

Change-Id: If41c7b37585210e71c08660bd716d4799b4b55da

Try sliding down your touch screen onto your menu or back key. This prevents the capacitive keys from being accidentally triggered Change-Id: I47dc3e8ae869b422cc092d2a51db6a2e12cdebad

Change-Id: Ia5db1f2cec9c4634253bd6a7199d4a56fbb86c80

…mping directly to frequencies.

…the current voltages.

Ported from AOSP Samsung source - http://android.git.kernel.org/?p=kernel/samsung.git;a=summary Tunning of PHY0 Tune Register to improve physical characteristics. This improves the margin of USB eye diagram, which means the quality of USB signal is also improved.

…the i9000 / SGS - needs testing

commit d39195c upstream. Orphan cleanup is currently executed even if the file system has some number of unknown ROCOMPAT features, which deletes inodes and frees blocks, which could be very bad for some RO_COMPAT features, especially the SNAPSHOT feature. This patch skips the orphan cleanup if it contains readonly compatible features not known by this ext4 implementation, which would prevent the fs from being mounted (or remounted) readwrite. Signed-off-by: Amir Goldstein <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>

…necessary Replace the jbd2_inode structure (which is 48 bytes) with a pointer and only allocate the jbd2_inode when it is needed --- that is, when the file system has a journal present and the inode has been opened for writing. This allows us to further slim down the ext4_inode_info structure. Signed-off-by: "Theodore Ts'o" <[email protected]>

…ded padding By reordering the elements in the ext4_inode_info structure, we can reduce the padding needed on an x86_64 system by 16 bytes. Signed-off-by: "Theodore Ts'o" <[email protected]>

We can store the dynamic inode state flags in the high bits of EXT4_I(inode)->i_flags, and eliminate i_state_flags. This saves 8 bytes from the size of ext4_inode_info structure, which when multiplied by the number of the number of in the inode cache, can save a lot of memory. Signed-off-by: "Theodore Ts'o" <[email protected]>

We don't need to set s_dirt in most of the ext4 code when journaling is enabled. In ext3/4 some of the summary statistics for # of free inodes, blocks, and directories are calculated from the per-block group statistics when the file system is mounted or unmounted. As a result the superblock doesn't have to be updated, either via the journal or by setting s_dirt. There are a few exceptions, most notably when resizing the file system, where the superblock needs to be modified --- and in that case it should be done as a journalled operation if possible, and s_dirt set only in no-journal mode. This patch will optimize out some unneeded disk writes when using ext4 with a journal. Signed-off-by: "Theodore Ts'o" <[email protected]>

These changes are not ones which are likely to result in races, but they should be fixed. Signed-off-by: "Theodore Ts'o" <[email protected]>

No real bugs found, just removed some dead code. Found by gcc 4.6's new warnings. Signed-off-by: Andi Kleen <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]>

ext4 didn't update the ctime of the file when its permission was changed. Steps to reproduce: # touch aaa # stat -c %Z aaa 1275289822 # setfacl -m 'u::x,g::x,o::x' aaa # stat -c %Z aaa 1275289822 <- unchanged But, according to the spec of the ctime, ext4 must update it. Port of ext3 patch by Miao Xie <[email protected]>. CC: [email protected] Signed-off-by: Jan Kara <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]>

Use a macro definition for ext4_abort() to clean up the .c files a wee bit. Signed-off-by: "Theodore Ts'o" <[email protected]>

… numbers Also use a macro definition so that __func__ and __LINE__ is implicit. Signed-off-by: "Theodore Ts'o" <[email protected]>

This allows the error messages to include the line number Signed-off-by: "Theodore Ts'o" <[email protected]>

Also start passing the line number to ext4_check_dir since we're going to need it in upcoming patch. Signed-off-by: "Theodore Ts'o" <[email protected]>

Signed-off-by: "Theodore Ts'o" <[email protected]>

Save number of file system errors, and the time function name, line number, block number, and inode number of the first and most recent errors reported on the file system in the superblock. Signed-off-by: "Theodore Ts'o" <[email protected]>

This allows us to grab any file system error messages by scraping /var/log/messages. This will make it easy for us to do error analysis across the very large number of machines as we deploy ext4 across the fleet. Signed-off-by: "Theodore Ts'o" <[email protected]>

Signed-off-by: Joe Perches <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]>

…ng files We have experienced bitmap inconsistencies after crash during file delete under heavy load. The crash is not file system related and I the following patch in ext4_free_branches() fixes the recovery problem. If the transaction is restarted and there is a crash before the new transaction is committed, then after recovery, the blocks that this indirect block points to have been freed, but the indirect block itself has not been freed and may still point to some of the free blocks (because of the ext4_forget()). So ext4_forget() should be called inside ext4_free_blocks() to avoid this problem. Signed-off-by: Amir Goldstein <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]>

__GFP_NOFAIL is going away, so add our own retry loop. Also add jbd2__journal_start() and jbd2__journal_restart() which take a gfp mask, so that file systems can optionally (re)start transaction handles using GFP_KERNEL. If they do this, then they need to be prepared to handle receiving an PTR_ERR(-ENOMEM) error, and be ready to reflect that error up to userspace. Signed-off-by: "Theodore Ts'o" <[email protected]>

Issue discard request in ext4_free_blocks() when ext4 has no journal and is mounted with discard option. Signed-off-by: Jiaying Zhang <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]>

Under heavy memory pressure we may hit out of memory situation and as result kstrdup'ed options will not be freed. Fix it. Signed-off-by: Cyrill Gorcunov <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]>

When journaled quota options are not specified, we do writes to quota files just in data=ordered mode. This actually causes warnings from JBD2 about dirty journaled buffer because ext4_getblk unconditionally treats a block allocated by it as metadata. Since quota actually is filesystem metadata, the easiest way to get rid of the warning is to always treat quota writes as metadata... Signed-off-by: Jan Kara <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]>

ext4_get_blocks got renamed to ext4_map_blocks, but left stale comments and a prototype littered around. Signed-off-by: Eric Sandeen <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]>

By running the following reproducer, we can confirm that the write system call returns with 0 when it should return the error EFBIG. #!/bin/sh /bin/dd if=/dev/zero of=./img bs=1k count=1 seek=1024k > /dev/null 2>&1 /sbin/mkfs.ext3 -Fq ./img /bin/mount -o loop -t ext4 ./img /mnt /bin/touch /mnt/file strace /bin/dd if=/dev/zero of=/mnt/file conv=notrunc bs=1k count=1 seek=$((2194719883264/1024)) 2>&1 | /bin/egrep "write.* 1024\) = " /bin/umount /mnt exit Signed-off-by: Toshiyuki Okajima <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]> Cc: Eric Sandeen <[email protected]>

I often get emails containing the "This should not happen!!" message, conveniently trimmed to remove things like: sd 0:0:0:0: [sda] Unhandled error code sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 03 13 c9 70 00 00 28 00 end_request: I/O error, dev sda, sector 51628400 Aborting journal on device dm-0-8. EXT4-fs error (device dm-0): ext4_journal_start_sb: Detected aborted journal EXT4-fs (dm-0): Remounting filesystem read-only I don't think there is any value to the verbosity if the reason is due to a filesystem abort; it just obfuscates the root cause. Signed-off-by: Eric Sandeen <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]>

There were some error paths in ext4_delete_inode() which was not dropping the inode from the orphan list. This could lead to a BUG_ON on umount when the orphan list is discovered to be non-empty. Signed-off-by: "Theodore Ts'o" <[email protected]>

Perform full sync procedure so that any delayed allocation blocks are allocated so quota will be consistent. Signed-off-by: Dmitry Monakhov <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]>

Allow mount options to be stored in the superblock. Also add default mount option bits for nobarrier, block_validity, discard, and nodelalloc. Signed-off-by: "Theodore Ts'o" <[email protected]>

commit 3d0518f, "ext4: New rec_len encoding for very large blocksizes" made several changes to this path, but from a perf perspective, un-inlining ext4_rec_len_from_disk() seems most significant. This function is called from ext4_check_dir_entry(), which on a file-creation workload is called extremely often. I tested this with bonnie: # bonnie++ -u root -s 0 -f -x 200 -d /mnt/test -n 32 (this does 200 iterations) and got this for the file creations: ext4 stock: Average = 21206.8 files/s ext4 inlined: Average = 22346.7 files/s (+5%) Signed-off-by: Eric Sandeen <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]>

In data=journal mode, we still use block_write_begin() to prepare page for writing. This function can occasionally mark buffer dirty which violates journalling assumptions - when a buffer is part of a transaction, it should be dirty and a buffer can be already part of a forget list of some transaction when block_write_begin() gets called. This violation of journalling assumptions then results in "JBD: Spotted dirty metadata buffer..." warnings. In fact, temporary dirtying the buffer while the page is still locked does not really cause problems to the journalling because we won't write the buffer until the page gets unlocked. So we just have to make sure to clear dirty bits before unlocking the page. Signed-off-by: Jan Kara <[email protected]>

patch by LorD ClockaN] In data=journal mode, we still use block_write_begin() to prepare page for writing. This function can occasionally mark buffer dirty which violates journalling assumptions - when a buffer is part of a transaction, it should be dirty and a buffer can be already part of a forget list of some transaction when block_write_begin() gets called. This violation of journalling assumptions then results in "JBD: Spotted dirty metadata buffer..." warnings. In fact, temporary dirtying the buffer while the page is still locked does not really cause problems to the journalling because we won't write the buffer until the page gets unlocked. So we just have to make sure to clear dirty bits before unlocking the page. Signed-off-by: Jan Kara <[email protected]>

Signed-off-by: Al Viro <[email protected]>

The BKL is still used in ext4_put_super(), ext4_fill_super() and ext4_remount(). All three calles are protected against concurrent calls by the s_umount rw semaphore of struct super_block. Therefore the BKL is protecting nothing in this case. Signed-off-by: Jan Blunck <[email protected]> Acked-by: "Theodore Ts'o" <[email protected]> Signed-off-by: Arnd Bergmann <[email protected]>

It turns out we have several problems with how EOFBLOCKS_FL is handled. First of all, there was a fencepost error where we were not clearing the EOFBLOCKS_FL when fill in the last uninitialized block, but rather when we allocate the next block _after_ the uninitalized block. Secondly we were not testing to see if we needed to clear the EOFBLOCKS_FL when writing to the file O_DIRECT or when were converting an uninitialized block (which is the most common case). Google-Bug-Id: 2928259 Signed-off-by: "Theodore Ts'o" <[email protected]>

ext4_group_info structures are currently allocated with kmalloc(). With a typical 4K block size, these are 136 bytes each -- meaning they'll each consume a 256-byte slab object. On a system with many ext4 large partitions, that's a lot of wasted kernel slab space. (E.g., a single 1TB partition will have about 8000 block groups, using about 2MB of slab, of which nearly 1MB is wasted.) This patch creates an array of slab pointers created as needed -- depending on the superblock block size -- and uses these slabs to allocate the group info objects. Google-Bug-Id: 2980809 Signed-off-by: Curt Wohlgemuth <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]>

Ext4 already performs block allocation on rename, but it does it after rename was complete, so race window is much tighter but still exist. In order to guarantee atomic behavior let's force block allocation before actual rename. This rearrangement should not affect IO performance. - Code cleanup: It is possible to move some checks out of transaction which theoretically may result in better performance. Signed-off-by: Dmitry Monakhov <[email protected]>

…by: Akira Fujita <[email protected]>)

Change-Id: I501c3feb233088247e9dfe52cc117d00b0b705cc

Compensate for chipset inaccuracies in returning battery percentage the way Samsung did it in its Froyo rom. This allows the battery to reach 100% (may require bump charging) and no visible battery drop is noticable (even after a reboot). The precision is also increased (no 2% jump) from the current method of calculation because the calculation is done where we have extra precision information from the chipset. Change-Id: Id7f15dd3906f7a12949683c0d921ce7a8498e70a

credit to efpophis

…vate -> captivatemtd)

This patch populates the L1 entries for MT_MEMORY and MT_MEMORY_NONCACHED types so that at boot-up, we can map memories outside system memory at page level granularity Previously the mapping was limiting to section level, which creates unnecessary additional mapping for which physical memory may not present. On the newer ARM with speculation, this is dangerous and can result in untraceable aborts. Signed-off-by: Santosh Shilimkar <[email protected]> Signed-off-by: Russell King <[email protected]>

The commit f1a2481 sets up the default flags for MT_MEMORY and MT_MEMORY_NONCACHED memory types. L_PTE_USER flag is wrongly set as default for these entries so remove it. Also adding the 'L_PTE_WRITE' flag so that these pages become read-write instead of just being read-only [this stops them being exposed to userspace, which is the main concern here --rmk] Reported-by: Catalin Marinas <[email protected]> Signed-off-by: Santosh Shilimkar <[email protected]> Acked-by: Catalin Marinas <[email protected]> Signed-off-by: Russell King <[email protected]>

Kconfig doesn't have any knowledge of specific v7 cores, so it is possible to select errata workarounds that may cause inadvertent behaviour when executed on a core other than those targetted by the fix. This patch improves the variant and revision checking in proc-v7.S so that the primary part number is also considered when applying errata workarounds. Acked-by: Catalin Marinas <[email protected]> Signed-off-by: Will Deacon <[email protected]> Signed-off-by: Russell King <[email protected]>

The MOVW instruction moves a 16-bit immediate into the bottom halfword of the destination register. This patch ensures that kprobes leaves the 16-bit immediate intact, rather than assume a 12-bit immediate and mask out the upper 4 bits. Acked-by: Nicolas Pitre <[email protected]> Signed-off-by: Will Deacon <[email protected]> Signed-off-by: Russell King <[email protected]>

Defconfigs updated to include smartass 2

…t was just an annoyance.

Enabled easy setup of cross compiler from script.

This should fix a rare race condition causing the touchkeys to fail (due to bl_off timer) as i2c isn't thread-safe. When the touchkeys fails this way, the screen won't turn on and this may be certain cases of the so called "sleep of death". Change-Id: Id9b0af983c17a562058edf0154a171558a147584

…ed from Samsung's GT-I9000B kernel config) and added CONFIG_INPUT_YAMAHA. Compass works now after proper calibration.

Samsung's source for aries doesn't set ear_sel from wm8994. Change-Id: I495f4c8342e3d589b12fe42dbdb369f55f9c7545

- CAPTIVATE ifdef in wm8994 drivers are removed because they no longer have any effect Change-Id: I8e26ecc4df63a813a665ab012cd7c6c49651c061

Change-Id: Ib1c8e3cd98046477ff06de98089264f42c2c560d

…alonmtd into android-samsung-2.6.35

…0 counting scheme)

…alonmtd into android-samsung-2.6.35

…ightly #143/#144)

…granularity Mathieu reported bad latencies with make -j10 kind of kbuild workloads - which is mostly caused by us scheduling with a too coarse granularity. Reduce the minimum granularity some more, to make sure we can meet the latency target. I got the following results (make -j10 kbuild load, average of 3 runs): vanilla: maximum latency: 38278.9 µs average latency: 7730.1 µs patched: maximum latency: 22702.1 µs average latency: 6684.8 µs Mathieu also measured it: | | * wakeup-latency.c (SIGEV_THREAD) with make -j10 | | - Mainline 2.6.35.2 kernel | | maximum latency: 45762.1 µs | average latency: 7348.6 µs | | - With only Peter's smaller min_gran (shown below): | | maximum latency: 29100.6 µs | average latency: 6684.1 µs | Reported-by: Mathieu Desnoyers <[email protected]> Reported-by: Linus Torvalds <[email protected]> Acked-by: Mathieu Desnoyers <[email protected]> Suggested-by: Peter Zijlstra <[email protected]> Acked-by: Peter Zijlstra <[email protected]> LKML-Reference: <[email protected]> Signed-off-by: Ingo Molnar <[email protected]>

Commits on Jun 10, 2011

fascinate: fix in-call audio

jt1134 committed Jun 10, 2011

Configuration menu

View commit details

Copy full SHA for 0f35129

Browse repository at this point

Copy the full SHA

0f35129 View commit details

Browse the repository at this point in the history

Commits on Jul 29, 2011

Build fuse.ko

Build FUSE module.

yath committed Jul 29, 2011

Configuration menu

View commit details

Copy full SHA for 38e889b

Browse repository at this point

Copy the full SHA

38e889b View commit details

Browse the repository at this point in the history

Commits on Aug 15, 2011

cpufreq: added ondemandx governor

ytt3r committed Aug 15, 2011

Configuration menu

View commit details

Copy full SHA for 7243d7a

Browse repository at this point

Copy the full SHA

7243d7a View commit details

Browse the repository at this point in the history

Commits on Sep 8, 2011

Reset any smartass commits

ytt3r committed Sep 8, 2011

Configuration menu

View commit details

Copy full SHA for deee5f9

Browse repository at this point

Copy the full SHA

deee5f9 View commit details

Browse the repository at this point in the history

Android samsung 2.6.35 #1

Are you sure you want to change the base?

Android samsung 2.6.35 #1

Commits on May 29, 2011

Commits on May 30, 2011

Commits on May 31, 2011

Commits on Jun 1, 2011

Commits on Jun 2, 2011

Commits on Jun 3, 2011

Commits on Jun 6, 2011

Commits on Jun 7, 2011

Commits on Jun 8, 2011

Commits on Jun 9, 2011

Commits on Jun 10, 2011

Commits on Jun 15, 2011

Commits on Jun 16, 2011

Commits on Jun 19, 2011

Commits on Jun 21, 2011

Commits on Jun 24, 2011

Commits on Jun 25, 2011

Commits on Jun 27, 2011

Commits on Jun 28, 2011

Commits on Jul 3, 2011

Commits on Jul 4, 2011

Commits on Jul 6, 2011

Commits on Jul 9, 2011

Commits on Jul 20, 2011

Commits on Jul 21, 2011

Commits on Jul 29, 2011

Commits on Jul 30, 2011

Commits on Aug 1, 2011

Commits on Aug 2, 2011

Commits on Aug 3, 2011

Commits on Aug 4, 2011

Commits on Aug 5, 2011

Commits on Aug 7, 2011

Commits on Aug 8, 2011

Commits on Aug 9, 2011

Commits on Aug 10, 2011

Commits on Aug 11, 2011

Commits on Aug 12, 2011

Commits on Aug 13, 2011

Commits on Aug 14, 2011

Commits on Aug 15, 2011

Commits on Aug 19, 2011

Commits on Aug 20, 2011

Commits on Aug 27, 2011

Commits on Aug 31, 2011

Commits on Sep 3, 2011

Commits on Sep 4, 2011

Commits on Sep 6, 2011

Commits on Sep 8, 2011

Commits on Sep 9, 2011

Commits on Sep 22, 2011

Commits on Oct 14, 2011