Device tree documentation for Broadcom Secure Processing Unit
(SPU) crypto hardware.
Signed-off-by: Steve Lin
Signed-off-by: Rob Rice
Acked-by: Rob Herring
---
.../devicetree/bindings/crypto/brcm,spu-crypto.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 D
On Fri, 2017-02-03 at 09:42 -0800, Shannon Nelson wrote:
> In order to allow the underlying LDC and outstanding memory operations
> to potentially catch up with the driver's Tx requests, add a memory
> barrier before checking again for available tx descriptors.
>
> Signed-off-by: Shannon Nelson
>
On 02/03/2017 06:41 AM, Laurent Pinchart wrote:
Hello,
On Wednesday 01 Feb 2017 16:19:27 Steve Longerbeam wrote:
On 02/01/2017 01:30 AM, Philipp Zabel wrote:
media-ctl propagates the output pad format to all remote subdevices'
input pads for all enabled links:
https://git.linuxtv.org/v4l-u
Add Northstar2 device tree entry for Broadcom Secure Processing
Unit (SPU) crypto hardware.
Signed-off-by: Steve Lin
Signed-off-by: Rob Rice
---
arch/arm64/boot/dts/broadcom/ns2.dtsi | 24
1 file changed, 24 insertions(+)
diff --git a/arch/arm64/boot/dts/broadcom/ns2.d
On Fri, 2017-02-03 at 09:42 -0800, Shannon Nelson wrote:
> The ldmvsw driver is specifically for supporting the ldom virtual
> networking by running in the primary ldom and using the LDC to connect
> the remaining ldoms to the outside world via a bridge. With TSO and GSO
> supported while connecte
Changes in v4:
- Added Rob Herring's Acked-by to patch 1/3 for bindings doc
- In response to Herbert's comment, in ahash_export() and
ahash_import(), only copy the hash state, not state params
related to cipher or aead algos.
- Noticed that hmac_offset in iproc_reqctx_s and spu_hash_params
This microbenchmark simulates how the use of different futex types
can affect the actual performanace of userspace rwlock locks. The
usage is:
perf bench futex rwlock
Two sets of simple rwlock lock and unlock functions are implemented
using the wait-wake futexes and glibc rwlock respecti
Currently, the futex state objects can only be located indirectly as
hash bucket => futex_q => futex state
Actually it can be beneficial in some cases to locate the futex state
object directly from the hash bucket without the futex_q middleman.
Therefore, a new list head to link the futex
All the TP futex lock waiters are serialized in the kernel using a
kernel mutex which acts like a wait queue. The order at which the
waiters popped out from the wait queue will affect performance when
exclusive (writer) and shared (reader) lock waiters are mixed in the
queue. The worst case scenari
Unlike wake_up_process(), wake_up_q() doesn't tell us how many
tasks have been woken up. This information can sometimes be useful
for tracking purpose. So wake_up_q() is now modified to return that
information.
Signed-off-by: Waiman Long
---
include/linux/sched/wake_q.h | 2 +-
kernel/futex.c
The tp-futex.txt was updated to add description about shared locking
support.
Signed-off-by: Waiman Long
---
Documentation/tp-futex.txt | 163 +++--
1 file changed, 143 insertions(+), 20 deletions(-)
diff --git a/Documentation/tp-futex.txt b/Documentation
The TP futexes don't have code to handle the death of futex
owners. There are 2 different cases that need to be considered.
As top waiter gets a reference to the task structure of the futex
owner, the task structure will never go away even if the owner dies.
When the futex owner died while the top
This patch extends the futex-mutex and futex-rwlock microbenchmarks to
test userspace mutexes and rwlocks built on top of the TP futexes. We
can then compare the relative performance of those userspace locks
based on different type of futexes.
Signed-off-by: Waiman Long
---
tools/perf/bench/fute
The TP-futexes prefer writers as the code path is much simpler for
them. This may not be good for overall system performance especially
if there is a fair amount of reader activities.
This patch enables kernel reader to steal the lock when the futex is
currently reader-owned and the lock handoff m
For debugging purpose, it is sometimes useful to dump the internal
states in the futex hash bucket table. This patch adds a file
"futex_hash_table" in debugfs root filesystem to dump the internal
futex states.
Signed-off-by: Waiman Long
---
kernel/futex.c | 82 +++
The TP futexes was designed to support userspace mutually exclusive
locks. They are now extended to support userspace reader/writer
locks as well.
Two new futex command codes are added:
1) FUTEX_LOCK_SHARED - to acquire a shared lock (reader-lock)
2) FUTEX_UNLOCK_SHARED - to release a shred lock
On 03/02/17 16:40, Juergen Gross wrote:
> On 03/02/17 17:20, Boris Ostrovsky wrote:
+
+ __HEAD
+
+/* Entry point for PVH guests. */
>>> Could you add some comments about register conetnts at entry?
>> Reference to Xen's docs/misc/hvmlite.markdown would be sifficient?
> I think
This patch adds a new document file on how to use the TP futexes.
Signed-off-by: Waiman Long
---
Documentation/00-INDEX | 2 +
Documentation/tp-futex.txt | 161 +
2 files changed, 163 insertions(+)
create mode 100644 Documentation/tp-futex.txt
As the futex_state structure will be overloaded in later patches
to be used by non-PI futexes, it is necessary to add a type field to
distinguish among different types of futexes.
Signed-off-by: Waiman Long
---
kernel/futex.c | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
Unlike other futexes, TP futexes do not accept the specification of
a timeout value. To align with the other futexes, timeout support is
now added. However, the timeout isn't as precise as the other futex
types due to the fact that timer expiration can't be detected when
the thread is waiting in t
A new futex implementation called throughput-optimized (TP) futexes
is introduced. The goal of this new futex type is to maximize locking
throughput at the expense of fairness and deterministic latency. Its
throughput is higher than that of the wait-wake futexes especially
on systems with a large n
To better understand how the TP futexes are performing, it is useful to
return the internal status on the TP futexes. The FUTEX_LOCK futex(2)
syscall will now return a positive status code if no error happens. The
status code consists of the following 3 fields:
1) Bits 00-07: code on how the lock
Two new helper functions (task_pi_list_add & task_pi_list_del)
are created to consolidate all the pure pi_state_list addition and
insertion codes. The set_owner argument in task_pi_list_add() will
be needed in a later patch.
Signed-off-by: Waiman Long
---
kernel/futex.c | 64
A new futex_setup_timer() helper function is added to consolidate all
the hrtimer_sleeper setup code.
Signed-off-by: Waiman Long
---
kernel/futex.c | 67 --
1 file changed, 37 insertions(+), 30 deletions(-)
diff --git a/kernel/futex.c b/ke
The current TP futexes has no guarantee that the top waiter
(serialization mutex owner) can get the lock within a finite time.
As a result, lock starvation can happen.
A lock handoff mechanism is added to the TP futexes to prevent lock
starvation from happening. The idea is that the top waiter can
Two new helper functions cmpxchg_futex_value() and get_futex_value()
are added to access and change the futex value without the hash
bucket lock. As a result, page fault is enabled and the page will
be faulted in if not present yet.
Signed-off-by: Waiman Long
---
kernel/futex.c | 15 +++
The futex_pi_state structure will be overloaded in later patches to
store state information about non-PI futexes. So the structure name
itself is no longer a good description of its purpose. So its name
is changed to futex_state, a more generic name.
Some of the functions that process the futex st
On Fri, Feb 3, 2017 at 5:25 AM, Peter Zijlstra wrote:
> Provide refcount_t, an atomic_t like primitive built just for
> refcounting.
>
> It provides saturation semantics such that overflow becomes impossible
> and thereby 'spurious' use-after-free is avoided.
Wheee :) Thanks for working on this
This microbenchmark simulates how the use of different futex types
can affect the actual performanace of userspace mutex locks. The
usage is:
perf bench futex mutex
Three sets of simple mutex lock and unlock functions are implemented
using the wait-wake and PI futexes respectively. This
v4->v5:
- Fix 0-day kernel build test compilation warnings.
- Extract out non-TP futexes futex-mutex and futex-rwlock
microbenchmarks as separate patches, as suggested by Arnaldo.
- Rebased to the latest tip tree & use running_clock() instead
of sched_clock().
v3->v4:
- Properly
SLAB as part of its bootstrap pre-creates one kmalloc cache that can fit the
kmem_cache_node management structure, and puts it into the generic kmalloc
cache array (e.g. for 128b objects). The name of this cache is "kmalloc-node",
which is confusing for readers of /proc/slabinfo as the cache is use
On Fri, Feb 03, 2017 at 06:24:38PM +0530, Nayna wrote:
>
>
> On 02/01/2017 11:23 PM, Jarkko Sakkinen wrote:
> > There are two type issues associated with tpm_getcap().
> >
> > You must not do arithmetic with __be32 or __le32 types because sometimes
> > it results incorrect results. Calculations
On Fri, Feb 03, 2017 at 04:14:14PM +0100, Robert Richter wrote:
> On 17.01.17 19:16:56, Will Deacon wrote:
> > I can't really see the trend given that, for system time, your
> > pfn_valid_within results have a variance of ~9 and the early_pfn_valid
> > results have a variance of ~92. Given that the
On Fri, Feb 03, 2017 at 09:52:21AM -0800, Laura Abbott wrote:
> There are multiple architectures that support CONFIG_DEBUG_RODATA and
> CONFIG_SET_MODULE_RONX. These options also now have the ability to be
> turned off at runtime. Move these to an architecture independent
> location and make these
Modes supported:
- 640x480 RAW 8
Signed-off-by: Ramiro Oliveira
Acked-by: Pavel Machek
---
MAINTAINERS| 7 +
drivers/media/i2c/Kconfig | 12 +
drivers/media/i2c/Makefile | 1 +
drivers/media/i2c/ov5647.c | 718 +
4 files changed
Hello,
I'm resending this patchset since it didn't have much feedback, and it
already had two ACKs, one in each patch.
This patchset adds support for the Omnivision OV5647 sensor.
At the moment it only supports 640x480 in RAW 8.
This is the seventh version of the OV5647 camera driver patchset.
Create device tree bindings documentation.
Signed-off-by: Ramiro Oliveira
Acked-by: Rob Herring
---
.../devicetree/bindings/media/i2c/ov5647.txt | 35 ++
1 file changed, 35 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5647.txt
diff -
Simplify the code handling the slave netdevice notifier call by
providing a dsa_slave_changeupper helper for NETDEV_CHANGEUPPER, and so
on (only this event is supported at the moment.)
Return NOTIFY_DONE when we did not care about an event, and NOTIFY_OK
when we were concerned but no error occurre
Add a notifier block per DSA switch, registered against a notifier head
in the switch fabric they belong to.
This infrastructure will allow to propagate fabric-wide events such as
port bridging, VLAN configuration, etc. If a DSA switch driver cares
about cross-chip configuration, such events can b
When a switch fabric is composed of multiple switch chips, these chips
must be programmed accordingly when an event occurred on one of them.
Examples of such event include hardware bridging: when a Linux bridge
spans interconnected chips, they must be programmed to allow external
ports to ingress
The scope of the functions inside net/dsa/slave.c must be the slave
net_device pointer. Change to state setter helper accordingly to
simplify callers.
Signed-off-by: Vivien Didelot
---
net/dsa/slave.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/net/dsa/sla
Collect expired timers in interrupt context to avoid overhead of waking
ktimersoftd on every tick. ktimersoftd now wakes only when one or more
timers are ready, which yields a minor reduction in small latency spikes.
This is implemented by storing lists of expired timers in timer_base,
updated on
When an error is returned during the bridging of a port in a
NETDEV_CHANGEUPPER event, net/core/dev.c rolls back the operation.
Be consistent and unassign dp->bridge_dev when this happens.
In the meantime, add comments to document this behavior.
Signed-off-by: Vivien Didelot
---
net/dsa/slave.
A slave device will now notify the switch fabric once its port is
bridged or unbridged, instead of calling directly its switch operations.
This code allows propagating cross-chip bridging events in the fabric.
Signed-off-by: Vivien Didelot
---
include/net/dsa.h | 10 ++
net/dsa/slave.c
Move the netdevice notifier block register code in slave.c and provide
helpers for dsa.c to register and unregister it.
At the same time, check for errors since (un)register_netdevice_notifier
may fail.
Signed-off-by: Vivien Didelot
---
net/dsa/dsa.c | 10 --
net/dsa/dsa_priv.h |
On Fri, 03 Feb 2017 13:03:50 -0500, Waiman Long said:
> On a 2-socket 36-core E5-2699 v3 system (HT off) running on a 4.10
> WW futex TP futex Glibc
> -
> Total locking ops35,707,234
On Fri, Feb 03, 2017 at 06:40:34PM +0100, Radim Krcmar wrote:
> 2017-02-02 15:47-0200, Marcelo Tosatti:
> > Implement min/max/up/down frequency change
> > KVM hypercalls. To be used by DPDK implementation.
> >
> > Also allow such hypercalls from guest userspace.
> >
> > Signed-off-by: Marcelo To
On Fri, Feb 03, 2017 at 05:43:50PM +0100, Radim Krcmar wrote:
> 2017-02-02 15:47-0200, Marcelo Tosatti:
> > Implement KVM hypercalls for the guest
> > to issue frequency changes.
> >
> > Current situation with DPDK and frequency changes is as follows:
> > An algorithm in the guest decides when to
On 02/03/2017 10:51 AM, Sebastian Andrzej Siewior wrote:
On 2016-12-13 15:44:05 [-0600], Haris Okanovic wrote:
Changed the way timers are collected per Julia and Thomas'
recommendation: Expired timers are now collected in interrupt context
and fired in ktimersoftd to avoid double-walk of `pend
On Fri, Feb 03, 2017 at 09:52:22AM -0800, Laura Abbott wrote:
>
> Both of these options are poorly named. The features they provide are
> necessary for system security and should not be considered debug only.
> Change the name to something that accurately describes what these
> options do.
>
> Si
On Thu, Feb 2, 2017 at 11:29 PM, Al Viro wrote:
>
> get_user_pages() relies upon find_extend_vma() to reject kernel
> addresses; the fast side of get_user_pages_fast() doesn't have anything
> of that sort
It is *supposed* to have it.
See pte_allows_gup(), for example. In particular, it requires
On 02/03/2017 09:30 AM, Alexey Brodkin wrote:
> Hi Andrew,
>
> On Fri, 2017-02-03 at 18:10 +0100, Andrew Lunn wrote:
>> On Fri, Feb 03, 2017 at 07:52:37PM +0300, Alexey Brodkin wrote:
>>>
>>> Current implemntation returns ENODEV if device tree node for
>>> phy is absent. But in reality there're ma
Hanjun, Sinan,
On Wed, Jan 18, 2017 at 08:54:50PM +0800, Hanjun Guo wrote:
> From: Hanjun Guo
>
> With platform msi support landed in the kernel, and the introduction
> of IORT for GICv3 ITS (PCI MSI) and SMMU, the framework for platform msi
> is ready, this patch set add few patches to enable t
On 1/28/2017 1:59 AM, Dan Carpenter wrote:
> On Fri, Jan 27, 2017 at 07:05:52PM -0500, Doug Ledford wrote:
>>> Do you think this patch needs "Fixes:" and "Cc: stable" tags?
>>
>> It does not.
>
> We always should have fixes tags.
>
> When I'm reviewing, I try to look up the patch which introduced
Add the RPM Clock Controller DT node for msm8974-based platforms, so that
drivers can use the clocks provided by the RPM processor.
Signed-off-by: Georgi Djakov
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
From: "Ivan T. Ivanov"
Add initial set of CoreSight components found on Qualcomm
msm8974 and apq8074 based platforms, including the APQ8074
Dragonboard board.
Signed-off-by: Ivan T. Ivanov
Signed-off-by: Georgi Djakov
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 280 +
On Fri, Feb 3, 2017 at 2:59 AM, Anup Patel wrote:
>
>
> On Thu, Feb 2, 2017 at 11:31 AM, Dan Williams
> wrote:
>>
>> On Wed, Feb 1, 2017 at 8:47 PM, Anup Patel
>> wrote:
>> > The DMAENGINE framework assumes that if PQ offload is supported by a
>> > DMA device then all 256 PQ coefficients are sup
On 02/03/2017 01:23 PM, valdis.kletni...@vt.edu wrote:
> On Fri, 03 Feb 2017 13:03:50 -0500, Waiman Long said:
>
>> On a 2-socket 36-core E5-2699 v3 system (HT off) running on a 4.10
>> WW futex TP futex Glibc
>> -
On 02/03/2017 02:11 AM, thathi reddy wrote:
> Hi,
>
> Sorry for disturb, i got work related DSA in Linux,
> I am new to this stuff, Can you please share Documents, if you have.
There is documentation in the kernel sources here:
https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/tre
On 02/03/2017 11:45 PM, Jarkko Sakkinen wrote:
On Fri, Feb 03, 2017 at 06:24:38PM +0530, Nayna wrote:
On 02/01/2017 11:23 PM, Jarkko Sakkinen wrote:
There are two type issues associated with tpm_getcap().
You must not do arithmetic with __be32 or __le32 types because sometimes
it results i
Den 03.02.2017 10.59, skrev Maxime Ripard:
Hi,
Here is an attempt at supporting the ST7789V LCD controller from Sitronix.
What happens if there's another panel driven by ST7789V that needs
a different controller initialization?
Maybe it's better to name it after the panel, not the controller.
On 02/02/2017 02:29 PM, Russell King - ARM Linux wrote:
On Thu, Feb 02, 2017 at 11:12:41AM -0800, Steve Longerbeam wrote:
Here is the current .queue_setup() op in imx-media-capture.c:
static int capture_queue_setup(struct vb2_queue *vq,
unsigned int *nbuffers,
The VC_AUDIO_MAX_MSG_LEN macro is not used anywhere and has coding style
violations.
Signed-off-by: Hendrik v. Raven
---
drivers/staging/bcm2835-audio/vc_vchi_audioserv_defs.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/bcm2835-audio/vc_vchi_audioserv_defs.h
b/drivers/
From: Dave Hansen
'orig_pkru' might have been uninitialized here. Fix it.
Signed-off-by: Dave Hansen
---
b/tools/testing/selftests/x86/protection_keys.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN
tools/testing/selftests/x86/protection_keys.c~pkeys-selftests-cleanru
From: Dave Hansen
The siginfo contains a bunch of information about the fault.
For protection keys, it tells us which protection key's
permissions were violated.
The wrong offset in here leads to reading garbage and thus
failures in the tests.
We should probably eventually move this over to us
The memory protection keys selftests are spewing an uninitialized
variable warning
I also included a fix that affected the 32-bit version of the
pkeys test case. It was parsing the siginfo incorrectly.
Den 03.02.2017 10.59, skrev Maxime Ripard:
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/panel/Kconfig | 4 +-
drivers/gpu/drm/panel/Makefile | 1 +-
drivers/gpu/drm/panel/panel-sitronix-st7789v.c | 435 ++-
3 files changed, 440 inser
Em Fri, 27 Jan 2017 13:55:00 -0800
Eric Anholt escreveu:
> This is derived from the downstream tree's build system, but with just
> a single Kconfig option.
>
> For now the driver only builds on 32-bit arm -- the aarch64 build
> breaks due to the driver using arm-specific cache flushing function
Hi!
Hmm. I moved keyboard between USB ports, and now 4.10-rc6 no longer
boots. v4.6 works ok. Let me try with keyboard unplugged... no, I
could not get it to work. I believe v4.9 and some v4.10-rc's worked,
but I'll have to double check.
Machine is small Intel desktop:
00:00.0 Host bridge: Intel
On Sat, Feb 04, 2017 at 12:16:31AM +0530, Nayna wrote:
>
>
> On 02/03/2017 11:45 PM, Jarkko Sakkinen wrote:
> > On Fri, Feb 03, 2017 at 06:24:38PM +0530, Nayna wrote:
> > >
> > >
> > > On 02/01/2017 11:23 PM, Jarkko Sakkinen wrote:
> > > > There are two type issues associated with tpm_getcap().
On Fri, Feb 03, 2017 at 10:29:23AM -0800, Linus Torvalds wrote:
> On Thu, Feb 2, 2017 at 11:29 PM, Al Viro wrote:
> >
> > get_user_pages() relies upon find_extend_vma() to reject kernel
> > addresses; the fast side of get_user_pages_fast() doesn't have anything
> > of that sort
>
> It is *suppose
2017-02-03 16:14-0200, Marcelo Tosatti:
> On Fri, Feb 03, 2017 at 05:43:50PM +0100, Radim Krcmar wrote:
>> 2017-02-02 15:47-0200, Marcelo Tosatti:
>> > Implement KVM hypercalls for the guest
>> > to issue frequency changes.
>> >
>> > Current situation with DPDK and frequency changes is as follows:
On Mon, Jan 30, 2017 at 2:57 PM, Fabrice Gasnier wrote:
> Add dt documentation for st,stm32-exti-trigger.
> EXTi gpio signal can be routed internally as trigger source for various
> IPs (e.g. for ADC or DAC conversions).
And you say this is done using pin control, elsewhere in the conversation
i
On Fri, Jan 06, 2017 at 06:22:48PM +0530, Kishon Vijay Abraham I wrote:
> Group all the PCI drivers that use designware core in dwc directory.
> dwc IP is capable of operating in both host mode and device mode and
> keeping it inside the *host* directory is misleading.
>
> Cc: Thomas Petazzoni
>
On Fri, 3 Feb 2017, Pavel Machek wrote:
> Hi!
>
> Hmm. I moved keyboard between USB ports, and now 4.10-rc6 no longer
> boots. v4.6 works ok. Let me try with keyboard unplugged... no, I
> could not get it to work. I believe v4.9 and some v4.10-rc's worked,
> but I'll have to double check.
But al
Hi Joerg,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc6]
[cannot apply to iommu/next next-20170203]
[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/Joerg-Roedel/Let
On Fri, 03 Feb 2017 13:42:46 -0500, Waiman Long said:
> This patch set does guarantee some minimum performance level, but it
> can't guarantee fairness for all the lock waiters.
OK, sounds like it's a situation that's statistically unlikely, but it has
protections against starvation so the system
2017-02-03 16:24-0200, Marcelo Tosatti:
> On Fri, Feb 03, 2017 at 06:40:34PM +0100, Radim Krcmar wrote:
>> You can make it one hypercall with an argument.
>
> Fine.
>
>> And the argument doesn't have to be enum {UP, DOWN, MAX, MIN}, but an
>> int, which would also allow you to do -2 steps.
>
> A
On Fri, Feb 3, 2017 at 11:08 AM, Al Viro wrote:
>
> On x86 it does. I don't see anything equivalent in mm/gup.c one, and the
> only kinda-sorta similar thing (access_ok() in __get_user_pages_fast()
> there) is vulnerable to e.g. access via kernel_write().
Yeah, access_ok() is bogus. It needs to
ATTENZIONE;
La cassetta postale ha superato il limite di archiviazione, che è 5 GB come
definiti dall'amministratore, che è attualmente in esecuzione su 10.9GB, non si
può essere in grado di inviare o ricevere nuovi messaggi fino a ri-convalidare
la tua mailbox. Per rinnovare la vostra casella
If we get an unknown 'childmode' value, a number of variables are not
initialized properly:
drivers/iio/adc/rcar-gyroadc.c: In function 'rcar_gyroadc_probe':
drivers/iio/adc/rcar-gyroadc.c:390:5: error: 'num_channels' may be used
uninitialized in this function [-Werror=maybe-uninitialized]
driver
Hi Michael,
Thanks for the review! I'll defer to Anju on most of the aspects, but...
On 2017/02/01 09:53PM, Michael Ellerman wrote:
> Anju T Sudhakar writes:
>
> > +static void optimized_callback(struct optimized_kprobe *op,
> > + struct pt_regs *regs)
> > +{
> > + str
From: Colin Ian King
On an allocation failure of gd, the current exit path is via out_free_devt
which leaves sdpk still allocated and hence it gets leaked. Fix this by
correcting the order of resource free'ing with a change in the error exit
path labels.
Detected by CoverityScan, CID#1399519 ("R
On Mon, Jan 30, 2017 at 3:33 PM, Fabrice Gasnier wrote:
> EXTi[0..15] gpio signal can be routed internally as trigger source for
> ADC or DAC conversions. Configure them as interrupts to configure
> trigger path in HW.
>
> Note: interrupt handler isn't required here, and corresponding interrupt
>
ncore: Make package handling more robust (2017-02-01
> 08:37:27 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
> tags/perf-urgent-for-mingo-4.10-20170203
>
> for you to fetch changes up to aa33b9
On Fri, Jan 06, 2017 at 01:59:08PM -0800, Emil Tantilov wrote:
> Enabling/disabling SRIOV via sysfs by echo-ing multiple values
> simultaneously:
>
> echo 63 > /sys/class/net/ethX/device/sriov_numvfs&
> echo 63 > /sys/class/net/ethX/device/sriov_numvfs
>
> sleep 5
>
> echo 0 > /sys/class/net/eth
On Fri, Feb 3, 2017 at 9:52 AM, Laura Abbott wrote:
> There are multiple architectures that support CONFIG_DEBUG_RODATA and
> CONFIG_SET_MODULE_RONX. These options also now have the ability to be
> turned off at runtime. Move these to an architecture independent
> location and make these options d
This commit enables the NBUS on the TS-4600, using the ts-nbus driver.
---
Changes v1 -> v2:
- rebase on master
- remove the simple-bus compatibility as the root node will now
populate the child nodes (suggested by Rob Herring)
- add the vendor prefix to all gpio (suggested by Rob Herring)
Commit-ID: 8381cdd0e32dd748bd34ca3ace476949948bd793
Gitweb: http://git.kernel.org/tip/8381cdd0e32dd748bd34ca3ace476949948bd793
Author: Namhyung Kim
AuthorDate: Wed, 18 Jan 2017 14:14:56 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 2 Feb 2017 11:39:04 -0300
perf diff: Fix
Add binding documentation for the Technologic Systems NBUS that is used
to interface with peripherals in the FPGA of the TS-4600 SoM.
---
Changes v1 -> v2:
- rebase on master
- remove the simple-bus compatibility as the root node will now
populate child nodes (suggested by Rob Herring)
- u
This patch serie adds support for the TS-4600 boards rev A and B. These
boards, manufactured by Technologic Systems, are based on an i.MX28.
This serie include the support for the watchdog which could be enable
at Linux boot time depending on the bootloader.
The watchdog and few peripherals are i
Commit-ID: aa33b9b9a2ebb00d33c83a5312d4fbf2d5aeba36
Gitweb: http://git.kernel.org/tip/aa33b9b9a2ebb00d33c83a5312d4fbf2d5aeba36
Author: Krister Johansen
AuthorDate: Thu, 5 Jan 2017 22:23:31 -0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 2 Feb 2017 11:39:09 -0300
perf callcha
This adds the documentation for the TS-4600 by Technologic Systems.
Acked-by: Rob Herring
---
Changes v1 -> v2:
- rebase on master
- add ack by Rob Herring
Signed-off-by: Sebastien Bourdelin
---
Documentation/devicetree/bindings/arm/technologic.txt | 5 +
1 file changed, 5 insertions(
These device trees add support for the TS-4600 by Technologic Systems.
More details here:
http://wiki.embeddedarm.com/wiki/TS-4600
---
Changes v1 -> v2:
- rebase on master
Signed-off-by: Sebastien Bourdelin
---
arch/arm/boot/dts/Makefile | 2 +
arch/arm/boot/dts/imx28-ts46
This watchdog is instantiated in a FPGA and can only be access using a
GPIOs bit-banged bus, called the NBUS by Technologic Systems.
The watchdog is made of only one register, called the feed register.
Writing to this register will re-arm the watchdog for a given time (and
enable it if it was disab
Commit-ID: a1c9f97f0b64e6337d9cfcc08c134450934fdd90
Gitweb: http://git.kernel.org/tip/a1c9f97f0b64e6337d9cfcc08c134450934fdd90
Author: Namhyung Kim
AuthorDate: Wed, 18 Jan 2017 14:14:57 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 2 Feb 2017 11:39:09 -0300
perf diff: Fix
This driver implements a GPIOs bit-banged bus, called the NBUS by
Technologic Systems. It is used to communicate with the peripherals in
the FPGA on the TS-4600 SoM.
---
Changes v1 -> v2:
- rebase on master
- the driver now populate its child nodes
- remove the 'default y' option from the Kc
Hi Joerg,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc6]
[cannot apply to iommu/next next-20170203]
[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/Joerg-Roedel/Let
On 01/28, Masahiro Yamada wrote:
> Add clock for the Cadence eMMC controller on LD11/LD20.
> For the other SoCs, the clock for the eMMC controller is included
> in the MIO/SD control block.
>
> Signed-off-by: Masahiro Yamada
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a me
On 01/28, Masahiro Yamada wrote:
> Add clock line for the Denali NAND controller.
>
> Signed-off-by: Masahiro Yamada
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
401 - 500 of 716 matches
Mail list logo
