From: Nick Dyer
The atmel touch messages contain orientation information as a byte in a
packed format which can be passed straight on to Android if the input
device configuration is correct.
This requires vector reports to be enabled in maXTouch config (zero
DISVECT bit 3 in T9 CTRL field)
Andr
From: Bhuvanesh Surachari
Move sysfs creation after intializing the input device to
prevent crash due to freeing of input device by function via sysfs.
Signed-off-by: Bhuvanesh Surachari
Signed-off-by: Sanjeev Chugh
Signed-off-by: George G. Davis
Signed-off-by: Jiada Wang
---
drivers/input/
From: Nick Dyer
Signed-off-by: Nick Dyer
Acked-by: Benson Leung
Acked-by: Yufeng Shen
(cherry picked from ndyer/linux/for-upstream commit
2895a6ff150a49f27a02938f8d262be238b296d8)
Signed-off-by: George G. Davis
Signed-off-by: Jiada Wang
---
drivers/input/touchscreen/atmel_mxt_ts.c | 25 +++
From: Nick Dyer
Signed-off-by: Nick Dyer
Acked-by: Benson Leung
Acked-by: Yufeng Shen
(cherry picked from ndyer/linux/for-upstream commit
56405a5ea08eb34cfe83f3121867c9de0a5c48c1)
Signed-off-by: George G. Davis
Signed-off-by: Jiada Wang
---
drivers/input/touchscreen/atmel_mxt_ts.c | 12 +++
From: Balasubramani Vivekanandan
In mxt_process_messages_until_invalid() function, driver tries to read
all possible reportid in a single i2c transaction. Number of bytes read
is limited by the max_reportid parameter.
If the max_reportid is a very large value, then a large chunk of bytes
will be
From: Deepak Das
"a008387 Input: atmel_mxt_ts: Limit the max bytes transferred in an i2c
transaction" limited the Max bytes transferred in i2c transaction while
reading T5 message in mxt_process_messages_until_invalid().
mxt_process_messages_t44() reads the T44 message which contains the
pending
From: Dean Jenkins
Replace HZ / 10 with msecs_to_jiffies(100) in the
schedule_delayed_work() calls in mxt_fw_work() and
mxt_check_bootloader() because it is cleaner.
Signed-off-by: Dean Jenkins
Signed-off-by: Sanjeev Chugh
Signed-off-by: George G. Davis
Signed-off-by: Jiada Wang
---
drivers
From: Nick Dyer
Signed-off-by: Nick Dyer
(cherry picked from ndyer/linux/for-upstream commit
078569c13c88dcb6f8d882bfe17168587712df7d)
[gdavis: Resolve forward port conflicts due to v4.14.51 commit
960fe000b1d3 ("Input: atmel_mxt_ts - fix the firmware
update").]
Signed-off-by:
From: Dean Jenkins
In mxt_interrupt(), complete(&data->chg_completion) was
called everytime mxt_interrupt() ran which is unnecessary.
mxt_regulator_enable() sets data->in_bootloader to true and
waits for the completion indication for data->chg_completion
to be set by mxt_interrupt().
mxt_interr
Dynamically allocated in mxt_read_info_block() buffer buf is assigned
both to data->info and data->raw_info_block, having both data->info
and data->raw_info_block is redundant and confusing.
This patch eliminates data->raw_info_block.
Signed-off-by: Jiada Wang
Signed-off-by: George G. Davis
Sig
From: Balasubramani Vivekanandan
In case of remote display, touch controller will be also remote.
In such cases, the reset pin of the touch controller will be
controlled through bridging ICs like Deserilizer and Serializer.
Therefore accessing the gpio pins require transactions with the
external
From: Kautuk Consul
Revamping the code to call mxt_free_object_table and mxt_free_input_device
functions only in the following scenarios and code paths:
1) The error path of the mxt_probe() entry point
2) The mxt_remove de-init path entry point
3) All paths which definitely expect to populate the
From: Deepak Das
T44 object returns the count of valid T5 messages in the buffer. According
to atmel, this count should be the main criteria to read the number of T5
messages.
Following is the statement from atmel confirming the same :-
"For the readout of messages we recommend to stop after the
From: Nick Dyer
Atmel maXTouch chips can be addressed via an "Object Based Protocol" which
defines how i2c registers are mapped to different functions within the
chips. This interface exposes the register map and allows user-space
utilities to inspect and alter object configuration, and to view d
From: Bhuvanesh Surachari
>From the static analysis of the code it seems that there could be a
race condition leading to crash while freeing input device in
mxt_free_input_device(). The backtrace of crash is as shown below:
Unable to handle kernel NULL pointer dereference at virtual address
On 08/16/2019 12:43 AM, Guenter Roeck wrote:
> On Fri, Aug 16, 2019 at 12:19:42AM +0200, Max Staudt wrote:
>> On 08/15/2019 02:58 PM, Max Staudt wrote:
>>> - if (of_node) {
>>> - ret = of_property_read_u32_array(of_node, "lltc,meas-mode",
>>> -
From: Deepak Das
Currently Driver probe continues with a warning message when it fails to
get the proper multitouch object configurations like TouchScreen resolution.
But Driver probe should fail in case of above scneario because it will not
behave
as expected without the proper touchscreen conf
From: Deepak Das
Currently mxt_initialize() tries to probe bootloader mode
even if valid bootloader address is not specified.
This commit modifies mxt_initialize() to return error
if Device is not in appmode and bootloader address is
not specified.
This commit also returns error code from mxt_s
From: Deepak Das
mxt_start() does not return error in any of
the failure cases which will allow input_dev->open()
to return success even in case of any failure.
This commit modifies mxt_start() to return error
in failure cases.
Signed-off-by: Deepak Das
Signed-off-by: George G. Davis
Signed-o
From: Deepak Das
mxt_update_cfg() failed to propagate the error
code from mxt_init_t7_power_cfg() so return the error code.
Signed-off-by: Deepak Das
Signed-off-by: George G. Davis
Signed-off-by: Jiada Wang
---
drivers/input/touchscreen/atmel_mxt_ts.c | 4 +++-
1 file changed, 3 insertions(+
From: Deepak Das
Validity of bootloader address is now checked before checking the
bootloader status so mxt_lookup_bootloader_address() was moved
from mxt_probe_bootloader() to mxt_initialize().
Above changes added lot of bootloader mode verification code into
mxt_initialize() which made this fun
Hi,
On Wed, Aug 14, 2019 at 12:36:40PM +0200, Arnd Bergmann wrote:
> On Wed, Aug 14, 2019 at 9:49 AM Tony Lindgren wrote:
> > * Arnd Bergmann [190813 19:34]:
> > > -#define OMAP1_IO_OFFSET0x0100 /* Virtual IO
> > > = 0xfefb */
> > > +#define OMAP1_IO_OFFSET
From: Nick Dyer
When in hover, the orientation information is not sent
Signed-off-by: Nick Dyer
(cherry picked from ndyer/linux/for-upstream commit
0c885d5bd276bd9240c43aa046fc407cbe2ae864)
Signed-off-by: George G. Davis
Signed-off-by: Jiada Wang
---
drivers/input/touchscreen/atmel_mxt_ts.c
From: Nick Dyer
The path of enabling the IRQ in the probe function is not safe in level
triggered operation, if it was already powered up and there is a message
waiting on the device (eg finger down) because the object table has not yet
been read. This forces the ISR into a hard loop.
Delay enab
From: Nick Dyer
Signed-off-by: Nick Dyer
(cherry picked from ndyer/linux/for-upstream commit
dda8453bfb44216645ede798918a314d4fca2481)
[gdavis: Resolve forward port conflicts due to applying upstream
commit 96a938aa214e ("Input: atmel_mxt_ts - remove platform
data support").]
From: Nick Dyer
Signed-off-by: Nick Dyer
(cherry picked from ndyer/linux/for-upstream commit
67a3eea0cfc724c3c2a7410ac064f74227c7c6ef)
[gdavis: Resolve forward port conflicts due to applying upstream
commit 96a938aa214e ("Input: atmel_mxt_ts - remove platform
data support").]
From: Nick Dyer
The code is much clearer if we switch on the actual state the bootloader
is in, rather than the state we want it to be in, and allows the removal
of a goto retry tangle.
Signed-off-by: Nick Dyer
(cherry picked from ndyer/linux/for-upstream commit
463e15ee95ee6e6274017ff645839db
From: Nick Dyer
Signed-off-by: Nick Dyer
(cherry picked from ndyer/linux/for-upstream commit
d691d3ee6c6de84b38464a423207b3e23cb9dc3a)
Signed-off-by: George G. Davis
Signed-off-by: Jiada Wang
---
drivers/input/touchscreen/atmel_mxt_ts.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletion
From: Nick Dyer
Some maXTouch chips (eg mXT1386) will not respond on the first I2C request
when they are in a sleep state. It must be retried after a delay for the
chip to wake up.
Signed-off-by: Nick Dyer
Acked-by: Yufeng Shen
(cherry picked from ndyer/linux/for-upstream commit
63fd7a2cd03c3
From: Nick Dyer
Signed-off-by: Nick Dyer
(cherry picked from ndyer/linux/for-upstream commit
1bbe20ff3dcd6612e7942c495929eae5c138ece2)
Signed-off-by: George G. Davis
Signed-off-by: Jiada Wang
---
drivers/input/touchscreen/atmel_mxt_ts.c | 59 +++-
1 file changed, 36 inser
From: Nick Dyer
This removes some complexity from the bootloader state machine, and means
that we always output some debug about the version as soon as we start
talking to the bootloader.
Signed-off-by: Nick Dyer
(cherry picked from ndyer/linux/for-upstream commit
a2d141f170c80fea6663af98aab0b
From: Nick Dyer
Signed-off-by: Nick Dyer
(cherry picked from ndyer/linux/for-upstream commit
bedd706a32522b946467e15f4f4f24de86a1b4d7)
[gdavis: Resolve forward port conflicts due to applying upstream
commit 96a938aa214e ("Input: atmel_mxt_ts - remove platform
data support").]
From: ARUL JENISTON MC
---
fs/timerfd.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/fs/timerfd.c b/fs/timerfd.c
index 6a6fc8aa1de7..f5094e070e9a 100644
--- a/fs/timerfd.c
+++ b/fs/timerfd.c
@@ -284,8 +284,16 @@ static ssize_t timerfd_read(struct file *file,
Hi Petr
> -Original Message-
> From: Petr Mladek
> Sent: 2019年8月16日 16:27
> To: Justin He (Arm Technology China)
> Cc: Geert Uytterhoeven ; Sergey Senozhatsky
> ; Thomas Gleixner ;
> Andy Shevchenko ; linux-
> ker...@vger.kernel.org; Kees Cook ; Steven
> Rostedt (VMware) ; Shuah Khan
> ;
From: Nick Dyer
An error in the sysfs init may otherwise interfere with the async return
from the firmware loader
Signed-off-by: Nick Dyer
(cherry picked from ndyer/linux/for-upstream commit
3114584ae77c2b03b6dad87174f010d002e9c05d)
[gdavis: Forward port and fixup conflicts. Also fixed sysfs l
From: Nick Dyer
The workaround of reading all messages until an invalid is received is a
way of forcing the CHG line high, which means that when using
edge-triggered interrupts the interrupt can be acquired.
With level-triggered interrupts the workaround is unnecessary.
Also, most recent maXTou
This patch-set forward ports Nick Dyer's work in ndyer/linux github repository
as long as some other features and fixes
Balasubramani Vivekanandan (4):
Input: atmel_mxt_ts: Limit the max bytes transferred in an i2c
transaction
Input: atmel_mxt_ts: update stale use_retrigen_workaround flag
input_mt_report_slot_state() ignores the tool when the slot is closed.
which has caused a bit of confusion.
This patch introduces input_mt_report_slot_inactive() to report slot
inactive state.
replaces all input_mt_report_slot_state() with input_mt_report_slot_inactive()
in case of close of slot, a
From: Nick Dyer
On some firmware variants, the size of the info block exceeds what can
be read in a single transfer.
Signed-off-by: Nick Dyer
(cherry picked from ndyer/linux/for-upstream commit
74c4f5277cfa403d43fafc404119dc57a08677db)
[gdavis: Forward port and fix conflicts due to v4.14.51 co
On Thu 2019-08-15 23:33:01, Chuhong Yuan wrote:
> On Thu, Aug 15, 2019 at 9:52 PM Petr Mladek wrote:
> >
> > On Thu 2019-08-15 16:50:33, Sergey Senozhatsky wrote:
> > > On (08/14/19 12:49), Petr Mladek wrote:
> > > > On Fri 2019-08-09 15:10:34, Chuhong Yuan wrote:
> > > > > strncmp(str, const, len
On Fri 2019-08-09 09:24:57, Jia He wrote:
> This add some additional test cases of null/invalid pointer dereference
> for dentry and file (%pd and %pD)
>
> Signed-off-by: Jia He
> ---
> lib/test_printf.c | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/lib/test_printf.c b/lib/tes
Add a new variant of Intel Atom Airmont CPU model.
Signed-off-by: Rahul Tanwar
---
arch/x86/include/asm/intel-family.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/include/asm/intel-family.h
b/arch/x86/include/asm/intel-family.h
index 0278aa66ef62..cbbb8250370f 100644
--- a/arch
On Fri, Aug 16, 2019 at 09:50:31AM +0200, Maxime Ripard wrote:
> On Fri, Aug 16, 2019 at 12:17:09PM +0530, Bhushan Shah wrote:
> > Add device-tree nodes for i2c0 to i2c2, and also add relevant pinctrl
> > nodes.
> >
> > Suggested-by: Icenowy Zheng
> > Signed-off-by: Bhushan Shah
> > ---
> > Chang
On Thu, Aug 15, 2019 at 06:39:56PM -0700, Bart Van Assche wrote:
> On 8/15/19 12:51 AM, Will Deacon wrote:
> > On Sat, Aug 10, 2019 at 05:24:06PM -0700, syzbot wrote:
> > > The bug was bisected to:
> > >
> > > commit a0b0fd53e1e67639b303b15939b9c653dbe7a8c4
> > > Author: Bart Van Assche
> > > Dat
On Fri, Aug 16, 2019 at 09:52:11AM +0200, Maxime Ripard wrote:
> > +/* This i2c interface is exposed on PI-2 BUS, Pin 3 (I2C_SDA) and 5
> > (I2C_SCL) */
> > +&i2c0 {
> > + status = "disabled";
> > +};
>
> This property is set to disabled in the DTSI already
I added this node here with disabled
Hi,
> I cleaned up the build system, and pushed it based on my
> kbuild tree.
>
> Please see:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> klp-cleanup
This indeed looks much simpler and cleaner (as far as I can judge with my
limited kbuild knowledge). We just
On 8/16/19 10:10 AM, Hayes Wang wrote:
> Eric Dumazet [mailto:eric.duma...@gmail.com]
>> Sent: Friday, August 16, 2019 2:40 PM
> [...]
>> tasklet and NAPI are scheduled on the same core (the current
>> cpu calling napi_schedule() or tasklet_schedule())
>>
>> I would rather not add this dubious t
Update vulnerability init data for the newly added CPU model.
Enable setting CPU feature applicable for newly added CPU model.
Add TSC MSR freq_desc entry for newly added CPU model.
Signed-off-by: Rahul Tanwar
---
arch/x86/kernel/cpu/common.c | 1 +
arch/x86/kernel/cpu/intel.c | 1 +
arch/x86/k
On Fri 2019-08-09 10:56:04, Justin He (Arm Technology China) wrote:
>
>
> > -Original Message-
> > From: Andy Shevchenko
> > Sent: 2019年8月9日 18:52
> > To: Justin He (Arm Technology China)
> > Cc: Petr Mladek ; Andy Shevchenko
> > ; Sergey Senozhatsky
> > ; Geert Uytterhoeven
> > ; Lin
Replace direct values usage with constant definitions when access CPU models.
Signed-off-by: Rahul Tanwar
Suggested-by: Andy Shevchenko
---
arch/x86/kernel/cpu/intel.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/int
A forthcoming product uses a new variant of Atom Airmont CPU model.
This series adds support for this new CPU model.
Patches are baselined upon Linux 5.3-rc4 at below Git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/core
v2:
* Address review concerns about incorrect patch p
On Mon, Aug 12, 2019 at 11:30:48AM -0600, Logan Gunthorpe wrote:
> The comment describing pci_p2pdma_distance_many() still referred to
> the devices being behind the same root port. This no longer applies
> so reword the documentation.
Looks good,
Reviewed-by: Christoph Hellwig
Hi Hugues,
On Wed, Aug 14, 2019 at 03:48:51PM +0200, Hugues Fruchet wrote:
> Add a trace of the set of supported fourcc/mbus_code which
> intersect between DCMI and source sub-device.
>
> Signed-off-by: Hugues Fruchet
> ---
> drivers/media/platform/stm32/stm32-dcmi.c | 12 ++--
> 1 file
On Mon, Aug 12, 2019 at 11:30:47AM -0600, Logan Gunthorpe wrote:
> Now that we map the requests correctly we can remove the iommu_present()
> restriction.
Looks good,
Reviewed-by: Christoph Hellwig
On Mon, Aug 12, 2019 at 11:30:46AM -0600, Logan Gunthorpe wrote:
> Any requests that traverse the host bridge will need to be mapped into the
> IOMMU, so call dma_map_sg() inside pci_p2pdma_map_sg() when appropriate.
>
> Similarly, call dma_unmap_sg() inside pci_p2pdma_unmap_sg().
>
> Link: https
On Mon, Aug 12, 2019 at 11:30:45AM -0600, Logan Gunthorpe wrote:
> When upstream_bridge_distance() is called, store the method required to map
> the DMA transfers in an xarray so it can be looked up efficiently on the
> hot path in pci_p2pdma_map_sg().
>
> Link: https://lore.kernel.org/r/201907301
On Mon, Aug 12, 2019 at 11:30:44AM -0600, Logan Gunthorpe wrote:
> Factor out the bus-only mapping into its own static function. No
> functional changes. The original pci_p2pdma_map_sg_attrs() will be used to
> decide whether this is an appropriate way to map.
>
> Link: https://lore.kernel.org/r/
On Mon, Aug 12, 2019 at 11:30:43AM -0600, Logan Gunthorpe wrote:
> Add pci_p2pdma_unmap_sg() to the two places that call pci_p2pdma_map_sg().
>
> This is a prep patch to introduce correct mappings for p2pdma transactions
> that go through the root complex.
I personally wouldn't split it from actu
This patch-set includes cleanups and bugfix for the HNS3 ethernet
controller driver.
[patch 01/06 - 03/06] adds some cleanups.
[patch 04/06] changes the print level of RAS.
[patch 05/06] fixes a bug related to MAC TNL.
[patch 06/06] adds phy_attached_info().
Guojia Liao (3):
net: hns3: add o
On Mon, Aug 12, 2019 at 11:30:42AM -0600, Logan Gunthorpe wrote:
> This is to match the dma_map_sg() API which this function will have to call
> in an future patch.
>
> Add a pci_p2pdma_map_sg_attrs() function and helper to call it with no
> attributes just like the dma_map_sg() function.
>
> Lin
From: Guojia Liao
Some temporary variables do not need to be initialized that
they will be set before used, so this patch deletes the
initialization value of these temporary variables.
Signed-off-by: Guojia Liao
Signed-off-by: Guangbin Huang
Signed-off-by: Huzhong Tan
---
drivers/net/etherne
From: Guojia Liao
The pointer type parameter should be declare as const for preventing
from its pointed value being unexpected modified.
The uninitialized variable can not be return directly. The default
return value is 0 if no abnormal result.
This patch fixes the preceding two errors, deletes
MAC TNL interrupt is used to collect statistic info about
link status changing suddenly when netdev is running.
But when stopping netdev, the enabled MAC TNL interrupt is
unnecessary, and may add some noises to the statistic info.
So this patch disables it before stopping MAC.
Fixes: a63457878b12
From: Guojia Liao
To explain some code, this patch adds some comments, and modifies or
merges some comments to make them more neat.
Signed-off-by: Guojia Liao
Signed-off-by: Zhongzhu Liu
Signed-off-by: Weihang Li
Signed-off-by: Guangbin Huang
Signed-off-by: Huazhong Tan
---
drivers/net/eth
From: Xiaofei Tan
This patch changes print level of RAS error log from warning to error.
Because RAS error and its recovery process could cause application
failure. Also uses %u instead of %d when the parameter is unsigned.
Signed-off-by: Xiaofei Tan
Signed-off-by: Weihang Li
Signed-off-by: Hu
From: Yonglong Liu
This patch adds the call to phy_attached_info() to the hns3 driver
to identify which exact PHY drivers and models is in use.
Signed-off-by: Yonglong Liu
Reviewed-by: Yunsheng Lin
Signed-off-by: Huazhong Tan
---
drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_mdio.c | 2 ++
Looks good,
Reviewed-by: Christoph Hellwig
Eric Dumazet [mailto:eric.duma...@gmail.com]
> Sent: Friday, August 16, 2019 2:40 PM
[...]
> tasklet and NAPI are scheduled on the same core (the current
> cpu calling napi_schedule() or tasklet_schedule())
>
> I would rather not add this dubious tasklet, and instead try to understand
> what is wr
On Wed, Aug 7, 2019 at 2:35 PM Jinpu Wang wrote:
>
> On Wed, Aug 7, 2019 at 8:36 AM Jinpu Wang wrote:
> >
> > On Wed, Aug 7, 2019 at 1:40 AM NeilBrown wrote:
> > >
> > > On Tue, Aug 06 2019, Jinpu Wang wrote:
> > >
> > > > On Tue, Aug 6, 2019 at 9:54 AM Jinpu Wang
> > > > wrote:
> > > >>
> > >
Hi Greg, hi Laurent,
> From: Greg Kroah-Hartman
> Sent: 15 August 2019 20:05
> Subject: Re: [PATCH v2 3/9] drm: Rename drm_bridge_timings to drm_timings
>
> On Thu, Aug 15, 2019 at 09:06:41PM +0300, Laurent Pinchart wrote:
> > Hi Greg,
> >
> > On Thu, Aug 15, 2019 at 04:53:00PM +0200, Greg Kroah
On Mon, Aug 12, 2019 at 11:30:40AM -0600, Logan Gunthorpe wrote:
> Push both PCI devices into the whitelist checking function seeing some
> hardware will require us ensuring they are on the same host bridge.
>
> At the same time we rename root_complex_whitelist() to
> host_bridge_whitelist() to ma
On Mon, Aug 12, 2019 at 11:30:39AM -0600, Logan Gunthorpe wrote:
> When a P2PDMA transfer is rejected due to ACS being set, we can also check
> the whitelist and allow the transactions.
>
> Do this by pushing the whitelist check into the upstream_bridge_distance()
> function.
>
> Link: https://lo
I'd like to announce my first release of kdevops [0] which I am happy to
share with the community. The goal behind this project is to provide a
modern devops framework for Linux kernel development. It is not a tests
suite, it is designed to *use* *any* test suites, and more importantly,
it allows u
On Mon, Aug 12, 2019 at 11:30:38AM -0600, Logan Gunthorpe wrote:
> This is a prep patch to create a second level helper. There are no
> functional changes.
>
> The root complex whitelist code will be moved into this function in a
> subsequent patch.
>
> Link: https://lore.kernel.org/r/20190730163
On Mon, Aug 12, 2019 at 11:30:37AM -0600, Logan Gunthorpe wrote:
> Add constant flags to indicate how two devices will be mapped or if they
> are unsupported. upstream_bridge_distance() will now return the
> mapping type and the distance in a passed-by-reference argument.
>
> This helps annotate t
Hi,
A few more questions below
> > From: Jian-Hong Pan [mailto:jian-h...@endlessm.com]
> >
> > There is a mass of jobs between spin lock and unlock in the hardware
> > IRQ which will occupy much time originally. To make system work more
> > efficiently, this patch moves the jobs to the soft IRQ (
On Mon, Aug 12, 2019 at 11:30:36AM -0600, Logan Gunthorpe wrote:
> The provider will be needed to figure out how to map a device.
>
> Link: https://lore.kernel.org/r/20190730163545.4915-3-log...@deltatee.com
> Signed-off-by: Logan Gunthorpe
> Signed-off-by: Bjorn Helgaas
Looks good,
Reviewed-b
Looks good,
Reviewed-by: Christoph Hellwig
On 16/08/2019 10:46:36+0800, Biwen Li wrote:
> Issue:
> - # hwclock -w
> hwclock: RTC_SET_TIME: Invalid argument
>
> Why:
> - Relative patch: https://lkml.org/lkml/2019/4/3/55 , this patch
> will always check for unwritable registers, it will compare reg
> with max_regist
Le 15/08/2019 à 02:16, Daniel Axtens a écrit :
In the case where KASAN directly allocates memory to back vmalloc
space, don't map the early shadow page over it.
If early shadow page is not mapped, any bad memory access will Oops on
the shadow access instead of Oopsing on the real bad access
> ubifs_assert(c, p < c->gap_lebs + c->lst.idx_lebs);
I've done 50 problem reproduces on different flash devices and made sure that
the assertion was not triggered. See record.txt for details.
-邮件原件-
发件人: chengzhihao
发送时间: 2019年8月14日 9:20
收件人: 'Richard Weinberger'
抄送: Richard Weinberg
> From: Jian-Hong Pan [mailto:jian-h...@endlessm.com]
>
> There is a mass of jobs between spin lock and unlock in the hardware
> IRQ which will occupy much time originally. To make system work more
> efficiently, this patch moves the jobs to the soft IRQ (bottom half) to
> reduce the time in hardw
copy_page() and clear_page() expect page aligned destination, and
use dcbz instruction to clear entire cache lines based on the
assumption that the destination is cache aligned.
As shown during analysis of a bug in BTRFS filesystem, a misaligned
copy_page() can create bugs that are difficult to lo
65;5603;1c
On Fri, Aug 16, 2019 at 12:17:10PM +0530, Bhushan Shah wrote:
> i2c0 bus is exposed by PI-2 BUS in the PineH64, model B.
>
> Signed-off-by: Bhushan Shah
> ---
> Changes in v2:
> - Don't enable the i2c0 node in PineH64 by default
>
> arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dt
On Fri, Aug 16, 2019 at 12:17:09PM +0530, Bhushan Shah wrote:
> Add device-tree nodes for i2c0 to i2c2, and also add relevant pinctrl
> nodes.
>
> Suggested-by: Icenowy Zheng
> Signed-off-by: Bhushan Shah
> ---
> Changes in v2:
> - Add the SoC specific compatible string instead of re-using a31
Le 15/08/2019 à 02:16, Daniel Axtens a écrit :
Hook into vmalloc and vmap, and dynamically allocate real shadow
memory to back the mappings.
Most mappings in vmalloc space are small, requiring less than a full
page of shadow space. Allocating a full shadow page per mapping would
therefore be
On 8/14/19 9:59 PM, Ezequiel Garcia wrote:
> From: Hertz Wong
>
> Add helpers and patch hantro_{drv,v4l2}.c to prepare addition of H264
> decoding support.
>
> Signed-off-by: Hertz Wong
> Signed-off-by: Boris Brezillon
> Tested-by: Philipp Zabel
> ---
> Changes in v6:
> * Fixed duplicated CAB
On 8/14/19 9:59 PM, Ezequiel Garcia wrote:
> The cedrus VPU is slice-based and expects V4L2_PIX_FMT_H264_SLICE
> buffers to contain H264 slices with no start code.
>
> Expose this to userspace with the newly added menu control.
>
> These two controls are specified as mandatory for applications,
>
On Fri, Aug 16, 2019 at 03:25:51PM +0800, Tanwar, Rahul wrote:
>
> On 16/8/2019 2:43 PM, Borislav Petkov wrote:
> > Now to another question: you see how I put my reply to the previous mail
> > *below* the quoted text. Why is yours ontop? Why not put it after mine
> > since you're replying to it, l
> >
> > This patch adds prefix 'v' in disk name for virtio pmem.
> > This differentiates virtio-pmem disks from the pmem disks.
>
> I don't think the small matter that this device does not support
> MAP_SYNC warrants a separate naming scheme. That said I do think we
> need to export this attrib
On Fri, Aug 16, 2019 at 03:21:19PM +0800, Sam Shih wrote:
> From: Ryder Lee
>
> This adds a property "num-pwms" to avoid having an endless
> list of compatibles with no differences for the same driver.
>
> Signed-off-by: Ryder Lee
> Signed-off-by: Sam Shih
> ---
> drivers/pwm/pwm-mediatek.c |
On 8/14/19 9:59 PM, Ezequiel Garcia wrote:
> From: Boris Brezillon
>
> Some stateless decoders don't support per-slice decoding granularity
> (or at least not in a way that would make them efficient or easy to use).
>
> Expose a menu to control the supported decoding modes. Drivers are
> allowed
On 16/8/2019 2:43 PM, Borislav Petkov wrote:
Now to another question: you see how I put my reply to the previous mail
*below* the quoted text. Why is yours ontop? Why not put it after mine
since you're replying to it, like it is usually done on the mailing
lists and thus not confuse the reading
On 16/08/2019 9.56, Wenwen Wang wrote:
> If devm_request_irq() fails to disable all interrupts, no cleanup is
> performed before retuning the error. To fix this issue, invoke
> omap_dma_free() to do the cleanup.
Thank you,
Acked-by: Peter Ujfalusi
> Signed-off-by: Wenwen Wang
> ---
> driver
From: Ryder Lee
This adds a property "num-pwms" for PWM controller.
Signed-off-by: Ryder Lee
Signed-off-by: Sam Shih
---
arch/arm/boot/dts/mt7623.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/mt7623.dtsi b/arch/arm/boot/dts/mt7623.dtsi
index a79f0b6c3429..208e0d19
From: sam shih
This adds pwm support for MT7629.
Signed-off-by: Sam Shih
---
arch/arm/boot/dts/mt7629.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/mt7629.dtsi b/arch/arm/boot/dts/mt7629.dtsi
index 9608bc2ccb3f..10f788a93346 100644
--- a/arch/arm/bo
From: sam shih
This updates bindings for MT7628 pwm controller.
Signed-off-by: Sam Shih
---
Documentation/devicetree/bindings/pwm/pwm-mediatek.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt
b/Documentation/devicetree/bindings/
From: Ryder Lee
This adds a property "num-pwms" to avoid having an endless
list of compatibles with no differences for the same driver.
Signed-off-by: Ryder Lee
Signed-off-by: Sam Shih
---
drivers/pwm/pwm-mediatek.c | 35 ++-
1 file changed, 22 insertions(+), 1
From: Ryder Lee
Instead of using fixed size of arrays, allocate the memory for them
based on the information we get from the chips.
Signed-off-by: Ryder Lee
Signed-off-by: Sam Shih
---
drivers/pwm/pwm-mediatek.c | 76 +++---
1 file changed, 39 insertions(+), 37
On Thu, 2019-08-15 at 12:50 +0100, Will Deacon wrote:
> Ok, I think speaking to Robin helped me a bit with this...
>
> On Thu, Aug 15, 2019 at 06:18:38PM +0800, Yong Wu wrote:
> > On Thu, 2019-08-15 at 10:51 +0100, Will Deacon wrote:
> > > On Thu, Aug 15, 2019 at 04:47:49PM +0800, Yong Wu wrote:
>
701 - 800 of 817 matches
Mail list logo
