{"push_id":2709625105,"size":98,"distinct_size":98,"ref":"refs/heads/oreo-mr1","head":"36c9a3a75f143494a68ca8e10060d141fbc26cb5","before":"ea5436d8c28fb2ac93579877f135c16e3c8f0b18","commits":[{"sha":"457813850e0b6ff53de6a742fb2940ddbf69d8af","author":{"name":"Will Deacon","email":"b913f13ef92ac157955c954ccaaff7be065faba4@arm.com"},"message":"arm64: lse: Add early clobbers to some input/output asm operands\n\ncommit 32c3fa7cdf0c4a3eb8405fc3e13398de019e828b upstream.\n\nFor LSE atomics that read and write a register operand, we need to\nensure that these operands are annotated as \"early clobber\" if the\nregister is written before all of the input operands have been consumed.\nFailure to do so can result in the compiler allocating the same register\nto both operands, leading to splats such as:\n\n Unable to handle kernel paging request at virtual address 11111122222221\n [...]\n x1 : 1111111122222222 x0 : 1111111122222221\n Process swapper/0 (pid: 1, stack limit = 0x000000008209f908)\n Call trace:\n  test_atomic64+0x1360/0x155c\n\nwhere x0 has been allocated as both the value to be stored and also the\natomic_t pointer.\n\nThis patch adds the missing clobbers.\n\nCc: <stable@vger.kernel.org>\nCc: Dave Martin <dave.martin@arm.com>\nCc: Robin Murphy <robin.murphy@arm.com>\nReported-by: Mark Salter <msalter@redhat.com>\nSigned-off-by: Will Deacon <will.deacon@arm.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/457813850e0b6ff53de6a742fb2940ddbf69d8af"},{"sha":"1480fa6ad2a83bb44c8c650f6da49dae5ef2e9ac","author":{"name":"Michael Neuling","email":"7b0ab45a730e48a69239010b5b8fe5fa4e8eaac6@neuling.org"},"message":"powerpc/64s: Clear PCR on boot\n\ncommit faf37c44a105f3608115785f17cbbf3500f8bc71 upstream.\n\nClear the PCR (Processor Compatibility Register) on boot to ensure we\nare not running in a compatibility mode.\n\nWe've seen this cause problems when a crash (and kdump) occurs while\nrunning compat mode guests. The kdump kernel then runs with the PCR\nset and causes problems. The symptom in the kdump kernel (also seen in\npetitboot after fast-reboot) is early userspace programs taking\nsigills on newer instructions (seen in libc).\n\nSigned-off-by: Michael Neuling <mikey@neuling.org>\nCc: stable@vger.kernel.org\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/1480fa6ad2a83bb44c8c650f6da49dae5ef2e9ac"},{"sha":"904048b832d5bc4d9ac36e0eed57166c35474770","author":{"name":"Geert Uytterhoeven","email":"0da414d9d963da4039c2a0525b1844228075aa58@linux-m68k.org"},"message":"USB: serial: cp210x: use tcflag_t to fix incompatible pointer type\n\ncommit 009615ab7fd4e43b82a38e4e6adc5e23c1ee567f upstream.\n\nOn sparc32, tcflag_t is unsigned long, unlike all other architectures:\n\n    drivers/usb/serial/cp210x.c: In function 'cp210x_get_termios':\n    drivers/usb/serial/cp210x.c:717:3: warning: passing argument 2 of 'cp210x_get_termios_port' from incompatible pointer type\n       cp210x_get_termios_port(tty->driver_data,\n       ^\n    drivers/usb/serial/cp210x.c:35:13: note: expected 'unsigned int *' but argument is of type 'tcflag_t *'\n     static void cp210x_get_termios_port(struct usb_serial_port *port,\n\t\t ^\n\nConsistently use tcflag_t to fix this.\n\nSigned-off-by: Geert Uytterhoeven <geert@linux-m68k.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nCc: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/904048b832d5bc4d9ac36e0eed57166c35474770"},{"sha":"3c65e2f40ed486fbf44e4e33f490f1d579e554a4","author":{"name":"Yoshinori Sato","email":"7b39ff94cb259c2eec0f0bda4ceed2a4f98b3595@users.sourceforge.jp"},"message":"sh: New gcc support\n\ncommit 940d4113f3306e07a1f86541489b686d1a979d54 upstream.\n\nNew gcc (4.8 or later) used new shift helper functions.\nSo we need added new helper to private libgcc.\n\nSigned-off-by: Yoshinori Sato <ysato@users.sourceforge.jp>\nSigned-off-by: Rich Felker <dalias@libc.org>\nCc: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/3c65e2f40ed486fbf44e4e33f490f1d579e554a4"},{"sha":"6895f0def6c4a850a536dca067c9254b154d5a40","author":{"name":"Brian Foster","email":"335646b5e374a776a6a2caca10969d6e3ec1cd2b@redhat.com"},"message":"xfs: detect agfl count corruption and reset agfl\n\ncommit a27ba2607e60312554cbcd43fc660b2c7f29dc9c upstream.\n\nThe struct xfs_agfl v5 header was originally introduced with\nunexpected padding that caused the AGFL to operate with one less\nslot than intended. The header has since been packed, but the fix\nleft an incompatibility for users who upgrade from an old kernel\nwith the unpacked header to a newer kernel with the packed header\nwhile the AGFL happens to wrap around the end. The newer kernel\nrecognizes one extra slot at the physical end of the AGFL that the\nprevious kernel did not. The new kernel will eventually attempt to\nallocate a block from that slot, which contains invalid data, and\ncause a crash.\n\nThis condition can be detected by comparing the active range of the\nAGFL to the count. While this detects a padding mismatch, it can\nalso trigger false positives for unrelated flcount corruption. Since\nwe cannot distinguish a size mismatch due to padding from unrelated\ncorruption, we can't trust the AGFL enough to simply repopulate the\nempty slot.\n\nInstead, avoid unnecessarily complex detection logic and and use a\nsolution that can handle any form of flcount corruption that slips\nthrough read verifiers: distrust the entire AGFL and reset it to an\nempty state. Any valid blocks within the AGFL are intentionally\nleaked. This requires xfs_repair to rectify (which was already\nnecessary based on the state the AGFL was found in). The reset\nmitigates the side effect of the padding mismatch problem from a\nfilesystem crash to a free space accounting inconsistency. The\ngeneric approach also means that this patch can be safely backported\nto kernels with or without a packed struct xfs_agfl.\n\nCheck the AGF for an invalid freelist count on initial read from\ndisk. If detected, set a flag on the xfs_perag to indicate that a\nreset is required before the AGFL can be used. In the first\ntransaction that attempts to use a flagged AGFL, reset it to empty,\nwarn the user about the inconsistency and allow the freelist fixup\ncode to repopulate the AGFL with new blocks. The xfs_perag flag is\ncleared to eliminate the need for repeated checks on each block\nallocation operation.\n\nThis allows kernels that include the packing fix commit 96f859d52bcb\n(\"libxfs: pack the agfl header structure so XFS_AGFL_SIZE is correct\")\nto handle older unpacked AGFL formats without a filesystem crash.\n\nSuggested-by: Dave Chinner <david@fromorbit.com>\nSigned-off-by: Brian Foster <bfoster@redhat.com>\nReviewed-by: Darrick J. Wong <darrick.wong@oracle.com>\nReviewed-by Dave Chiluk <chiluk+linuxxfs@indeed.com>\nSigned-off-by: Darrick J. Wong <darrick.wong@oracle.com>\nSigned-off-by: Dave Chiluk <chiluk+linuxxfs@indeed.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/6895f0def6c4a850a536dca067c9254b154d5a40"},{"sha":"e9f76c15d7abf49884f25ea52a4a6a5e8cb1e807","author":{"name":"Mimi Zohar","email":"f02992f7c171053741caa6b515d9896745b37477@linux.vnet.ibm.com"},"message":"Revert \"ima: limit file hash setting by user to fix and log modes\"\n\ncommit f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b upstream.\n\nUserspace applications have been modified to write security xattrs,\nbut they are not context aware.  In the case of security.ima, the\nsecurity xattr can be either a file hash or a file signature.\nPermitting writing one, but not the other requires the application to\nbe context aware.\n\nIn addition, userspace applications might write files to a staging\narea, which might not be in policy, and then change some file metadata\n(eg. owner) making it in policy.  As a result, these files are not\nlabeled properly.\n\nThis reverts commit c68ed80c97d9720f51ef31fe91560fdd1e121533, which\nprevents writing file hashes as security.ima xattrs.\n\nRequested-by: Patrick Ohly <patrick.ohly@intel.com>\nCc: Dmitry Kasatkin <dmitry.kasatkin@gmail.com>\nSigned-off-by: Mimi Zohar <zohar@linux.vnet.ibm.com>\nCc: Mike Rapoport <rppt@linux.vnet.ibm.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/e9f76c15d7abf49884f25ea52a4a6a5e8cb1e807"},{"sha":"587b8163617fbb597cf6ac7612cb5640085467ac","author":{"name":"Benjamin Tissoires","email":"7a0e50e3f6a0939db82b6a8a423c08a163896f41@redhat.com"},"message":"Input: elan_i2c_smbus - fix corrupted stack\n\ncommit 40f7090bb1b4ec327ea1e1402ff5783af5b35195 upstream.\n\nNew ICs (like the one on the Lenovo T480s) answer to\nETP_SMBUS_IAP_VERSION_CMD 4 bytes instead of 3. This corrupts the stack\nas i2c_smbus_read_block_data() uses the values returned by the i2c\ndevice to know how many data it need to return.\n\ni2c_smbus_read_block_data() can read up to 32 bytes (I2C_SMBUS_BLOCK_MAX)\nand there is no safeguard on how many bytes are provided in the return\nvalue. Ensure we always have enough space for any future firmware.\nAlso 0-initialize the values to prevent any access to uninitialized memory.\n\nCc: <stable@vger.kernel.org> # v4.4.x, v4.9.x, v4.14.x, v4.15.x, v4.16.x\nSigned-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>\nAcked-by: KT Liao <kt.liao@emc.com.tw>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/587b8163617fbb597cf6ac7612cb5640085467ac"},{"sha":"314aeba9b477f83d19e740e3cfa319787e309821","author":{"name":"Steven Rostedt (VMware)","email":"43232e92d70cc7aa53504ad0397085ee47bad87f@goodmis.org"},"message":"tracing: Fix crash when freeing instances with event triggers\n\ncommit 86b389ff22bd6ad8fd3cb98e41cd271886c6d023 upstream.\n\nIf a instance has an event trigger enabled when it is freed, it could cause\nan access of free memory. Here's the case that crashes:\n\n # cd /sys/kernel/tracing\n # mkdir instances/foo\n # echo snapshot > instances/foo/events/initcall/initcall_start/trigger\n # rmdir instances/foo\n\nWould produce:\n\n general protection fault: 0000 [#1] PREEMPT SMP PTI\n Modules linked in: tun bridge ...\n CPU: 5 PID: 6203 Comm: rmdir Tainted: G        W         4.17.0-rc4-test+ #933\n Hardware name: Hewlett-Packard HP Compaq Pro 6300 SFF/339A, BIOS K01 v03.03 07/14/2016\n RIP: 0010:clear_event_triggers+0x3b/0x70\n RSP: 0018:ffffc90003783de0 EFLAGS: 00010286\n RAX: 0000000000000000 RBX: 6b6b6b6b6b6b6b2b RCX: 0000000000000000\n RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8800c7130ba0\n RBP: ffffc90003783e00 R08: ffff8801131993f8 R09: 0000000100230016\n R10: ffffc90003783d80 R11: 0000000000000000 R12: ffff8800c7130ba0\n R13: ffff8800c7130bd8 R14: ffff8800cc093768 R15: 00000000ffffff9c\n FS:  00007f6f4aa86700(0000) GS:ffff88011eb40000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007f6f4a5aed60 CR3: 00000000cd552001 CR4: 00000000001606e0\n Call Trace:\n  event_trace_del_tracer+0x2a/0xc5\n  instance_rmdir+0x15c/0x200\n  tracefs_syscall_rmdir+0x52/0x90\n  vfs_rmdir+0xdb/0x160\n  do_rmdir+0x16d/0x1c0\n  __x64_sys_rmdir+0x17/0x20\n  do_syscall_64+0x55/0x1a0\n  entry_SYSCALL_64_after_hwframe+0x49/0xbe\n\nThis was due to the call the clears out the triggers when an instance is\nbeing deleted not removing the trigger from the link list.\n\nCc: stable@vger.kernel.org\nFixes: 85f2b08268c01 (\"tracing: Add basic event trigger framework\")\nSigned-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/314aeba9b477f83d19e740e3cfa319787e309821"},{"sha":"0db1db6167d3a61ea234730e1e741c8f1dc0ef45","author":{"name":"Sachin Grover","email":"af668b036f98d0122bb232b04400bb78b43edbba@codeaurora.org"},"message":"selinux: KASAN: slab-out-of-bounds in xattr_getsecurity\n\ncommit efe3de79e0b52ca281ef6691480c8c68c82a4657 upstream.\n\nCall trace:\n [<ffffff9203a8d7a8>] dump_backtrace+0x0/0x428\n [<ffffff9203a8dbf8>] show_stack+0x28/0x38\n [<ffffff920409bfb8>] dump_stack+0xd4/0x124\n [<ffffff9203d187e8>] print_address_description+0x68/0x258\n [<ffffff9203d18c00>] kasan_report.part.2+0x228/0x2f0\n [<ffffff9203d1927c>] kasan_report+0x5c/0x70\n [<ffffff9203d1776c>] check_memory_region+0x12c/0x1c0\n [<ffffff9203d17cdc>] memcpy+0x34/0x68\n [<ffffff9203d75348>] xattr_getsecurity+0xe0/0x160\n [<ffffff9203d75490>] vfs_getxattr+0xc8/0x120\n [<ffffff9203d75d68>] getxattr+0x100/0x2c8\n [<ffffff9203d76fb4>] SyS_fgetxattr+0x64/0xa0\n [<ffffff9203a83f70>] el0_svc_naked+0x24/0x28\n\nIf user get root access and calls security.selinux setxattr() with an\nembedded NUL on a file and then if some process performs a getxattr()\non that file with a length greater than the actual length of the string,\nit would result in a panic.\n\nTo fix this, add the actual length of the string to the security context\ninstead of the length passed by the userspace process.\n\nSigned-off-by: Sachin Grover <sgrover@codeaurora.org>\nCc: stable@vger.kernel.org\nSigned-off-by: Paul Moore <paul@paul-moore.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/0db1db6167d3a61ea234730e1e741c8f1dc0ef45"},{"sha":"2f41d5e25963e61c688b376dd5de6feb2d975f15","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"cfg80211: further limit wiphy names to 64 bytes\n\ncommit 814596495dd2b9d4aab92d8f89cf19060d25d2ea upstream.\n\nwiphy names were recently limited to 128 bytes by commit a7cfebcb7594\n(\"cfg80211: limit wiphy names to 128 bytes\").  As it turns out though,\nthis isn't sufficient because dev_vprintk_emit() needs the syslog header\nstring \"SUBSYSTEM=ieee80211\\0DEVICE=+ieee80211:$devname\" to fit into 128\nbytes.  This triggered the \"device/subsystem name too long\" WARN when\nthe device name was >= 90 bytes.  As before, this was reproduced by\nsyzbot by sending an HWSIM_CMD_NEW_RADIO command to the MAC80211_HWSIM\ngeneric netlink family.\n\nFix it by further limiting wiphy names to 64 bytes.\n\nReported-by: syzbot+e64565577af34b3768dc@syzkaller.appspotmail.com\nFixes: a7cfebcb7594 (\"cfg80211: limit wiphy names to 128 bytes\")\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/2f41d5e25963e61c688b376dd5de6feb2d975f15"},{"sha":"97b5c2845fe497e473f550cee7bbd3b87b090afd","author":{"name":"Matthias Kaehlcke","email":"df22eae001bf82a113742cff559755b8fc65d45a@chromium.org"},"message":"rtlwifi: rtl8192cu: Remove variable self-assignment in rf.c\n\ncommit fb239c1209bb0f0b4830cc72507cc2f2d63fadbd upstream.\n\nIn _rtl92c_get_txpower_writeval_by_regulatory() the variable writeVal\nis assigned to itself in an if ... else statement, apparently only to\ndocument that the branch condition is handled and that a previously read\nvalue should be returned unmodified. The self-assignment causes clang to\nraise the following warning:\n\ndrivers/net/wireless/realtek/rtlwifi/rtl8192cu/rf.c:304:13:\n  error: explicitly assigning value of variable of type 'u32'\n    (aka 'unsigned int') to itself [-Werror,-Wself-assign]\n  writeVal = writeVal;\n\nDelete the branch with the self-assignment.\n\nSigned-off-by: Matthias Kaehlcke <mka@chromium.org>\nAcked-by: Larry Finger <Larry.Finger@lwfinger.net>\nReviewed-by: Guenter Roeck <groeck@chromium.org>\nSigned-off-by: Kalle Valo <kvalo@codeaurora.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/97b5c2845fe497e473f550cee7bbd3b87b090afd"},{"sha":"a3cd143aaf9fa34b7f21cf4538500dd0035be30d","author":{"name":"Colin Ian King","email":"d100aa70785e45ee8deab668147d941941915c21@canonical.com"},"message":"ASoC: Intel: sst: remove redundant variable dma_dev_name\n\ncommit 271ef65b5882425d500e969e875c98e47a6b0c86 upstream.\n\nThe pointer dma_dev_name is assigned but never read, it is redundant\nand can therefore be removed.\n\nCleans up clang warning:\nsound/soc/intel/common/sst-firmware.c:288:3: warning: Value stored to\n'dma_dev_name' is never read\n\nSigned-off-by: Colin Ian King <colin.king@canonical.com>\nAcked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nCc: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/a3cd143aaf9fa34b7f21cf4538500dd0035be30d"},{"sha":"2db437e3a28aa51befa9939480e0ac6f58bcc435","author":{"name":"Arnd Bergmann","email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de"},"message":"irda: fix overly long udelay()\n\ncommit c9bd28233b6d0d82ac3ba0215723be0a8262c39c upstream.\n\nirda_get_mtt() returns a hardcoded '10000' in some cases,\nand with gcc-7, we get a build error because this triggers a\ncompile-time check in udelay():\n\ndrivers/net/irda/w83977af_ir.o: In function `w83977af_hard_xmit':\nw83977af_ir.c:(.text.w83977af_hard_xmit+0x14c): undefined reference to `__bad_udelay'\n\nOlder compilers did not run into this because they either did not\ncompletely inline the irda_get_mtt() or did not consider the\n10000 value a constant expression.\n\nThe code has been wrong since the start of git history.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nCc: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/2db437e3a28aa51befa9939480e0ac6f58bcc435"},{"sha":"32be9051747de9d59f487126da77155d5bd1d873","author":{"name":"Eric Dumazet","email":"312c7d941f03386814be517ffdb3e0eb6624e275@google.com"},"message":"tcp: avoid integer overflows in tcp_rcv_space_adjust()\n\ncommit 607065bad9931e72207b0cac365d7d4abc06bd99 upstream.\n\nWhen using large tcp_rmem[2] values (I did tests with 500 MB),\nI noticed overflows while computing rcvwin.\n\nLets fix this before the following patch.\n\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nAcked-by: Soheil Hassas Yeganeh <soheil@google.com>\nAcked-by: Wei Wang <weiwan@google.com>\nAcked-by: Neal Cardwell <ncardwell@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\n[Backport: sysctl_tcp_rmem is not Namespace-ify'd in older kernels]\nSigned-off-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/32be9051747de9d59f487126da77155d5bd1d873"},{"sha":"f87e02d8779f42267e59194871b8602388dfc82a","author":{"name":"Wolfram Sang","email":"66ab244bc42248f12645ba300439b5263f6a6fca@sang-engineering.com"},"message":"i2c: rcar: make sure clocks are on when doing clock calculation\n\ncommit e43e0df13f8528ca55ed79f469c4b2af897fa796 upstream.\n\nWhen calculating the bus speed, the clock should be on, of course. Most\nbootloaders left them on, so this went unnoticed so far.\n\nMove the ioremapping out of this clock-enabled-block and prepare for\nadding hw initialization there, too.\n\nReported-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>\nSigned-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>\nSigned-off-by: Wolfram Sang <wsa@the-dreams.de>\nSigned-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>\nReviewed-by: Chris Paterson <Chris.Paterson2@renesas.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/f87e02d8779f42267e59194871b8602388dfc82a"},{"sha":"c51db90f30cbc3582c35fb5749c99bd4e09af714","author":{"name":"Wolfram Sang","email":"66ab244bc42248f12645ba300439b5263f6a6fca@sang-engineering.com"},"message":"i2c: rcar: rework hw init\n\ncommit 2c78cdc1c06308a59d6ed4145cdba73fdeff8c0d upstream.\n\nWe don't need to init HW before every transfer since we know the HW\nstate then. HW init at probe time is enough. While here, add setting the\nclock register which belongs to init HW. Also, set MDBS bit since not\nsetting it is prohibited according to the manual.\n\nSigned-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>\nSigned-off-by: Wolfram Sang <wsa@the-dreams.de>\nSigned-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>\nReviewed-by: Chris Paterson <Chris.Paterson2@renesas.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/c51db90f30cbc3582c35fb5749c99bd4e09af714"},{"sha":"4fc92bcaef5265855fead314bb0441709dc9f201","author":{"name":"Wolfram Sang","email":"66ab244bc42248f12645ba300439b5263f6a6fca@sang-engineering.com"},"message":"i2c: rcar: remove unused IOERROR state\n\ncommit 90f779e565bdc18dd4f79d81cf11f43a7266010b upstream.\n\nSigned-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>\nSigned-off-by: Wolfram Sang <wsa@the-dreams.de>\nSigned-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>\nReviewed-by: Chris Paterson <Chris.Paterson2@renesas.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/4fc92bcaef5265855fead314bb0441709dc9f201"},{"sha":"35a791b4cddec12a22373e4245532b735c8e5b0c","author":{"name":"Wolfram Sang","email":"66ab244bc42248f12645ba300439b5263f6a6fca@sang-engineering.com"},"message":"i2c: rcar: remove spinlock\n\ncommit ff2316b87a336bff940939cd9fc56287ed48e578 upstream.\n\nAfter making sure to reinit the HW and clear interrupts in the timeout\ncase, we know that interrupts are always disabled in the sections\nprotected by the spinlock. Thus, we can simply remove it which is a\npreparation for further refactoring. While here, rename the timeout\nvariable to time_left which is way more readable.\n\nSigned-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>\nSigned-off-by: Wolfram Sang <wsa@the-dreams.de>\nSigned-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>\nReviewed-by: Chris Paterson <Chris.Paterson2@renesas.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/35a791b4cddec12a22373e4245532b735c8e5b0c"},{"sha":"ed7c13dd288ec31b0874ef34d56740050cc83541","author":{"name":"Wolfram Sang","email":"66ab244bc42248f12645ba300439b5263f6a6fca@sang-engineering.com"},"message":"i2c: rcar: refactor setup of a msg\n\ncommit b9d0684c79c4b9d30ce0d47d3270493dd0e76e59 upstream.\n\nWe want to reuse this function later.\n\nSigned-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>\nSigned-off-by: Wolfram Sang <wsa@the-dreams.de>\nSigned-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>\nReviewed-by: Chris Paterson <Chris.Paterson2@renesas.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/ed7c13dd288ec31b0874ef34d56740050cc83541"},{"sha":"47ba16713359dfc6882715a277274566c12d6a8d","author":{"name":"Wolfram Sang","email":"66ab244bc42248f12645ba300439b5263f6a6fca@sang-engineering.com"},"message":"i2c: rcar: init new messages in irq\n\ncommit cc21d0b4b62e41e5013d763adade5ea4462c33a4 upstream.\n\nSetting up new messages was done in process context while handling a\nmessage was in interrupt context. Because of the HW design, this IP core\nis sensitive to timing, so the context switches were too expensive. Move\nthis setup to interrupt context as well.\n\nIn my test setup, this fixed the occasional 'data byte sent twice' issue\nwhich a number of people have seen. It also fixes to send REP_START\nafter a read message which was wrongly send as a STOP + START sequence\nbefore.\n\nSigned-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>\nSigned-off-by: Wolfram Sang <wsa@the-dreams.de>\nSigned-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>\nReviewed-by: Chris Paterson <Chris.Paterson2@renesas.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/AOSiP-Devices/kernel_essential_msm8998/commits/47ba16713359dfc6882715a277274566c12d6a8d"}]}
{"actor":{"display_login":"xlxfoxxlx"}}