Function partial_name_hash() takes long type value into which can be stored
one Unicode code point. Therefore conversion from UTF-32 to UTF-16 is not
needed.
Signed-off-by: Pali Rohár <pali@kernel.org>
Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
Git-commit: dddf7da3985ee144b46ee287e81e47b9ee8bb980
Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: lixiang <lixiang@codeaurora.org>
Remove the direct use of KERN_<LEVEL> in functions by creating
separate exfat_<level> macros.
Miscellanea:
o Remove several unnecessary terminating newlines in formats
o Realign arguments and fit to 80 columns where appropriate
Signed-off-by: Joe Perches <joe@perches.com>
Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
Git-commit: d1727d55c0327efdba2a5bad7801d509b721fef3
Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: lixiang <lixiang@codeaurora.org>
If two Unicode code points represented in UTF-16 are different then also
their UTF-32 representation must be different. Therefore conversion from
UTF-32 to UTF-16 is not needed.
Signed-off-by: Pali Rohár <pali@kernel.org>
Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
Git-commit: 197298a64983e2beaf1a87413daff3044b4f3821
Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: lixiang <lixiang@codeaurora.org>
'es' is malloced from exfat_get_dentry_set() in exfat_find() and should
be freed before leaving from the error handling cases, otherwise it will
cause memory leak.
Fixes: 5f2aa075070c ("exfat: add inode operations")
Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
Git-commit: 94182167ec730dadcaea5fbc6bb8f1136966ef66
Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: lixiang <lixiang@codeaurora.org>
Doing copy_file_range() on exfat with a file opened for direct IO leads
to an -EFAULT:
-c "copy_range -d 16384 -l 16384 -f 0" /mnt/test/junk
copy_range: Bad address
and the reason seems to be that we go through:
default_file_splice_write
splice_from_pipe
__splice_from_pipe
write_pipe_buf
__kernel_write
new_sync_write
generic_file_write_iter
generic_file_direct_write
exfat_direct_IO
do_blockdev_direct_IO
iov_iter_get_pages
and land in iterate_all_kinds(), which does "return -EFAULT" for our kvec
iter.
Setting exfat's splice_write to iter_file_splice_write fixes this and lets
fsx (which originally detected the problem) run to success from
the xfstests harness.
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
Git-commit: 035779483072ff7854943dc0cbae82c4e0070d15
Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: lixiang <lixiang@codeaurora.org>
The timestamp for access_time has double seconds granularity(There is no
10msIncrement field for access_time unlike create/modify_time).
exfat's atimes are restricted to only 2s granularity so after
we set an atime, round it down to the nearest 2s and set the
sub-second component of the timestamp to 0.
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
Git-commit: 81df1ad40644b706a1cdbd28a1471f9f0c0ea3e8
Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: lixiang <lixiang@codeaurora.org>
The s_time_gran superblock field indicates the on-disk nanosecond
granularity of timestamps, and for exfat that seems to be 10ms, so
set s_time_gran to 10000000ns. Without this, in-memory timestamps
change when they get re-read from disk.
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
Git-commit: 674a9985b8e35288225f2b67829a7dee3bf761da
Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: lixiang <lixiang@codeaurora.org>
This adds the necessary MODULE_ALIAS_FS() to exfat so the module gets
automatically loaded when an exfat filesystem is mounted.
Signed-off-by: Thomas Backlund <tmb@mageia.org>
Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
Git-commit: cd76ac258cd92a6425cb68f95a76d6abdce5395a
Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: lixiang <lixiang@codeaurora.org>
Discard support was always unconditionally disabled. Now it is disabled
only in the case when blk_queue_discard() returns false.
Signed-off-by: Pali Rohár <pali@kernel.org>
Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
Git-commit: b7e038a92449f191395fbb86538b14093c529833
Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: lixiang <lixiang@codeaurora.org>
Add config flag to enable qseecom and
TZ diag log drivers for sdxnightjar.
Change-Id: I68017faf02c1ca8f1f6a68ef01b93cb436abc04a
Signed-off-by: Phanindra Babu Pabba <pabba@codeaurora.org>
In kgsl_mem_entry_create, access map_count only if entry is allocated
successfully to avoid invalid access.
Change-Id: I57bce1aec2da6a27b6d13dbee96ed86a45c9660c
Signed-off-by: Deepak Kumar <dkumar@codeaurora.org>
Touch uses gpio as irq in LA. As per latest change from pinctrl,
wakeup bit is disabled/enabled when disable_irq/enable_irq is called.
During transtion from LA to LE, disable_irq is called leading to
wakeup bit getting disabled and in LE Touch interrupts does not come.
So, use disable_irq_wake to disable Touch interrupts while transition
from LA to LE and use enable_irq_wake to enable back Touch interrupts
while transition from LE to LA.
Change-Id: Iad3391af40535d51daeef881c3d62b3ec893fff2
Signed-off-by: Ritesh Kumar <riteshk@codeaurora.org>
Spi slave will support only mode1, so set the CPHA parameter
for spi slave.
wrongly added condition by merge conflict, hence removing it.
Change-Id: I37f9b159b01c9253de1a9e8b46e41160fa940660
Signed-off-by: Aniket Randive <arandive@codeaurora.org>
In the current deign, it is expected for the charger driver
to detect OTG and enable it without the USB driver to
explicitly enable it. As this support exists in the driver,
remove the OTG regulator configuration.
Change-Id: I165b144a2a8be88b493142de3a4a645e07f06253
Signed-off-by: Kavya Nunna <knunna@codeaurora.org>
Currently we are accessing snapshot structure after signaling
dump_gate. In corner cases this worker can get preempted
before driver reads this variable, and eventually client
dumps the snapshot and snapshot object gets released.
When worker gets back in execution it will read freed memory
and will case kernel panic.
To fix this race, do completion for dump_gate after finishing
work in worker kgsl_snapshot_save_frozen_objs.
Change-Id: Iaf3c9f9e75a6e3e19653d2d166e2da624796ec98
Signed-off-by: Pankaj Gupta <gpankaj@codeaurora.org>
Signed-off-by: Deepak Kumar <dkumar@codeaurora.org>
Currently certain platforms have cores which are only host-mode
compatible. Prevent switch to peripharal mode for such cores so
as to prevent unanticipated core behavior and crashes.
Change-Id: I163e878bfe7428ed339409adb8a491a6673ca055
Signed-off-by: Harsh Agarwal <harshq@codeaurora.org>
Upon any command errors we should do a CMD and DAT reset
prior to DMA unmap but the current logic is other way.
So, with the existing change it could possible to access the
unmapped address before resetting and this leads to SMMU unmapped
address access faults. So, check for reset prior to DMA unmap.
Change-Id: I89a751118b00df1c952693a713cb5060739a0ed5
Suggested-by: Veerabhadrarao Badiganti <vbadigan@codeaurora.org>
Signed-off-by: Pradeep P V K <pragalla@codeaurora.org>
A NULL return for ICC get is valid for platforms where
CONFIG_INTERCONNECT is not defined. Refine the error handling
for the scm perf client to allow a NULL value.
Change-Id: I714a9091000e99aecb466a54968a140868659410
Signed-off-by: Anant Goel <anantg@codeaurora.org>
Add a cnss wrapper api to get pci reg dump for hang data.
Change-Id: Ic1e7b676b6999d8aa7f168625dd27fa7b9aa7746
Signed-off-by: Mohammed Siddiq <msiddiq@codeaurora.org>
Enable LKDTM driver to enable testing PAN features
Change-Id: I4b6ddd88fb730d1814cfd77262faf7269470c266
Signed-off-by: Dennis Cagle <dcagle@codeaurora.org>
On some boards, debug batteries cause a high value of battery
temperature to be read due to HW faults, and thereby, the continuous
triggering of the "bat-temp" interrupt. Prevent this false positive from
occurring.
Change-Id: I7c8058d3470159bd3ee423bc9c4873c5fb4973b0
Signed-off-by: Guru Das Srinagesh <gurus@codeaurora.org>
Add required macro definitions for SSPHY registers to be accessed
for platforms having 11nm SSPHY.
Change-Id: Idc0de1e701f7c84a13a0795b6e3af9000563e324
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
