Hello,
I've previously sent a stack of similar patches (with no cover letter),
starting at this patch:
[PATCH 01/14] mwifiex: pcie: properly synchronize, disable interrupts in driver
callbacks
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1405062.html
https://patchwork.kernel.org/p
In rogue cases (due to other bugs) it's possible we try to process an
old command response *after* resetting the device. This could trigger a
double-free (or the SKB can get reallocated elsewhere...causing other
memory corruptions) in mwifiex_pcie_process_cmd_complete().
For safety (and symmetry)
When resetting the device, we might have queued up interrupts that
didn't get a chance to finish processing. We really don't need to handle
them at this point; we just want to make sure they don't cause us to try
to process old commands from before the device was reset.
Signed-off-by: Brian Norris
It's possible for some control interfaces (e.g., scans, set freq) to be
active after we've stopped our main work queue and the netif TX queues.
These don't get completely shut out until we've unregistered the wdevs
and wiphy.
So let's only free command buffers and poison our lists after
wiphy_unre
In general, it's helpful to use the same code for device removal as for
device reset, as this tends to have fewer bugs. Let's move the wiphy
unregistration code into the common reset and removal code.
In particular, it's very hard to properly handle the reset sequence when
something fails. Current
On 07/24/2017 03:49 AM, Paul Burton wrote:
Hi Guenter & all,
On Monday, 24 July 2017 01:39:37 BST Guenter Roeck wrote:
The MIPS Boston board configuration tries to enable CONFIG_PCIE_XILINX.
That doesn't work since PCIE_XILINX depends on ARCH_ZYNQ || MICROBLAZE.
Remove that restriction.
I'd p
'card->dev' is initialized once and is never cleared. Drop the
unnecessary "safety" check, as it simply obscures things, and we don't
do this check everywhere (and therefore it's not really "safe").
Signed-off-by: Brian Norris
---
new in v2
---
drivers/net/wireless/marvell/mwifiex/pcie.c | 13 ++
It has some scary comments about "only being called" from the timeout
handler, so let's help keep it that way.
Signed-off-by: Brian Norris
---
new in v2
---
drivers/net/wireless/marvell/mwifiex/cmdevt.c | 4 +++-
drivers/net/wireless/marvell/mwifiex/main.h | 1 -
2 files changed, 3 insertions(
In testing the mwifiex reset code path, I've noticed KASAN complaining
about some "overwritten poison values" in our RX buffer descriptors.
Because KASAN didn't notice this at the time of a CPU write, this seems
to suggest that the device is writing to this memory.
This makes a little sense, becau
This macro is useful to avoid link error on 32-bit systems.
We have the same definition in two drivers, so move it to
include/linux/kernel.h
While we are here, refactor DIV_ROUND_UP_ULL() by using
DIV_ROUND_DOWN_ULL().
Signed-off-by: Masahiro Yamada
---
drivers/mtd/nand/denali.c | 3 ---
inc
The card_reset() implementation should be setting our state flags and
cancelling commands for us (i.e., in mwifiex_shutdown_drv()), so let's
not do it here.
Also, this debugfs file is useful for testing and debugging the reset
feature, so we shouldn't do extra preparatory steps here, as that might
This print isn't very useful. It's also different between
mwifiex_add_card() and mwifiex_reinit_sw(), and I'd like to consolidate
them eventually.
Signed-off-by: Brian Norris
---
new in v2
---
drivers/net/wireless/marvell/mwifiex/main.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
d
Signed-off-by: Brian Norris
---
v2: no change
---
drivers/net/wireless/marvell/mwifiex/cfp.c | 4 +---
drivers/net/wireless/marvell/mwifiex/sta_cmd.c | 8 ++--
drivers/net/wireless/marvell/mwifiex/sta_cmdresp.c | 5 ++---
3 files changed, 5 insertions(+), 12 deletions(-)
diff --g
After removing the interrupt loop in commit 5d5ddb5e0d9b ("mwifiex:
pcie: don't loop/retry interrupt status checks"), we don't need to keep
track of the cleared interrupts (actually, we didn't need to do that
before, but we *really* don't need to now).
Signed-off-by: Brian Norris
---
new in v2
--
We're open-coding these. Just use the helpers.
Signed-off-by: Brian Norris
---
v2: no change
---
drivers/net/wireless/marvell/mwifiex/init.c | 20 ++--
1 file changed, 2 insertions(+), 18 deletions(-)
diff --git a/drivers/net/wireless/marvell/mwifiex/init.c
b/drivers/net/wirele
It doesn't fail.
Signed-off-by: Brian Norris
---
new in v2; noticed when reworking driver
---
drivers/net/wireless/marvell/mwifiex/cmdevt.c | 6 ++
drivers/net/wireless/marvell/mwifiex/main.h | 2 +-
2 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/net/wireless/marvel
Despite the name (and meticulous comments), this function frees no
memory and does not touch any locks. All it does is "delete" the list
heads -- which just means they'll be dangling, and we'll need to re-init
them if we use them again.
It seems like this code would work OK as a sort of canary for
When we leave the delete interface function, there are still netdev
hooks that might try to process the device. We're short-circuiting some
of that by changing the interface type and clearing ieee80211_ptr. This
means we skip NETDEV_UNREGISTER_FINAL in cfg80211. Fortunately, that is
currently a no-
The .idle_time field *should* be unused, but technically, we're allowing
unitialized stack garbage to pass all the way through to the firmware
host command. Let's zero it out instead.
Signed-off-by: Brian Norris
---
v2: no change
---
drivers/net/wireless/marvell/mwifiex/sta_ioctl.c | 6 +++---
1
In reading through _mwifiex_fw_dpc(), I noticed that after we've
registered our wiphy, we still have error paths that don't free it back
up. Let's do that.
Signed-off-by: Brian Norris
---
v2: no change
---
drivers/net/wireless/marvell/mwifiex/main.c | 3 ++-
1 file changed, 2 insertions(+), 1 de
After removing the interrupt loop in commit 5d5ddb5e0d9b ("mwifiex:
pcie: don't loop/retry interrupt status checks"), there is practically
zero difference between mwifiex_process_pcie_int() (which handled legacy
PCI interrupts and MSI interrupts) and mwifiex_process_msix_int() (which
handled MSI-X
It's always called with 'true' -- we only determine it 'false' locally
within this function. So drop the parameter.
Also, this should be 'bool' (since we use true/false), not 'u32'.
Signed-off-by: Brian Norris
---
v2: no change
---
drivers/net/wireless/marvell/mwifiex/cmdevt.c | 5 +++--
driver
hi all:
We found that the xen-netfront does not have the full function of
ethtool. When the VM's network is configured as xennet, the ethtool
commands provide very little function, such as the lack of Speed value.
Whereas VMware's vmxnet3 network card has the function of ethtool.
We'd like
Michal Hocko writes:
> On Mon 24-07-17 09:57:14, Tejun Heo wrote:
>> On Mon, Jul 24, 2017 at 03:42:40PM +0200, Michal Hocko wrote:
> [...]
>> > My understanding of the pcpu allocator is basically close to zero but it
>> > seems weird to me that we would need many TB of vmalloc address space
>> >
MODULE_DEVICE_TABLE(type, name) creates an alias of type 'extern const
typeof(name)'. If 'name' is already constant the 'const' attribute is
specified twice, which is not allowed in C89 (see discussion at
https://lkml.org/lkml/2017/5/23/1440). Since the kernel is built with
-std=gnu89 clang generat
On Mon, Jul 24, 2017 at 10:43:34AM -0700, Linus Torvalds wrote:
> On Sat, Jul 22, 2017 at 1:25 PM, Eric W. Biederman
> wrote:
> > I played with some clever changes such as limiting the copy to 48 bytes,
> > disabling the memset and the like but I could not get a strong enough
> > signal to say tha
On Tue, 25 Jul 2017 09:15:29 +0900
Masami Hiramatsu wrote:
> > arch/x86/kernel/unwind_frame.c is only compiled when CONFIG_FRAME_POINTER
> > is enabled, but CONFIG_KPROBES does not depend on it.
> >
> > Is unwind_frame.c really where in_entry_code() should be implemented, now
> > that its symbol
Hi Rafael,
If you delete "get" function implement within intel_pstate, the
sysfs interface cpuinfo_cur_freq will display all the time.
To be honest, at the beginning I have consider this way like you
patched, but based two reasons below, it is conservative for us to do that.
1. I am worried a
Prabu,
> As per internal decision, Joao Pinto will be maintainer for DWC UFS
> driver.
Applied to 4.14/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
Arnd,
> This series addresses all warnings that gcc-7 introduces for
> -Wformat-overflow= and turns off the -Wformat-truncation by default
> (they remain enabled with "make W=1").
Applied the SCSI patches. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
Rob,
> Now that we have a custom printf format specifier, convert users of
> full_name to use %pOF instead. This is preparation to remove storing
> of the full path string for each node.
Applied to 4.14/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
The swap readahead is an important mechanism to reduce the swap in
latency. Although pure sequential memory access pattern isn't very
popular for anonymous memory, the space locality is still considered
valid.
In the original swap readahead implementation, the consecutive blocks
in swap device ar
From: Huang Ying
VMA based swap readahead will readahead the virtual pages that is
continuous in the virtual address space. While the original swap
readahead will readahead the swap slots that is continuous in the swap
device. Although VMA based swap readahead is more correct for the
swap slots
From: Huang Ying
The swap cache stats could be gotten only via sysrq, which isn't
convenient in some situation. So the sysfs interface of swap cache
stats is added for that. The added sysfs directories/files are as
follow,
/sys/kernel/mm/swap
/sys/kernel/mm/swap/cache_find_total
/sys/kernel/mm
From: Huang Ying
The sysfs interface to control the VMA based swap readahead is added
as follow,
/sys/kernel/mm/swap/vma_ra_enabled
Enable the VMA based swap readahead algorithm, or use the original
global swap readahead algorithm.
/sys/kernel/mm/swap/vma_ra_max_order
Set the max order of the
From: Huang Ying
The statistics for total readahead pages and total readahead hits are
recorded and exported via the following sysfs interface.
/sys/kernel/mm/swap/ra_hits
/sys/kernel/mm/swap/ra_total
With them, the efficiency of the swap readahead could be measured, so
that the swap readahead
From: Huang Ying
In the original implementation, it is possible that the existing pages
in the swap cache (not newly readahead) could be marked as the
readahead pages. This will cause the statistics of swap readahead be
wrong and influence the swap readahead algorithm too.
This is fixed via mar
From: Huang Ying
The swap readahead is an important mechanism to reduce the swap in
latency. Although pure sequential memory access pattern isn't very
popular for anonymous memory, the space locality is still considered
valid.
In the original swap readahead implementation, the consecutive block
Greg,
> It's better to use the DRIVER_ATTR_RW() and DRIVER_ATTR_RO() macros to
> explicitly show that this is a read/write or read/only sysfs file. So
> convert the remaining SCSI drivers that use the old style to use the
> newer macros.
Applied to 4.14/scsi-queue. Thank you!
--
Martin K. Pet
shuw...@redhat.com,
> Found this issue by kmemleak, a few kb mem was leaked in
> megasas_alloc_cmdlist_fusion when kzalloc failed for one
> megasas_cmd_fusion allocation.
Applied to 4.13/scsi-fixes. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
On Mon, 2017-07-24 at 15:26 -0500, Rob Herring wrote:
> On Fri, Jul 21, 2017 at 10:34:49AM +0800, honghui.zh...@mediatek.com wrote:
> > From: Ryder Lee
> >
> > Add support for MediaTek new generation controller and update related
> > properities.
> >
> > Signed-off-by: Ryder Lee
> > Signed-off-
Improve subject.
Guochun Mao (1):
dt-bindings: mtd: add new compatible strings for mtk nor controller
Documentation/devicetree/bindings/mtd/mtk-quadspi.txt | 2 ++
1 file changed, 2 insertions(+)
--
1.9.1
Add "mediatek,mt2712-nor" and "mediatek,mt7622-nor"
for nor flash node's compatible strings.
Reviewed-by: Matthias Brugger
Signed-off-by: Guochun Mao
---
.../devicetree/bindings/mtd/mtk-quadspi.txt|2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings
Masahiro Yamada (3):
of: remove drivers/of/testcase-data from include search path for CPP
of: remove arch/$(SRCARCH)/boot/dts from include search path for CPP
of: search scripts/dtc/include-prefixes path for both CPP and DTC
scripts/Makefile.lib | 8
1 file changed, 4 insertions(+
This search path was added by commit b5190516b282 ("of: Move testcase
FDT data into drivers/of"). At that time, it was needed for platform
DT files to include testcase data.
It became unnecessary when commit ae9304c9d311 ("Adding selftest
testdata dynamically into live tree") introduced dynamic a
Since commit d5d332d3f7e8 ("devicetree: Move include prefixes from
arch to separate directory"), cross-arch DT reference works well,
but only for CPP style #include directives.
It makes as much sense to share DT between different architectures
by using DTC's /include/ directives.
So, scripts/dtc/
Having arch/$(SRCARCH)/boot/dts as an include search path is not
very useful these days because some architectures such as ARM64,
MIPS have no DT in this directory. Instead, they have DT in vendor
sub-directories.
With some DT files in ARM and PowerPC fixed, we can now drop this
include search pa
On Tue, Jul 25, 2017 at 4:27 AM, Alexander Potapenko wrote:
> On Wed, Jul 19, 2017 at 2:58 AM, Xin Long wrote:
>> On Wed, Jul 19, 2017 at 3:02 AM, Alexander Potapenko
>> wrote:
>>> On Tue, Jul 18, 2017 at 4:55 PM, Alexander Potapenko
>>> wrote:
KMSAN reported use of uninitialized sctp_ad
According to datasheet, BIT5 in reg-0x4800 are used to
enable/disable clock lane gate.
It's wrong to make clock lane free running before
sensor stream on was called, while the mipi phy
are not initialized.
Signed-off-by: Jacob Chen
---
drivers/media/i2c/ov5647.c | 10 +-
1 file changed,
Since the kernel segment registers are not prepared at the
entry of irq-entry code, if a kprobe on such code is
jump-optimized, accessing per-cpu variables may cause
kernel panic.
However, if the kprobe is not optimized, it kicks int3
exception and set segment registers correctly.
This checks prob
On Mon, Jul 24, 2017 at 04:49:27PM -0700, Paul E. McKenney wrote:
> On Mon, Jul 24, 2017 at 04:34:58PM -0700, David Miller wrote:
> > From: "Paul E. McKenney"
> > Date: Mon, 24 Jul 2017 16:20:33 -0700
[ . . . ]
> > That would take a while as it's hard to forcibly set this thing off.
>
> And my
Hi Varadarajan,
[auto build test WARNING on spi/for-next]
[also build test WARNING on v4.13-rc2 next-20170724]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Varadarajan-Narayanan/spi-qup-Fixes
On Tue, 2017-07-25 at 01:46 +, Huaisheng HS1 Ye wrote:
> Hi Rafael,
>
> If you delete "get" function implement within intel_pstate, the
> sysfs interface cpuinfo_cur_freq will display all the
> time.
cpuinfo_cur_freq by definition should show actual frequency HW
frequency. Unless I missed s
在 2017-07-24 15:58，Maxime Ripard 写道：
On Sat, Jul 22, 2017 at 10:28:49AM +0800, Icenowy Zheng wrote:
Allwinner A64 SoC has an EMAC which is used to provide Ethernet
function on several boards.
The EMAC itself doesn't have a fixed MAC address, but the sunxi
mainline U-Boot have the ability to gen
On Tue, Jul 25, 2017 at 11:04:24AM +0800, icen...@aosc.io wrote:
> 在 2017-07-24 15:58，Maxime Ripard 写道：
> > On Sat, Jul 22, 2017 at 10:28:49AM +0800, Icenowy Zheng wrote:
> > > Allwinner A64 SoC has an EMAC which is used to provide Ethernet
> > > function on several boards.
> > >
> > > The EMAC it
On Mon, Jul 24, 2017 at 6:03 AM, Hans Liljestrand
wrote:
> On Sun, Jul 23, 2017 at 08:52:53PM -0700, Kees Cook wrote:
>>
>> Is 14afee4b6092f ("net: convert sock.sk_wmem_alloc from atomic_t to
>> refcount_t") correct? That looks like a statistics counter, not a
>> refcounter? I can't quite tell, th
On Monday 24 July 2017 11:54 PM, Rob Herring wrote:
> On Tue, Jul 18, 2017 at 04:27:15PM +0530, Keerthy wrote:
>> Add a separate compatible for keystone-k2g soc
>>
>> Signed-off-by: Keerthy
>> ---
>> Documentation/devicetree/bindings/gpio/gpio-davinci.txt | 3 ++-
>> drivers/gpio/gpio-davinci.c
On Mon, Jul 24, 2017 at 02:46:00PM +0800, Baolin Wang wrote:
> Hi,
>
> On 六, 7月 22, 2017 at 01:27:31下午 +0530, Vinod Koul wrote:
> > On Tue, Jul 18, 2017 at 03:06:12PM +0800, Baolin Wang wrote:
> > > +static void sprd_dma_set_uid(struct sprd_dma_chn *mchan)
> > > +{
> > > + struct sprd_dma_dev *s
Hi Dave,
On Mon, 24 Jul 2017 16:34:58 -0700 (PDT) David Miller
wrote:
>
> Shoing my ignorance as well, after reading this, for some reason this
> commit below sticks out to me. Maybe I should do a bisect and see if
> it lands on this commit.
>
> That would take a while as it's hard to forcibly
On Mon, Jul 24, 2017 at 10:15:22AM +0200, Miklos Szeredi wrote:
> On Sat, Jul 22, 2017 at 11:30 AM, Amir Goldstein wrote:
> > Bumped into this patch (Now upstream commit 51f8f3c4e225) and realized
> > it is missing cc: stable # v4.8
> >
> > At least this docker PR suggests that regression introduc
Hi Mel,
[auto build test ERROR on mmotm/master]
[also build test ERROR on v4.13-rc2 next-20170724]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Mel-Gorman/mm-Always-flush-VMA-ranges-affected
On 07/23/2017 04:25 PM, Boris Ostrovsky wrote:
On 06/14/2017 01:11 PM, Juergen Gross wrote:
On 14/06/17 18:58, Boris Ostrovsky wrote:
On 06/12/2017 07:53 AM, Juergen Gross wrote:
In a HVM guest the kernel allocates the page for mapping the shared
info structure via extend_brk() today. This
On 19 July 2017 at 00:34, Peter Jones wrote:
> On Tue, Jul 18, 2017 at 04:09:09PM +1000, Dave Airlie wrote:
>> This patch allows the user to disable write combined mapping
>> of the efifb framebuffer console using an nowc option.
>>
>> A customer noticed major slowdowns while logging to the consol
On Mon, Jul 24, 2017 at 02:58:16PM -0700, Paul E. McKenney wrote:
> The sys_membarrier() system call has proven too slow for some use
> cases, which has prompted users to instead rely on TLB shootdown.
> Although TLB shootdown is much faster, it has the slight disadvantage
> of not working at all o
Hi Masami,
[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.13-rc2 next-20170724]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Masami-Hiramatsu/kprobes-x86-Do-not-jump
On Mon, Jul 24, 2017 at 07:34:38PM -0500, Grygorii Strashko wrote:
> Below if pure TBD/RFC version of patch which add kthread worker to PTP core.
> I'm sending it to get you opinion about implementation in general, before
> continue with more changes. Pls, take a look if you have time?
> - are you
Here's PCID v5.
Changes from v4:
- Remove smp_mb__after_atomic() (Peterz)
- Rebase, which involved tiny fixups due to SME
- Add the doc patch, as promised
Andy Lutomirski (2):
x86/mm: Try to preserve old TLB entries using PCID
x86/mm: Improve TLB flush documentation
arch/x86/include/asm/
PCID is a "process context ID" -- it's what other architectures call
an address space ID. Every non-global TLB entry is tagged with a
PCID, only TLB entries that match the currently selected PCID are
used, and we can switch PGDs without flushing the TLB. x86's
PCID is 12 bits.
This is an unortho
Improve comments as requested by PeterZ and also add some
documentation at the top of the file.
Signed-off-by: Andy Lutomirski
---
arch/x86/mm/tlb.c | 43 +--
1 file changed, 33 insertions(+), 10 deletions(-)
diff --git a/arch/x86/mm/tlb.c b/arch/x86/mm/t
Andy Lutomirski wrote:
> Improve comments as requested by PeterZ and also add some
> documentation at the top of the file.
>
> Signed-off-by: Andy Lutomirski
> ---
> arch/x86/mm/tlb.c | 43 +--
> 1 file changed, 33 insertions(+), 10 deletions(-)
>
> diff
Signed-off-by: Prakash Sangappa
---
tools/testing/selftests/vm/userfaultfd.c | 121 +-
1 files changed, 118 insertions(+), 3 deletions(-)
diff --git a/tools/testing/selftests/vm/userfaultfd.c
b/tools/testing/selftests/vm/userfaultfd.c
index 1eae79a..6a43e84 100644
-
Tyrel Datwyler writes:
> On 07/24/2017 03:42 AM, Michael Ellerman wrote:
>> Laurent Vivier writes:
>>
>>> As for commit 68baf692c435 ("powerpc/pseries: Fix of_node_put()
>>> underflow during DLPAR remove"), the call to of_node_put()
>>> must be removed from pSeries_reconfig_remove_node().
>>>
>
Hi Andrea, Mike,
Rsending - fixed email address.
Here is the patch set for the proposed userfaultfd UFFD_FEATURE_SIGBUS
feature, including tests in selftest/vm/userfaultfd.c
Please review.
See following for previous discussion.
http://www.spinics.net/lists/linux-mm/msg129224.html
http://www.s
In some cases, userfaultfd mechanism should just deliver a SIGBUS signal
to the faulting process, instead of the page-fault event. Dealing with
page-fault event using a monitor thread can be an overhead in these
cases. For example applications like the database could use the signaling
mechanism for
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 520eccdfe187591a51ea9ab4c1a024ae4d0f68d9
commit: dd55d44f408419278c00887bfcb2261d0caae350 staging: vboxvideo: Add
vboxvideo to drivers/staging
date: 8 days ago
config: i386-randconfig-x071-07241824 (attach
On Mon, Jul 24, 2017 at 10:04:51PM +0200, Pavel Machek wrote:
> Question for you was... Is the first 1KiB of each ext4 filesystem still
> free and "reserved for a bootloader"?
Yes.
> If I needed more for bcache superblock (8KiB, IIRC), would that be
> easy to accomplish on existing filesystem?
H
Hi all,
Changes since 20170724:
New tree: wberr
Non-merge commits (relative to Linus' tree): 2223
2355 files changed, 84862 insertions(+), 43462 deletions(-)
I have created today's linux-next t
ARM IORT specification(rev. C) has added provision to define proximity
domain in SMMUv3 IORT table. Adding required code to parse Proximity
domain and set numa_node of smmv3 platform devices.
Add code to parse proximity domain in SMMUv3 IORT table to
set numa node mapping for smmuv3 devices.
Sig
On Thu, 2017-07-20 at 16:50 +0200, Hans Verkuil wrote:
> On 19/06/17 07:10, Smitha T Murthy wrote:
> > Added V4l2 controls for HEVC encoder
> >
> > Signed-off-by: Smitha T Murthy
> > ---
> > Documentation/media/uapi/v4l/extended-controls.rst | 364
> > +
> > 1 file changed,
Xhci driver handles USB transaction errors on transfer events,
but transaction errors are possible on address device command
completion events as well.
The xHCI specification (section 4.6.5) says: A USB Transaction
Error Completion Code for an Address Device Command may be due
to a Stall response
The A80 includes an ARM CCI-400 interconnect to support multi-cluster
CPU caches.
Also add the maximum clock frequency for the CPUs, as listed in the
A80 Optimus Board FEX file.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun9i-a80.dtsi | 46
1 fil
CPUCFG is a collection of registers that are mapped to the SoC's signals
from each individual processor core and associated peripherals, such as
resets for processors, L1/L2 cache and other things.
These registers are used for SMP bringup and CPU hotplugging.
Signed-off-by: Chen-Yu Tsai
---
arc
The A80 is a big.LITTLE SoC with 1 cluster of 4 Cortex-A7s and
1 cluster of 4 Cortex-A15s.
This patch adds support to bring up the second cluster and thus all
cores using the common MCPM code. Core/cluster power down has not
been implemented, thus CPU hotplugging and big.LITTLE switcher is
not sup
The PRCM is a collection of clock controls, reset controls, and various
power switches/gates. Some of these can be independently listed and
supported, while a number of CPU related ones are used in tandem with
CPUCFG for SMP bringup and CPU hotplugging.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/b
Hi everyone,
This is a partial resend of my sun9i SMP support with MCPM series from
over two years ago [1]. Not much has changed since then. We've tried
to implement PSCI for both the A80 and A83T. Results were not promising.
The issue is that these two chips have a broken security extensions
impl
On Thu, 2017-07-20 at 18:46 +0300, Stanimir Varbanov wrote:
> Hi,
>
> >>> +
> >>> +* - ``V4L2_MPEG_VIDEO_HEVC_PROFILE_MAIN``
> >>> + - Main profile.
> >>
> >> MAIN10?
> >>
> > No just MAIN.
>
> I haven't because the MFC does not supported it?
>
> If so, I think we have to add MAIN10 for
Is there any update on these patches ?
Thanks,
Suganath Prabu S
On Fri, Jul 14, 2017 at 6:52 PM, Suganath Prabu S
wrote:
> Ventura Series controller are Tri-mode. The controller and
> firmware are capable of supporting NVMe devices and
> PCIe switches to be connected with the controller. This
>
On Fri, 2017-06-30 at 17:28 +1000, Nicholas Piggin wrote:
> On Fri, 30 Jun 2017 10:52:18 +0530
> Abdul Haleem wrote:
>
> > On Fri, 2017-06-30 at 00:45 +1000, Nicholas Piggin wrote:
> > > On Thu, 29 Jun 2017 20:23:05 +1000
> > > Nicholas Piggin wrote:
> > >
> > > > On Thu, 29 Jun 2017 19:36:14 +
Matthew Wilcox writes:
> From: Matthew Wilcox
>
> A relatively common idiom we're missing is a function to fill an area
> of memory with a pattern which is larger than a single byte. I first
> noticed this with a zram patch which wanted to fill a page with an
> 'unsigned long' value. There tur
Hi Linus,
please pull from the 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
to receive the following updates:
Three bug fixes.
Christian Borntraeger (2):
s390/perf: fix problem state detection
s390/mm: set change and reference
On Mon, Jul 24, 2017 at 10:06 PM, Jassi Brar wrote:
> On Mon, Jul 24, 2017 at 9:26 AM, Anup Patel wrote:
>> Hi Jassi,
>>
>> Sorry for the delayed response...
>>
>> On Fri, Jul 21, 2017 at 9:16 PM, Jassi Brar wrote:
>>> Hi Anup,
>>>
>>> On Fri, Jul 21, 2017 at 12:25 PM, Anup Patel
>>> wrote:
>>
On Mon, Jul 24, 2017 at 02:07:41PM -0500, Brijesh Singh wrote:
Subject: Re: [RFC Part1 PATCH v3 01/17] Documentation/x86: Add AMD Secure
Encrypted Virtualization (SEV) descrption
^^
From: Rajendra Nayak
Add PM8994 RPM regulators with their min/max voltages to DB820c.
Signed-off-by: Rajendra Nayak
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 148 +++
1 file changed, 148 insertions(+)
diff --git a/arch/arm64/boo
From: Vivek Gautam
Signed-off-by: Vivek Gautam
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
b/arch/arm64/boot/dts/qcom/msm8996.dtsi
index 395666dcce1b..d0865d2f73
A dump of DTS patches for MSM8996 and DB820c, found in the Linaro landing team
tree.
Bjorn Andersson (3):
ARM64: dts: qcom: Add RPM glink nodes to msm8996
arm64: dts: msm8996: Add modem smp2p nodes
arm64: dts: qcom: msm8996: Specify smd-edge for ADSP
Rajendra Nayak (1):
ARM64: dts: qcom:
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 24
1 file changed, 24 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
b/arch/arm64/boot/dts/qcom/msm8996.dtsi
index 8ebef05e1750..7d909546ca24 100644
--- a/arch/arm64/boot/dts/q
Add the smd-edge node for the adsp, to allow SMD communication with the
ADSP.
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
b/arch/arm64/boot/dts/qcom/msm8996.dtsi
index
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 78 +++
1 file changed, 78 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
b/arch/arm64/boot/dts/qcom/msm8996.dtsi
index 8f085716e258..8ebef05e1750 100644
--- a/arch/arm64
On Mon, Jul 24, 2017 at 9:47 PM, Nadav Amit wrote:
> Andy Lutomirski wrote:
>
>> Improve comments as requested by PeterZ and also add some
>> documentation at the top of the file.
>>
>> Signed-off-by: Andy Lutomirski
>> ---
>> arch/x86/mm/tlb.c | 43 +--
>>
Boris,
On 7/24/17 21:44, Borislav Petkov wrote:
On Mon, Jul 24, 2017 at 09:14:18PM +0700, Suravee Suthikulpanit wrote:
Actually, this is not totally accurate. My apology. This patch is
mainly fix to incorrect core ID in /proc/cpuinfo.
So you're "fixing" only some numbering thing. Because core
901 - 1000 of 1020 matches
Mail list logo
