The A64 SoC has the same dma engine as the H3 (sun8i), with a
reduced amount of physical channels. Add the proper config data
and compatible string to support it.
Signed-off-by: Stefan Brüns
---
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 4
drivers/dma/sun6i-dma.c
H3 (and A64/H5) have a sligthly different DMA controller compared with
older SoC generations:
- it supports a buswidth of 8 bytes
- it supports burst length of 4 and 16 transfers
- the register offset for the burst lengths are different, it uses bits
[6:7]/[22:23] instead of [7:8]/[23:24] for th
On Monday, August 28, 2017 8:13:14 PM CEST Yazen Ghannam wrote:
> From: Yazen Ghannam
>
> ACPI defines a number of instructions to use for triggering errors. However
> we are currently removing the address resources from the trigger resources
> for only the WRITE_REGISTER_VALUE instruction. This
veral phases of conversion. The series is
here to browse:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=kspp/timer/20170830
Replace open-coded variants of setup_timer() with actual setup_timer() calls:
coccinelle: Improve setup_timer.cocci matching
Run se
On Monday, August 28, 2017 2:07:51 PM CEST Lucas Stach wrote:
> Am Montag, den 28.08.2017, 14:05 +0300 schrieb Leonard Crestez:
> > This patch contains the minimal changes required to support imx6sx OPP
> > of 198 Mhz. Without this patch cpufreq still reports success but the
> > frequency is not ch
On Friday, August 25, 2017 7:00:16 PM CEST Colin King wrote:
> From: Colin Ian King
>
> Don't populate arrays on the stack, instead make them static.
> Makes the object code smaller by over 860 bytes:
>
> Before:
>text data bss dec hex filename
> 10716 5196
On Friday, August 25, 2017 4:31:56 PM CEST Dietmar Eggemann wrote:
> For a more accurate (i.e. frequency- and cpu-invariant) accounting
> the task scheduler needs a frequency-scaling and on a heterogeneous
> system a cpu-scaling correction factor.
>
> This patch-set implements a Frequency Invarian
On 08/30/17 13:14, Josh Poimboeuf wrote:
> On Wed, Aug 30, 2017 at 12:23:24PM -0700, H. Peter Anvin wrote:
>> On 08/30/17 02:43, tip-bot for Josh Poimboeuf wrote:
>>>
>>> Those warnings are caused by an unusual GCC non-optimization where it
>>> uses an intermediate register to adjust the stack poin
Hi all,
On Fri, 25 Aug 2017 10:24:20 +1000 Stephen Rothwell
wrote:
>
> After merging the nfsd tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> fs/nfsd/nfs4proc.c: In function 'nfsd4_getdeviceinfo_release':
> fs/nfsd/nfs4proc.c:1356:8: error: 'gdev' undeclared (first
Hi all,
After merging the xfs tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
fs/xfs/xfs_buf_item.c: In function 'xfs_buf_item_unlock':
fs/xfs/xfs_buf_item.c:573:9: warning: unused variable 'ordered'
[-Wunused-variable]
bool ordered = !!(bip->bli_flags & XFS_B
From: Khalid Aziz
Date: Wed, 30 Aug 2017 17:23:37 -0600
> That is an interesting idea. This would enable TSTATE_MCDE on all
> threads of a process as soon as one thread enables it. If we consider
> the case where the parent creates a shared memory area and spawns a
> bunch of threads. These threa
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/next
head: f95a66ebd95e133984762aa49e15d4a932c24465
commit: 7b32575c82ed5c891b93a4a5961e608a97cdb192 [20/24] rcu: Make RCU CPU
stall warnings check for irq-disabled CPUs
config: arm64-allnoconfig (attached as .con
On Wed, Aug 30, 2017 at 3:06 PM, Andrew Lunn wrote:
> On Wed, Aug 30, 2017 at 12:53:56PM -0700, Tim Harvey wrote:
>> Greetings,
>>
>> I'm seeing RX frame errors when using the mv88e6xxx DSA driver on
>> 4.13-rc7. The board I'm using is a GW5904 [1] which has an IMX6 FEC
>> MAC (eth0) connected via
Initialization of irq_fwd_mask was done using __raw_writel() which
happens to work for all cases except when using ARM BE8 which requires
writel() (with the proper swapping). Move the initialization of the
irq_fwd_mask till later when we have correctly defined our I/O
accessors.
Signed-off-by: Flo
On 08/30/2017 03:48 AM, Marc Zyngier wrote:
> On 29/08/17 19:43, Florian Fainelli wrote:
>> Initialization of irq_fwd_mask was done using __raw_readl() which
>> happens to work for all cases except when using ARM BE8 which requires
>> readl() (with the proper swapping). Move the initialization of t
On Wed, Aug 30, 2017 at 8:22 PM, Tim Harvey wrote:
> On Wed, Aug 30, 2017 at 3:06 PM, Andrew Lunn wrote:
>> On Wed, Aug 30, 2017 at 12:53:56PM -0700, Tim Harvey wrote:
>>> Greetings,
>>>
>>> I'm seeing RX frame errors when using the mv88e6xxx DSA driver on
>>> 4.13-rc7. The board I'm using is a G
On Wed, Aug 30, 2017 at 05:04:56PM +0300, Dan Carpenter wrote:
> The kernfs_get_inode() returns NULL on error, it never returns error
> pointers.
>
> Fixes: aa8188253474 ("kernfs: add exportfs operations")
> Signed-off-by: Dan Carpenter
Acked-by: Tejun Heo
Greg, can you please route this patch
Hello,
On Wed, Aug 30, 2017 at 03:27:55PM +0200, Christian Brauner wrote:
> The following patch was sent a while back by Wolfgang Bumiller to remap
> cpusets
> for a whole subtree in a cgroup v1 cpuset hierarchy. The fact that currently
> this is not possible in a non-racy why is a pretty big lim
On Wed, Aug 30, 2017 at 04:25:54PM -0700, Nadav Amit wrote:
> [cc’ing IOMMU people, which for some reason are not cc’d]
>
> Andrea Arcangeli wrote:
>
> > On Wed, Aug 30, 2017 at 11:00:32AM -0700, Nadav Amit wrote:
> >> It is not trivial to flush TLBs (primary or secondary) without holding the
>
Hello, Neeraj.
On Wed, Aug 30, 2017 at 06:24:09PM +0530, Neeraj Upadhyay wrote:
> There is a potential race between cgroup_exit() and the
> migration path. This race happens because cgroup_exit path
> reads the css_set and does cg_list empty check outside of
> css_set lock. This can potentially ra
On Wed, Aug 30, 2017 at 05:55:45PM -0700, Tejun Heo wrote:
> Would something like the following fix the issue? Thanks.
>
> diff --git a/kernel/cgroup/cgroup.c b/kernel/cgroup/cgroup.c
> index df2e0f1..cd85ca0 100644
> --- a/kernel/cgroup/cgroup.c
> +++ b/kernel/cgroup/cgroup.c
> @@ -683,7 +683,7
Hi all,
Today's linux-next merge of the pm tree got a conflict in:
drivers/acpi/blacklist.c
between commit:
f996c4155d0d ("dmi: Mark all struct dmi_system_id instances const")
from the dmi tree and commit:
5aa5911a0ed9 ("ACPI / blacklist: add acpi_match_platform_list()")
from the pm tr
Hello,
On Wed, Aug 30, 2017 at 06:23:50PM +0530, Neeraj Upadhyay wrote:
> cpuset_hotplug_workfn()
> cgroup_transfer_tasks()
> cgroup_migrate()
> cgroup_migrate_execute()
>
> list_del_init(&task->cg_list)
> cpuset_attach()
> cgroup_taskset_first(ts
On Wed, Aug 30, 2017 at 06:03:19PM -0700, Tejun Heo wrote:
> Oops, more like the following.
>
> diff --git a/kernel/cgroup/cgroup.c b/kernel/cgroup/cgroup.c
> index df2e0f1..6f34025 100644
> --- a/kernel/cgroup/cgroup.c
> +++ b/kernel/cgroup/cgroup.c
> @@ -683,7 +683,7 @@ static void css_set_move_
Hi!
I'm seeing a lot of kmemleak reports like this on 4.13.0-rc6:
unreferenced object 0x88045e62ab08 (size 1024):
comm "apparmor_parser", pid 802, jiffies 4294913386 (age 4794.692s)
hex dump (first 32 bytes):
0c 1b 30 6b 04 88 ff ff 0c 1b 30 6b 04 88 ff ff ..0k..0k
18 ab
On Tue, Aug 29, 2017 at 11:16:18AM +0200, Vlastimil Babka wrote:
> On 08/24/2017 08:36 AM, js1...@gmail.com wrote:
> > From: Joonsoo Kim
> >
> > 0. History
> >
> > This patchset is the follow-up of the discussion about the
> > "Introduce ZONE_CMA (v7)" [1]. Please reference it if more informatio
On Tue, Aug 29, 2017 at 09:33:44AM +0900, Joonsoo Kim wrote:
> On Mon, Aug 28, 2017 at 03:08:29PM +0200, Michal Hocko wrote:
> > On Mon 28-08-17 13:29:29, Vlastimil Babka wrote:
> > > On 08/28/2017 03:11 AM, js1...@gmail.com wrote:
> > > > From: Joonsoo Kim
> > > >
> > > > High-order atomic alloc
On Tue, Aug 29, 2017 at 03:39:45PM +0200, Michal Hocko wrote:
> On Tue 29-08-17 09:45:47, Joonsoo Kim wrote:
> > On Mon, Aug 28, 2017 at 11:56:16AM +0200, Michal Hocko wrote:
> > > On Mon 28-08-17 09:15:52, Joonsoo Kim wrote:
> > > > On Fri, Aug 25, 2017 at 09:38:42AM +0200, Michal Hocko wrote:
> >
> >/* Report late collisions as a frame error. */
> > if (status & (BD_ENET_RX_NO | BD_ENET_RX_CL))
> > ndev->stats.rx_frame_errors++;
> >
> > I don't see anywhere else frame errors are counted, but it would be
> > good
Long,
>> Which kernel version is this patch aimed at?
>
> Martin, thanks for pointing this out. This should also go to stable
> trees.
The reason I asked is that it didn't apply to neither fixes, nor
for-next.
I applied it to 4.13/scsi-fixes by hand and added a stable tag.
--
Martin K. Peters
Nikola,
> aac_convert_sgraw2() kmalloc memory and return -1 on error, which
> should be -ENOMEM. However, nobody is checking return value, so with
> this change, -ENOMEM is propagated to upper layer.
Applied to 4.14/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
Johannes,
> Since commit 7401bc18d1ee ("scsi: qla2xxx: Add FC-NVMe command handling")
> we make use of 'struct nvmefc_fcp_req' in qla24xx_nvme_iocb_entry() without
> including linux/nvme-fc-driver.h where it is defined.
Applied to 4.14/scsi-queue. Thank you!
--
Martin K. Petersen Oracle L
On Wed, 2017-08-30 at 12:46 -0700, Kees Cook wrote:
>
> With CONFIG_ARCH_HAS_REFCOUNT=y and this patch, do you get an earlier splat?
Yup, first gripe below.
[2.448393] refcount_t silent saturation at skb_unref.part.36+0x12/0x1a in
(haveged)[136], uid/euid: 0/0
[2.454975] [ c
Joe Stringer writes:
> On 30 August 2017 at 15:59, Andrew Morton wrote:
>> On Tue, 29 Aug 2017 16:01:14 -0700 Joe Stringer wrote:
>>
>>> Recent changes[0] to make use of __compiletime_assert() from
>>> container_of() increased the usage of this macro, allowing developers to
>>> notice type conf
On Wed, Aug 30, 2017 at 7:09 PM, Mike Galbraith wrote:
> On Wed, 2017-08-30 at 12:46 -0700, Kees Cook wrote:
>>
>> With CONFIG_ARCH_HAS_REFCOUNT=y and this patch, do you get an earlier splat?
>
> Yup, first gripe below.
>
> [2.448393] refcount_t silent saturation at skb_unref.part.36+0x12/0x1a
> Long,
>
> >> Which kernel version is this patch aimed at?
> >
> > Martin, thanks for pointing this out. This should also go to stable
> > trees.
>
> The reason I asked is that it didn't apply to neither fixes, nor for-next.
>
> I applied it to 4.13/scsi-fixes by hand and added a stable tag.
T
On Tuesday, August 29, 2017, Chris Brandt wrote:
> On Tuesday, August 29, 2017, Nicolas Pitre wrote:
> > On Tue, 29 Aug 2017, Chris Brandt wrote:
> >
> > > On Monday, August 28, 2017, Nicolas Pitre wrote:
> > > > OK I moved the lock promotion right at the beginning _before_
> > validating
> > > > t
On Wednesday, August 16, 2017, Nicolas Pitre wrote:
> This series brings a nice refresh to the cramfs filesystem, adding the
> following capabilities:
>
> - Direct memory access, bypassing the block and/or MTD layers entirely.
>
> - Ability to store individual data blocks uncompressed.
>
> - Abi
On Wed, 2017-08-30 at 12:47 +0100, Colin King wrote:
> From: Colin Ian King
connext->connect typo in patch subject
> Trivial fix to typo in printf error message
>
> Signed-off-by: Colin Ian King
> ---
> tools/testing/selftests/bpf/test_maps.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deleti
On Thursday 24 August 2017 01:48 PM, AKASHI Takahiro wrote:
This function, being a variant of walk_system_ram_res() introduced in
commit 8c86e70acead ("resource: provide new functions to walk through
resources"), walks through a list of all the resources of System RAM
in reversed order, i.e., f
On Thu, 31 Aug 2017, Chris Brandt wrote:
> On Wednesday, August 16, 2017, Nicolas Pitre wrote:
> > This series brings a nice refresh to the cramfs filesystem, adding the
> > following capabilities:
[...]
> For this whole series:
>
> Tested-by: Chris Brandt
Thanks
Nicolas
Hi Suganath,
> Theoretically we want to use h/w capability (to translate IEEE to PRP)
> for smaller IO size to leverage h/w capability.
Nobody says we have to use the capability just because the hardware has
it.
Unlike some other operating systems, Linux will only submit I/Os to the
driver that
On 31/08/17 05:02, Bjorn Helgaas wrote:
> On Fri, Aug 11, 2017 at 06:19:33PM +1000, Alexey Kardashevskiy wrote:
>> From: Gavin Shan
>>
>> The PowerNV platform is the only user of pcibios_sriov_disable().
>> The IOV BAR could be shifted by pci_iov_update_resource(). The
>> warning message in the fu
This series is also available based on v4.13-rc4 via git here:
http://git.linaro.org/people/nicolas.pitre/linux xipcramfs
Please consider this an official merge request.
This series brings a nice refresh to the cramfs filesystem, adding the
following capabilities:
- Direct memory access, bypa
Signed-off-by: Nicolas Pitre
Tested-by: Chris Brandt
---
init/do_mounts.c | 8
1 file changed, 8 insertions(+)
diff --git a/init/do_mounts.c b/init/do_mounts.c
index c2de5104aa..43b5817f60 100644
--- a/init/do_mounts.c
+++ b/init/do_mounts.c
@@ -556,6 +556,14 @@ void __init prepare_nam
Two new capabilities are introduced here:
- The ability to store some blocks uncompressed.
- The ability to locate blocks anywhere.
Those capabilities can be used independently, but the combination
opens the possibility for execute-in-place (XIP) of program text segments
that must remain uncompr
Update documentation, pointer to latest tools, appoint myself as
maintainer. Given it's been unloved for so long, I don't expect anyone
will protest.
Signed-off-by: Nicolas Pitre
Tested-by: Chris Brandt
---
Documentation/filesystems/cramfs.txt | 42
MAINTAIN
Small embedded systems typically execute the kernel code in place (XIP)
directly from flash to save on precious RAM usage. This adds the ability
to consume filesystem data directly from flash to the cramfs filesystem
as well. Cramfs is particularly well suited to this feature as it is
very simple a
When cramfs_physmem is used then we have the opportunity to map files
directly from ROM, directly into user space, saving on RAM usage.
This gives us Execute-In-Place (XIP) support.
For a file to be mmap()-able, the map area has to correspond to a range
of uncompressed and contiguous blocks, and i
On 30 August 2017 at 22:45, Stephen Rothwell wrote:
> Hi Jassi,
>
> Commits
>
> da91001cab90 ("mailbox: bcm-flexrm-mailbox: Set IRQ affinity hint for FlexRM
> ring IRQs")
> 6bee3ba26d4d ("mailbox: bcm-flexrm-mailbox: Add debugfs support")
> 73c28265c82b ("mailbox: bcm-flexrm-mailbox: Fix mask use
On Wed, 2017-08-30 at 19:27 -0700, Kees Cook wrote:
> Interesting! Can you try with 633547973ffc3 ("net: convert
> sk_buff.users from atomic_t to refcount_t") reverted? I'll see if
> running haveged will help me trigger this on my system...
With that (plus 230cd1279d001 fix to it) reverted, vbox
Patch "net/ncsi: Configure VLAN tag filter" defined two new callback
functions in include/net/ncsi.h, but neglected the !CONFIG_NET_NCSI
case. This can cause a build error if these are referenced elsewhere
without NCSI enabled, for example in ftgmac100:
>>> ERROR: "ncsi_vlan_rx_kill_vid" [drivers/
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
drivers/net/ethernet/cavium/liquidio/lio_main.c
between commit:
d1d97ee6e3a8 ("liquidio: moved liquidio_napi_drv_callback to lio_core.c")
from the net-next tree and commit:
966a967116e6 ("smp: Avoid using two cache line
hi,
This happens on 4.13.0-rc7+ to commit 42ff72c
After firing up the stress, touch a file in monitoring directory could
hang like forever.
Pretty easy to hit.
Thanks,
Xiong
[ 492.060879] INFO: task touch:2259 blocked for more than 120 seconds.
[ 492.093497] Not tainted 4.13.0-rc7-mast
On August 30, 2017 8:38:46 PM PDT, Samuel Mendoza-Jonas
wrote:
>Patch "net/ncsi: Configure VLAN tag filter" defined two new callback
>functions in include/net/ncsi.h, but neglected the !CONFIG_NET_NCSI
>case. This can cause a build error if these are referenced elsewhere
>without NCSI enabled, fo
On Wed, Aug 30, 2017 at 8:12 PM, Mike Galbraith wrote:
> On Wed, 2017-08-30 at 19:27 -0700, Kees Cook wrote:
>
>> Interesting! Can you try with 633547973ffc3 ("net: convert
>> sk_buff.users from atomic_t to refcount_t") reverted? I'll see if
>> running haveged will help me trigger this on my syste
On Fri, 2017-08-25 at 19:41 +0200, Borislav Petkov wrote:
Thanks Borislav for your feedback!
> On Fri, Aug 18, 2017 at 05:27:43PM -0700, Ricardo Neri wrote:
> > Both head_32.S and head_64.S utilize the same value to initialize the
> > control register CR0. Also, other parts of the kernel might wa
Hi,
I have seen a behavior using kernel threads that I do not understand. I
would like to know if there is a real issue within the kernel or if I am
expecting something that is not possible. I have donned the flame suit.
I would expect the kernel module listed below to load successfully and
run,
On Wed, Aug 30, 2017 at 9:01 PM, Kees Cook wrote:
> On Wed, Aug 30, 2017 at 8:12 PM, Mike Galbraith wrote:
>> On Wed, 2017-08-30 at 19:27 -0700, Kees Cook wrote:
>>
>>> Interesting! Can you try with 633547973ffc3 ("net: convert
>>> sk_buff.users from atomic_t to refcount_t") reverted? I'll see if
On Wed, Aug 30, 2017 at 01:55:36PM -0500, Christopher Bostic wrote:
> Add ability to clear logged faults via sysfs.
>
I am not in favor of such chip specific commands, in this case for several
reasons (besides it being a non-standard attribute).
The logged faults are not read or used by the drive
On Tue, 2017-08-29 at 18:09 +0200, Borislav Petkov wrote:
> On Fri, Aug 18, 2017 at 05:27:46PM -0700, Ricardo Neri wrote:
> > Even though memory addresses are unsigned, the operands used to compute the
> > effective address do have a sign. This is true for ModRM.rm, SIB.base,
> > SIB.index as well
On 08/30/2017 06:28 PM, Jakub Kicinski wrote:
> Hi!
>
> I'm seeing a lot of kmemleak reports like this on 4.13.0-rc6:
>
yep, thanks for the report. I have seen this one and am still trying
to chase it down.
> unreferenced object 0x88045e62ab08 (size 1024):
> comm "apparmor_parser", pid 802
Removed printk statements for debugging. The same information can be
acquired via ftrace, so these print statements are uneccessary.
Signed-off-by: Jonathan Whitaker
---
Changes in v2:
- Wrapped the changelog text to 72 columns.
- Fixed the commit subject to be more clear.
Changes in v3:
Hi all,
Today's linux-next merge of the xen-tip tree got a conflict in:
arch/x86/include/asm/traps.h
between commit:
11a7ffb01703 ("x86/traps: Simplify pagefault tracing logic")
from the tip tree and commit:
ad5b8c4ba323 ("xen: get rid of paravirt op adjust_exception_frame")
from the x
On Wed, Aug 30, 2017 at 12:46:38PM -0700, Sherry Yang wrote:
> On Tue, Aug 29, 2017 at 11:07 PM, Greg Kroah-Hartman
> wrote:
> > On Tue, Aug 29, 2017 at 05:46:57PM -0700, Sherry Yang wrote:
> >> Use helper functions buffer_next and buffer_prev instead
> >> of list_entry to get the next and previou
On Tue, Aug 29, 2017 at 11:32:58PM +0200, Ondrej Zary wrote:
> On Tuesday 29 August 2017 01:42:08 David Miller wrote:
> > From: Greg Kroah-Hartman
> > Date: Sun, 27 Aug 2017 17:03:30 +0200
> >
> > > The IRDA code has long been obsolete and broken. So, to keep people
> > > from trying to use it, a
On Wed, Aug 30, 2017 at 11:10:14PM +0300, Pasi Kärkkäinen wrote:
> Hello everyone,
>
> Recently Nathan March reported on centos-virt list he's getting frequent
> Linux kernel crashes with Linux 4.9 LTS kernel because of the missing patch
> "tty: Fix ldisc crash on reopened tty".
Crashes with "n
Hi all,
Today's linux-next merge of the xen-tip tree got a conflict in:
arch/x86/xen/enlighten_pv.c
between commit:
64b163fab684 ("x86/idt: Unify gate_struct handling for 32/64-bit kernels")
from the tip tree and commit:
ad5b8c4ba323 ("xen: get rid of paravirt op adjust_exception_frame"
On Wed, 2017-08-30 at 21:10 -0700, Kees Cook wrote:
> On Wed, Aug 30, 2017 at 9:01 PM, Kees Cook wrote:
> > On Wed, Aug 30, 2017 at 8:12 PM, Mike Galbraith wrote:
> >> On Wed, 2017-08-30 at 19:27 -0700, Kees Cook wrote:
> >>
> >>> Interesting! Can you try with 633547973ffc3 ("net: convert
> >>> s
If 'clk_prepare_enable()' fails, we must release some resources before
returning. Add a new label in the existing error handling path and 'goto'
there.
Fixes: 260ea95cc027 ("ASoC: atmel: ac97c: Handle return value of
clk_prepare_enable.")
Signed-off-by: Christophe JAILLET
---
sound/atmel/ac97c.
On Wed, Aug 30, 2017 at 04:39:42PM -0700, H. Peter Anvin wrote:
> On 08/30/17 13:14, Josh Poimboeuf wrote:
> > On Wed, Aug 30, 2017 at 12:23:24PM -0700, H. Peter Anvin wrote:
> >> On 08/30/17 02:43, tip-bot for Josh Poimboeuf wrote:
> >>>
> >>> Those warnings are caused by an unusual GCC non-optimi
On 08/30/2017 12:04 PM, Gustavo A. R. Silva wrote:
Refactor code in order to avoid identical code for different branches.
Addresses-Coverity-ID: 1248728
Signed-off-by: Gustavo A. R. Silva
According to Realtek, this change is OK.
Acked-by: Larry Finger
Thanks,
Larry
---
This issue was re
Host drivers have the requirement of implementing PCI hotplug
based on the how their SOC supports it.
Couple of properties have been added. the one to enable
the hotplug feature itself, and the other caters to
the PCI hotplug implementation with the use of gpios.
Signed-off-by: Oza Pawandeep
Ack
These patches bring in PCI hotplug support for iproc family chipsets.
It includes DT binding documentation and, the implementation in
iproc pcie RC driver.
Changes since v3:
Rebased to pci-next
Added; Acked-by: Rob Herring
Changes since v3:
Resend. just to be in sync previous in-flight patches.
This patch implements PCI hotplug support for iproc family chipsets.
iproc based SOC (e.g. Stingray) does not have hotplug controller
integrated.
Hence, standard PCI hotplug framework hooks can-not be used.
e.g. controlled power up/down of slot.
The mechanism, for e.g. Stingray has adopted for PC
Add description for optional device tree property
'prsnt-gpios' for PCI hotplug feature.
Signed-off-by: Oza Pawandeep
Reviewed-by: Ray Jui
Acked-by: Rob Herring
diff --git a/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt
b/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt
i
David Miller writes:
> From: Kalle Valo
> Date: Wed, 30 Aug 2017 20:31:31 +0300
>
>> AFAICS the bug was introduced by 9df86e2e702c6 back in 2010. If the bug
>> has been there for 7 years so waiting for a few more weeks should not
>> hurt.
>
> As a maintainer you have a right to handle bug fixing
Export rproc_elf_get_boot_addr so that it can be
used by any remoteproc to get the bootaddr of the
elf type firmware images. This is used in the
subsequent patch by the q6v5 based remoteproc
while loading its elf based mdt type image.
Signed-off-by: Sricharan R
---
drivers/remoteproc/remoteproc_
Instead of directly assigning reset, fw and rproc ops, put them
in to of_match data and get from that. Currently same ops
are used for all compatibles, but that will change when we add
q6v5-wcss support.
Signed-off-by: Sricharan R
---
drivers/remoteproc/qcom_q6v5_pil.c | 38 +
IPQ8074 has an integrated Hexagon dsp core Q6v5 and a wireless lan
(Lithium) IP. This series adds the remoteproc driver to reset, load
and boot Q6 firmware.
The first patch is to make the mdt_loader authenticate
the firmware only if required, so that the code can be reused for
self-authenticating
Most of the q6v5-pil start function is same for the q6v5-wcss rproc
that will be added later. So split and move out the common pieces
so that the same code can be reused.
Signed-off-by: Sricharan R
---
drivers/remoteproc/qcom_q6v5_pil.c | 166 -
1 file changed
q6v5-wcss core's start function is mostly common
with the q6v5 of msm8996. So reuse that and add
the stop function.
Signed-off-by: Sricharan R
---
drivers/remoteproc/qcom_q6v5_pil.c | 212 +
1 file changed, 212 insertions(+)
diff --git a/drivers/remoteproc/qc
qcom_mdt_load function loads the mdt type firmware and
initialises the secure memory as well. Make the initialisation only
when requested by the caller, so that the function can be used
by self-authenticating remoteproc as well.
Signed-off-by: Sricharan R
---
drivers/soc/qcom/mdt_loader.c
IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan
(Lithium) IP. An mdt type single image format is used for the
firmware. So the mdt_load function can be directly used to load
the firmware. Also add the relevant resets required for this core.
Signed-off-by: Sricharan R
---
.../d
On 08/30/2017 08:42 AM, Gustavo A. R. Silva wrote:
Refactor code in order to avoid identical code for different branches.
This issue was detected with the help of Coccinelle.
Addresses-Coverity-ID: 1226788
Signed-off-by: Gustavo A. R. Silva
---
This issue was reported by Coverity and it was te
These patches bring in PCI hotplug support for iproc family chipsets.
It includes DT binding documentation and, the implementation in
iproc pcie RC driver.
Changes since v5:
[RESEND]
Changes since v4:
Rebased to pci-next
Added; Acked-by: Rob Herring
Changes since v3:
Resend. just to be in sync
Host drivers have the requirement of implementing PCI hotplug
based on the how their SOC supports it.
Couple of properties have been added. the one to enable
the hotplug feature itself, and the other caters to
the PCI hotplug implementation with the use of gpios.
Signed-off-by: Oza Pawandeep
Ack
This patch implements PCI hotplug support for iproc family chipsets.
iproc based SOC (e.g. Stingray) does not have hotplug controller
integrated.
Hence, standard PCI hotplug framework hooks can-not be used.
e.g. controlled power up/down of slot.
The mechanism, for e.g. Stingray has adopted for PC
Add description for optional device tree property
'prsnt-gpios' for PCI hotplug feature.
Signed-off-by: Oza Pawandeep
Reviewed-by: Ray Jui
Acked-by: Rob Herring
diff --git a/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt
b/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt
i
On Thu, Aug 31, 2017 at 6:51 AM, Xiong Zhou wrote:
> hi,
>
> This happens on 4.13.0-rc7+ to commit 42ff72c
Don't understand. Is this a regression? from which commit?
>
> After firing up the stress, touch a file in monitoring directory could
> hang like forever.
>
> Pretty easy to hit.
So are ru
Hi Martin,
Replied inline.
Thanks,
Suganath Prabu S
On Thu, Aug 31, 2017 at 8:35 AM, Martin K. Petersen
wrote:
>
> Hi Suganath,
>
>> Theoretically we want to use h/w capability (to translate IEEE to PRP)
>> for smaller IO size to leverage h/w capability.
>
> Nobody says we have to use the capabi
On Wed, Aug 30, 2017 at 12:30:52PM +0100, Suzuki K Poulose wrote:
> commit 6c0d706b563af732adb094c5bf807437e8963e84 upstream.
>
> In kvm_free_stage2_pgd() we check the stage2 PGD before holding
> the lock and proceed to take the lock if it is valid. And we unmap
> the page tables, followed by rele
From: Andrii Vladyka
Date: Wed, 30 Aug 2017 09:04:35 +0300
> + if (opt_skb)
Trailing whitespace.
> @@ -653,6 +647,36 @@ static int dccp_v6_do_rcv(struct sock *sk, struct
> sk_buff *skb)
> __kfree_skb(opt_skb);
> kfree_skb(skb);
> return 0
>From: Rob Herring [mailto:r...@kernel.org]
>Subject: Re: [PATCH] arm64: dts: Add support for NXP's LX2160A SoC
>
>On Fri, Aug 18, 2017 at 04:25:36PM +0530, Sriram Dash wrote:
>> The QorIQ LX2160A processor is built in the 16FFC process on the
>> Layerscape architecture combining sixteen ARM A72 pr
Looking to lose weight fast in a healthy way?
While it may be very tempting to turn to diet aid solutions that promise
awesome weight loss, it's also important to be cautious about your health.
Recent data show that most diet medicines, drinks and "organic" formulas are
capable of causing a range
On 08/30/2017 05:37 PM, Maxime Ripard wrote:
Hi,
On Mon, Aug 28, 2017 at 09:32:42AM +0300, Stefan Mavrodiev wrote:
From revision J the board uses new phy chip LAN8710. Compared
with RTL8201, RA17 pin is TXERR. It has pullup which causes phy
not to work. To fix this PA17 is muxed with GMAC func
On Thu 31-08-17 10:42:41, Joonsoo Kim wrote:
> On Tue, Aug 29, 2017 at 09:33:44AM +0900, Joonsoo Kim wrote:
> > On Mon, Aug 28, 2017 at 03:08:29PM +0200, Michal Hocko wrote:
> > > On Mon 28-08-17 13:29:29, Vlastimil Babka wrote:
> > > > On 08/28/2017 03:11 AM, js1...@gmail.com wrote:
> > > > > From
On Thu, 2017-08-31 at 06:36 +0200, Greg Kroah-Hartman wrote:
> On Wed, Aug 30, 2017 at 11:10:14PM +0300, Pasi Kärkkäinen wrote:
> > Hello everyone,
> >
> > Recently Nathan March reported on centos-virt list he's getting frequent
> > Linux kernel crashes with Linux 4.9 LTS kernel because of the mis
Hi all,
After merging the xen-tip tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/xen/xen-asm_64.o: In function `xen_trace_page_fault':
(.text+0x174): undefined reference to `trace_page_fault'
Caused by commit
ad5b8c4ba323 ("xen: get rid of paravirt op adjust_e
I'll fix and re-send. Thanks.
On 8/31/2017 8:16 AM, David Miller wrote:
From: Andrii Vladyka
Date: Wed, 30 Aug 2017 09:04:35 +0300
+ if (opt_skb)
Trailing whitespace.
@@ -653,6 +647,36 @@ static int dccp_v6_do_rcv(struct sock *sk, struct sk_buff
*skb)
701 - 800 of 843 matches
Mail list logo
