On Tue, Jun 23, 2020 at 11:35:47AM -0700, Tim Harvey wrote:
> Add Gateworks System Controller support to Gateworks Ventana boards:
> - add dt bindings for GSC mfd driver and hwmon driver for ADC's and
> fan controllers.
> - add dt bindings for gpio-keys driver for push-button and interrupt
On Thu, Apr 16, 2020 at 04:51:23PM +0200, Sebastian Reichel wrote:
> From: Ian Ray
>
> Use kernel LED interface for the alarm LEDs.
>
> Signed-off-by: Ian Ray
> [Rebased]
> Signed-off-by: Samu Nuutamo
> [Rebased]
> Signed-off-by: Sebastian Reichel
s/imx53: ppd/imx53-ppd in subject.
On Fri, Jul 10, 2020 at 06:00:14PM -0400, Steven Rostedt wrote:
> > +int static_call_text_reserved(void *start, void *end)
> > +{
> > + int ret = __static_call_text_reserved(__start_static_call_sites,
> > + __stop_static_call_sites, start, end);
> > +
> > + if (ret)
> > +
On Fri, Jul 10, 2020 at 06:42:29PM -0400, Steven Rostedt wrote:
> On Fri, 10 Jul 2020 15:38:42 +0200
> Peter Zijlstra wrote:
> > +static int __init test_static_call_init(void)
> > +{
> > + WARN_ON(static_call(sc_selftest)(2) != 3);
> > + static_call_update(sc_selftest, _b);
> > +
On 2020-07-10 23:49, Nicolas Dufresne wrote:
> Le vendredi 10 juillet 2020 à 09:25 -0300, Ezequiel Garcia a écrit :
>> +Nicolas
>>
>> On Fri, 2020-07-10 at 14:05 +0200, Boris Brezillon wrote:
>>> On Fri, 10 Jul 2020 08:50:28 -0300
>>> Ezequiel Garcia wrote:
>>>
On Fri, 2020-07-10 at 10:13
If the user mode APP of drv-mode xsk does not process packets fast enough,
the packet receiving speed is lower than the flow rate. For example, the
flow rate is 1Mpps, and the APP processing speed is 10Kpss only, this will
cause a series of problems:
1. If the APP doesn't use wakeup mechanism, in
On Fri, Jul 10, 2020 at 06:13:31PM -0400, Steven Rostedt wrote:
> On Fri, 10 Jul 2020 15:38:40 +0200
> Peter Zijlstra wrote:
>
> > From: Josh Poimboeuf
> >
> > Add the x86 out-of-line static call implementation. For each key, a
> > permanent trampoline is created which is the destination for
The following commit has been merged into the locking/core branch of tip:
Commit-ID: 859d069ee1ddd87862e1d6a356a82ed417dbeb67
Gitweb:
https://git.kernel.org/tip/859d069ee1ddd87862e1d6a356a82ed417dbeb67
Author:Peter Zijlstra
AuthorDate:Wed, 27 May 2020 15:00:57 +02:00
The following commit has been merged into the locking/core branch of tip:
Commit-ID: 248591f5d257a19c1cba9ab9da3536bfbc2f0149
Gitweb:
https://git.kernel.org/tip/248591f5d257a19c1cba9ab9da3536bfbc2f0149
Author:Marco Elver
AuthorDate:Wed, 24 Jun 2020 13:32:46 +02:00
The following commit has been merged into the locking/core branch of tip:
Commit-ID: f9ad4a5f3f20bee022b1bdde94e5ece6dc0b0edc
Gitweb:
https://git.kernel.org/tip/f9ad4a5f3f20bee022b1bdde94e5ece6dc0b0edc
Author:Peter Zijlstra
AuthorDate:Wed, 27 May 2020 13:03:26 +02:00
The following commit has been merged into the locking/core branch of tip:
Commit-ID: d6bdceb6c2276276c0392b926ccd2e5991d5cb9a
Gitweb:
https://git.kernel.org/tip/d6bdceb6c2276276c0392b926ccd2e5991d5cb9a
Author:Peter Zijlstra
AuthorDate:Fri, 29 May 2020 22:41:01 +02:00
The following commit has been merged into the locking/core branch of tip:
Commit-ID: 28e5bfd81c8de77504703adf24ceff9301e3c7be
Gitweb:
https://git.kernel.org/tip/28e5bfd81c8de77504703adf24ceff9301e3c7be
Author:Peter Zijlstra
AuthorDate:Fri, 29 May 2020 22:41:05 +02:00
The following commit has been merged into the locking/core branch of tip:
Commit-ID: ba1f2b2eaa2a529dba722507c55ff3d761d325dd
Gitweb:
https://git.kernel.org/tip/ba1f2b2eaa2a529dba722507c55ff3d761d325dd
Author:Peter Zijlstra
AuthorDate:Wed, 27 May 2020 15:50:29 +02:00
The following commit has been merged into the locking/core branch of tip:
Commit-ID: 48017e5481ce85ba52c4cff082cad5f021c4b413
Gitweb:
https://git.kernel.org/tip/48017e5481ce85ba52c4cff082cad5f021c4b413
Author:Peter Zijlstra
AuthorDate:Fri, 29 May 2020 22:40:58 +02:00
The following commit has been merged into the locking/core branch of tip:
Commit-ID: a6342915881a687b07847b7c57628de07a256525
Gitweb:
https://git.kernel.org/tip/a6342915881a687b07847b7c57628de07a256525
Author:Peter Zijlstra
AuthorDate:Mon, 22 Jun 2020 17:21:58 +02:00
The following commit has been merged into the locking/core branch of tip:
Commit-ID: a21ee6055c30ce68c4e201c6496f0ed2a1936230
Gitweb:
https://git.kernel.org/tip/a21ee6055c30ce68c4e201c6496f0ed2a1936230
Author:Peter Zijlstra
AuthorDate:Mon, 25 May 2020 12:22:41 +02:00
Shakeel Butt writes:
The vmstat pgrefill is useful together with pgscan and pgsteal stats to
measure the reclaim efficiency. However vmstat's pgrefill is not updated
consistently at system level. It gets updated for both global and memcg
reclaim however pgscan and pgsteal are updated for only
> The wrappers in include/linux/pci-dma-compat.h should go away.
>
> The patch has been generated with the coccinelle script bellow.
* I suggest to avoid a typo in a word at the sentence end.
* The script for the semantic patch language could be a bit nicer
by the application of disjunctions
Hi!
> Some LED controllers may come with an internal HW triggering mechanism
> for the LED and an ability to switch between user control of the LED,
> or the internal control. One such example is AXP20X PMIC, that allows
> wither for user control of the LED, or for internal control based on
> the
On 11/7/2020 12:31 am, Rob Herring wrote:
On Fri, 10 Jul 2020 10:15:35 +0800, Chris Ruehl wrote:
Add documentation for the newly added DTS support in the shtc1 driver.
To align with the drivers logic to have high precision by default
a boolean sensirion,low_precision is used to switch to low
On 2020-06-08 19:22, Sasha Levin wrote:
> From: Serge Semin
>
> [ Upstream commit ed26aacfb5f71eecb20a51c4467da440cb719d66 ]
>
> Loops-per-jiffies is a special number which represents a number of
> noop-loop cycles per CPU-scheduler quantum - jiffies. As you
> understand aside from CPU-specific
On Fri, Jul 10, 2020 at 06:31:55PM -0400, Steven Rostedt wrote:
> On Fri, 10 Jul 2020 15:38:41 +0200
> Peter Zijlstra wrote:
> > + /* find key symbol */
> > + key_name = strdup(insn->call_dest->name);
>
> Should check for failed allocation of strdup().
Rigt, I'll go add the
Mr Alfred Chow is my name, I have an interesting business proposal of
$38,980,369.00 only for you to transact with me from my bank to your country.
Reply back for more details if interested.
Alfred.
Hi Greg,
/sys/class/power_supply//signal_strength
What units are this in? The "value" means what?
--> Unit is KHZ, the return value is also integer, the "value" means the
working frequency of receiver chip of wireless charging.
B
Fei Jiang
-邮件原件-
发件人: Greg KH
发送时间: 2020年7月10日 18:01
> The wrappers in include/linux/pci-dma-compat.h should go away.
>
> The patch has been generated with the coccinelle script bellow.
* I suggest to avoid a typo in a word at the sentence end.
* The script for the semantic patch language could be a bit nicer
by the application of a disjunction
On Fri, 10 Jul 2020 17:10:55 +0100,
Doug Anderson wrote:
>
> Hi,
>
> On Fri, Jul 10, 2020 at 2:03 AM Marc Zyngier wrote:
> >
> > Hi Doug,
[...]
> >
> > > + type = val ? IRQ_TYPE_EDGE_FALLING : IRQ_TYPE_EDGE_RISING;
> > > +
> > > + raw_spin_lock_irqsave(>lock, flags);
> >
> > What is
Hi, list
I have frequently faced sort lockups and hard lockups.
Here are some example logs:
1. Watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [cantest:1669]
2. NMI watchdog: Watchdog detected hard LOCKUP on CPU 0
What methods or tools could be used to investigate the causes of hard
or soft
On Sat, 11 Jul 2020 09:08:30 +0200,
Navid Emamdoost wrote:
>
> In the implementation of snd_trident_create(), the allocated trident is
> leaked if snd_trident_mixer() fails. Release via snd_trident_free().
No, this patch would result in double-free.
The manual release of trident object isn't
On Fri, 10 Jul 2020 12:37:47 -0700
Joe Perches wrote:
> On Fri, 2020-07-10 at 21:04 +0200, Alexander A. Klimov wrote:
> > Rationale:
> > Documentation/arm/ixp4xx.rst contains "xdp" as part of "ixdp465"
> > which has nothing to do with XDP.
> >
> > Signed-off-by: Alexander A. Klimov
> > ---
> >
On Thu, Jul 09, 2020 at 11:35:22PM +0200, Michael Walle wrote:
> This is a resend [now a new v6] of the series because the conversion to the
> phylink interface will likely take longer:
> https://lore.kernel.org/netdev/CA+h21hpBodyY8CtNH2ktRdc2FqPi=Fjp94=vvzvzsvbnvnf...@mail.gmail.com/
> Also the
On Mon, Jul 06, 2020 at 04:58:47PM +0100, Lorenzo Pieralisi wrote:
> On Tue, Jun 02, 2020 at 09:01:13AM -0600, Rob Herring wrote:
>
> [...]
>
> > > The other 2 error cases as well don't print the resource name as far as
> > > I recall (they will at least print the resource start/end).
> >
> >
Hi Gustavo
Thanks for the feedback.
I'll re-submit the patch.
Many thanks
john
On Fri, Jul 10, 2020 at 03:44:53PM -0500, Gustavo A. R. Silva wrote:
>
>
> On 7/10/20 15:16, John Oldman wrote:
> > clear below issues reported by checkpatch.pl:
> >
> > CHECK: Using comparison to true is error
Dear.Friend
I am Mrs. Abibatu. I am sending this brief letter to solicit
your partnership to transfer a sum of 11.9 Million Dollars into your
reliable account as my business partner. However, it's my urgent need
for foreign partner that made me to contact you for this transaction.
Further details
The wrappers in include/linux/pci-dma-compat.h should go away.
The patch has been generated with the coccinelle script bellow.
It has been compile tested.
When memory is allocated, GFP_ATOMIC should be used to be consistent with
the surrounding code.
@@
@@
-PCI_DMA_BIDIRECTIONAL
+
Hello,
syzbot found the following crash on:
HEAD commit:9e50b94b Add linux-next specific files for 20200703
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14a5cbcb10
kernel config: https://syzkaller.appspot.com/x/.config?x=f99cc0faa1476ed6
dashboard
Add more information, the name of the resource will be printed when the
request memory region or remapping of configuration space fails in the
devm_request_mem_region() function.
Signed-off-by: Dejin Zheng
---
drivers/pci/pci.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff
On Fri, 2020-07-10 at 16:13 +0200, Joerg Roedel wrote:
> On Fri, Jul 03, 2020 at 12:41:17PM +0800, Chao Hao wrote:
> > Chao Hao (10):
> > dt-bindings: mediatek: Add bindings for MT6779
> > iommu/mediatek: Rename the register STANDARD_AXI_MODE(0x48) to MISC_CTRL
> > iommu/mediatek: Use a u32
Hello,
syzbot found the following crash on:
HEAD commit:42f82040 Merge tag 'drm-fixes-2020-07-10' of git://anongit..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12d8033310
kernel config: https://syzkaller.appspot.com/x/.config?x=66ad203c2bb6d8b
: mips-randconfig-r014-20200711 (attached as .config)
compiler: mips-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout
In the implementation of snd_trident_create(), the allocated trident is
leaked if snd_trident_mixer() fails. Release via snd_trident_free().
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Signed-off-by: Navid Emamdoost
---
sound/pci/trident/trident_main.c | 5 -
1 file changed, 4 insertions(+), 1
Hello,
syzbot found the following crash on:
HEAD commit:7cc2a8ea Merge tag 'block-5.8-2020-07-01' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=135403a310
kernel config: https://syzkaller.appspot.com/x/.config?x=7be693511b29b338
Hello,
syzbot found the following crash on:
HEAD commit:7cc2a8ea Merge tag 'block-5.8-2020-07-01' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15dd7d8310
kernel config: https://syzkaller.appspot.com/x/.config?x=7be693511b29b338
Add "struct mtk_iommu_data *" in the "struct mtk_iommu_domain",
reduce the call mtk_iommu_get_m4u_data().
No functional change.
Signed-off-by: Yong Wu
---
drivers/iommu/mtk_iommu.c | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/drivers/iommu/mtk_iommu.c
Add mt8192 smi support.
Signed-off-by: Yong Wu
---
drivers/memory/mtk-smi.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/drivers/memory/mtk-smi.c b/drivers/memory/mtk-smi.c
index f2f6100c74ef..5d0268630e70 100644
--- a/drivers/memory/mtk-smi.c
+++
If the iova is over 32bit, the fault status register bit is a little
different. Add a flag for the special register bits.
Signed-off-by: Yong Wu
---
drivers/iommu/mtk_iommu.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/mtk_iommu.c
Add mt8192 iommu support.
Signed-off-by: Yong Wu
---
drivers/iommu/mtk_iommu.c | 20
drivers/iommu/mtk_iommu.h | 1 +
2 files changed, 21 insertions(+)
diff --git a/drivers/iommu/mtk_iommu.c b/drivers/iommu/mtk_iommu.c
index a4ac41e60c4f..da7d055af919 100644
---
Some HW IP(ex: CCU) require the special iova range. That means the
iova got from dma_alloc_attrs for that devices must locate in his
special range. In this patch, we allocate a special iova_range for
each a special requirement and create each a iommu domain for each
a iova_range.
meanwhile we
Originally MTK_IOMMU could depend on ARM || ARM64.
Both build ok. actually the source code don't support ARM.
this patch changes it only depend on ARM64.
This is a preparing patch for support multi-domain.
otherwise it will build warning in ARM case.
This is the build warning log:
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
we should enable its power before M4U hw initial. and disable it after HW
initialize.
When the
Defaultly the iova range is 0-4G. here we add a single-domain(0-4G)
for the previous SoC. this also is a preparing patch for supporting
multi-domains.
Signed-off-by: Yong Wu
---
drivers/iommu/mtk_iommu.c | 12
1 file changed, 12 insertions(+)
diff --git a/drivers/iommu/mtk_iommu.c
For multiple iommu_domains, we need to reserve some iova regions, so we
will add mtk_iommu_iova_region structure. It includes the base address
and size of the range.
This is a preparing patch for supporting multi-domain.
Signed-off-by: Anan sun
Signed-off-by: Hao Chao
Signed-off-by: Yong Wu
---
After extending v7s, our pagetable already support iova reach
16GB(34bit). the master got the iova via dma_alloc_attrs may reach
34bits, but its HW register still is 32bit. then how to set the
bit32/bit33 iova? this depend on a SMI larb setting(bank_sel).
we separate whole 16GB iova to four
In the lastest SoC, M4U has its special power domain. thus, If the engine
begin to work, it should help enable the power for M4U firstly.
Currently if the engine work, it always enable the power/clocks for
smi-larbs/smi-common. This patch adds device_link for smi-common and M4U.
then, if
If the iova is 34bit, the iova[32][33] is the bit0/1 in the tlb flush
register. Add a new macro for this.
there is a minor change unrelated with this patch. it also use the new
macro.
Signed-off-by: Yong Wu
---
drivers/iommu/mtk_iommu.c | 10 ++
1 file changed, 6 insertions(+), 4
Hi Catalin,
On 2020/7/11 2:31, Catalin Marinas wrote:
> On Fri, Jul 10, 2020 at 05:44:20PM +0800, Zhenyu Ye wrote:
>> -if ((end - start) >= (MAX_TLBI_OPS * stride)) {
>> +if ((!cpus_have_const_cap(ARM64_HAS_TLBI_RANGE) &&
>> +(end - start) >= (MAX_TLBI_OPS * stride)) ||
>> +
The standard input iova bits is 32. MediaTek quad the lvl1
pagetable(4*lvl1). No change for lvl2 pagetable.
Then the iova bits can reach 34bit.
Signed-off-by: Yong Wu
---
drivers/iommu/io-pgtable-arm-v7s.c | 10 +++---
drivers/iommu/mtk_iommu.c | 2 +-
2 files changed, 8
MediaTek extend the bit5 in lvl1 and lvl2 descriptor as PA34.
Signed-off-by: Yong Wu
---
drivers/iommu/io-pgtable-arm-v7s.c | 9 +++--
drivers/iommu/mtk_iommu.c | 2 +-
include/linux/io-pgtable.h | 4 ++--
3 files changed, 10 insertions(+), 5 deletions(-)
diff --git
Use the common larb-port header in the source code.
Signed-off-by: Yong Wu
---
drivers/iommu/mtk_iommu.c | 7 ---
drivers/iommu/mtk_iommu.h | 1 +
drivers/memory/mtk-smi.c | 1 +
include/soc/mediatek/smi.h | 2 --
4 files changed, 2 insertions(+), 9 deletions(-)
diff --git
As title.
Signed-off-by: Yong Wu
---
drivers/iommu/io-pgtable-arm-v7s.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iommu/io-pgtable-arm-v7s.c
b/drivers/iommu/io-pgtable-arm-v7s.c
index 4272fe4e17f4..01f2a8876808 100644
--- a/drivers/iommu/io-pgtable-arm-v7s.c
Add "cfg" as a parameter for some macros. This is a preparing patch for
mediatek extend the lvl1 pgtable. No functional change.
Signed-off-by: Yong Wu
---
drivers/iommu/io-pgtable-arm-v7s.c | 34 +++---
1 file changed, 17 insertions(+), 17 deletions(-)
diff --git
This patch adds decriptions for mt8192 IOMMU and SMI.
mt8192 also is MTK IOMMU gen2 which uses ARM Short-Descriptor translation
table format. The M4U-SMI HW diagram is as below:
EMI
|
M4U
|
Extend the max larb number definition as mt8192 has larb_nr over 16.
Signed-off-by: Yong Wu
---
include/dt-bindings/memory/mtk-smi-larb-port.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/dt-bindings/memory/mtk-smi-larb-port.h
This patch mainly adds support for mt8192 IOMMU and SMI.
mt8192 also is MTK IOMMU gen2 which uses ARM Short-Descriptor translation
table format. The M4U-SMI HW diagram is as below:
EMI
|
M4U
Put all the macros about smi larb/port togethers, this is a preparing
patch for extending LARB_NR and adding new dom-id support.
Signed-off-by: Yong Wu
---
include/dt-bindings/memory/mt2712-larb-port.h | 2 +-
include/dt-bindings/memory/mt6779-larb-port.h | 2 +-
In the latest SoC, there are several HW IP require a sepecial iova
range, mainly CCU and VPU has this requirement. Take CCU as a example,
CCU require its iova locate in the range(0x4000_ ~ 0x43ff_).
In this patch we add a domain definition for the special port. This is
a preparing patch
Please try this one:
---
>From 5e86146296fbcd7593da1d9d39b9685a5e6b83be Mon Sep 17 00:00:00 2001
From: Christoph Hellwig
Date: Sat, 11 Jul 2020 08:46:10 +0200
Subject: debugfs: add a proxy stub for ->read_iter
debugfs registrations typically go through a set of proxy ops to deal
with
The wrappers in include/linux/pci-dma-compat.h should go away.
The patch has been generated with the coccinelle script bellow.
It has been compile tested.
This also aligns code with what is in use in '/rsxx/dma.c'
@@
@@
-PCI_DMA_BIDIRECTIONAL
+DMA_BIDIRECTIONAL
@@
@@
-
在 2020/7/11 14:37, Zhihao Cheng 写道:
在 2020/7/7 20:47, Richard Weinberger 写道:
- Ursprüngliche Mail -
Perhaps I misunderstood what commit 32fe905c17f001 ("ubifs: Fix
O_TMPFILE corner case in ubifs_link()") wanted to fix.
I think orphan area is used to remind filesystem don't forget to
The wrappers in include/linux/pci-dma-compat.h should go away.
The patch has been generated with the coccinelle script bellow.
It has been compile tested.
This also aligns code with what is in use in '/rsxx/dma.c'
@@
@@
-PCI_DMA_BIDIRECTIONAL
+DMA_BIDIRECTIONAL
@@
@@
-
在 2020/7/7 20:47, Richard Weinberger 写道:
- Ursprüngliche Mail -
Perhaps I misunderstood what commit 32fe905c17f001 ("ubifs: Fix
O_TMPFILE corner case in ubifs_link()") wanted to fix.
I think orphan area is used to remind filesystem don't forget to delete
inodes (whose nlink is 0) in
On Fri, Jul 10, 2020 at 07:30:22PM +0300, Andy Shevchenko wrote:
> On Fri, Jul 10, 2020 at 06:58:06PM +0300, Cristian Ciocaltea wrote:
> > On Fri, Jul 10, 2020 at 03:35:42PM +0200, Greg Kroah-Hartman wrote:
> > > On Fri, Jul 10, 2020 at 03:05:49PM +0300, Cristian Ciocaltea wrote:
>
> ...
>
> > >
> On Jul 10, 2020, at 8:53 PM, Andrii Nakryiko
> wrote:
>
> On Fri, Jul 10, 2020 at 6:30 PM Song Liu wrote:
>>
>> Calling get_perf_callchain() on perf_events from PEBS entries may cause
>> unwinder errors. To fix this issue, the callchain is fetched early. Such
>> perf_events are marked
On Fri, Jul 10, 2020 at 07:39:31PM +0200, Alexander A. Klimov wrote:
> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
>
> Deterministic algorithm:
> For each file:
> If not .svg:
> For each line:
> If
On 2020/07/10 19:56, Greg Kroah-Hartman wrote:
> Where is the over/underflow happening here when we set a size to be so
> small? We should bound the size somewhere, and as you show, that's not
> really working properly, right?
It is bit_clear_margins() where integer underflow is happening
201 - 274 of 274 matches
Mail list logo
