NanoPi common dtsi supports all components of NEO SBC, so just include it.
Cc: James Pettigrew
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/sun8i-h3-nanopi-neo.dts | 79 +--
1 file changed, 1 insertion(+), 78 deletions(-)
diff --git a/arch/arm/boot/dts/sun8i-h3-nan
This patch provides a common file for NanoPi M1 and Neo SBC.
Those have common features below.
* UART0
* 2 LEDs
* USB host (EHCI3, OHCI3) and PHY
* MicroSD
* GPIO key switch
Cc: James Pettigrew
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/sun8i-h3-nanopi.dtsi | 144 +
NanoPi M1 is the Allwinner H3 based board.
This patch enables UART for debug console, LEDs, GPIO key switch, 3 USB
host ports, a micro SD slot and related power and pin controls by using
NanoPi common dtsi file.
Cc: James Pettigrew
Signed-off-by: Milo Kim
---
arch/arm/boot/dts/sun8i-h3-nanopi-m
NanoPi M1 and NEO have common features, so duplicate properties can be
moved into new dtsi file.
v2:
Add James's copyrights in NanoPi common dtsi file
Milo Kim (3):
ARM: dts: sun8i: Add common dtsi file for NanoPi SBCs
ARM: dts: sun8i: Use the common file in NanoPi NEO SBC
ARM: dts: sun
> -Original Message-
> From: Andy Shevchenko [mailto:andriy.shevche...@linux.intel.com]
> Sent: Thursday, October 27, 2016 4:59 PM
> To: Vadim Pasternak ; dvh...@infradead.org;
> fengguang...@intel.com
> Cc: da...@davemloft.net; ge...@linux-m68k.org; akpm@linux-
> foundation.org; kv...@co
Move mpc85xx.h to include/linux/fsl and rename it to svr.h as a common
header file. This SVR numberspace is used on some ARM chips as well as
PPC, and even to check for a PPC SVR multi-arch drivers would otherwise
need to ifdef the header inclusion and all references to the SVR symbols.
Signed-of
Add the dts node for device configuration unit that provides
general purpose configuration and status for the device.
Signed-off-by: Yangbo Lu
Acked-by: Scott Wood
---
Changes for v5:
- Added this patch
Changes for v6:
- None
Changes for v7:
- None
Changes for v8:
This patchset is used to fix a host version register bug in the T4240-R1.0-R2.0
eSDHC controller. To match the SoC version and revision, 10 previous version
patchsets had tried many methods but all of them were rejected by reviewers.
Such as
- dts compatible method
- syscon method
On Thu, Oct 27, 2016 at 11:45:37PM -0500, Eric W. Biederman wrote:
>
> Mind if I add your tested-by?
>
> To see Linus's tree fail with my patch you can apply the patch below.
> That is the essence of what I changed to fix things. Just ignoring
> dumpable when an mm exists.
Tested-by: Cyrill Gor
Move guts devicetree doc to Documentation/devicetree/bindings/soc/fsl/
since it's used by not only PowerPC but also ARM. And add a specification
for 'little-endian' property.
Signed-off-by: Yangbo Lu
Acked-by: Rob Herring
Acked-by: Scott Wood
---
Changes for v4:
- Added this patch
Chang
Add maintainer entry for Freescale SoC drivers including
the QE library and the GUTS driver now. Also add maintainer
for QE library.
Signed-off-by: Yangbo Lu
Acked-by: Scott Wood
Acked-by: Qiang Zhao
---
Changes for v8:
- Added this patch
Changes for v9:
- Added linux-arm mail l
The global utilities block controls power management, I/O device
enabling, power-onreset(POR) configuration monitoring, alternate
function selection for multiplexed signals,and clock control.
This patch adds a driver to manage and access global utilities block.
Initially only reading SVR and regis
From: Arnd Bergmann
We keep running into cases where device drivers want to know the exact
version of the a SoC they are currently running on. In the past, this has
usually been done through a vendor specific API that can be called by a
driver, or by directly accessing some kind of version regist
The eSDHC of T4240-R1.0-R2.0 has incorrect vender version and spec version.
Acturally the right version numbers should be VVN=0x13 and SVN = 0x1.
This patch adds the GUTS driver support for eSDHC driver to match SoC.
And fix host version to avoid that incorrect version numbers break down
the ADMA d
* Pavel Machek wrote:
> +static void rh_overflow(struct perf_event *event, struct perf_sample_data
> *data, struct pt_regs *regs)
> +{
> + u64 *ts = this_cpu_ptr(&rh_timestamp); /* this is NMI context */
> + u64 now = ktime_get_mono_fast_ns();
> + s64 delta = now - *ts;
> +
> +
We propose Window-Assisted Load Tracking (WALT) as an alternative or additional
load tracking scheme in lieu of or along with PELT, one that in our estimation
better tracks task demand and CPU utilization especially for use cases on
mobile devices. WALT was conceived by Srivatsa Vaddagiri to provi
From: Srivatsa Vaddagiri
Add the necessary hooks to core and the various scheduling
classes that will allow WALT to track CPU utilization and
handle task migration between CPUs as well.
With CONFIG_SCHED_WALT enabled, schedutil will use WALT's cpu
utilization metric by default. This can be switc
From: Srivatsa Vaddagiri
Add the per-task and per-runqueue data structures that
will later be used by Window Assisted Load Tracking (WALT)
to estimate task demand and CPU utilization.
Move cap_scale into sched.h as that will be needed by WALT
as well to implement frequency and capacity invarianc
From: Srivatsa Vaddagiri
This patch implements an alternative window-based CPU utilization
tracking mechanism in the scheduler. Per task and per CPU counters are
updated with utilization statistics using a synchronized (across CPUs)
time source and a single statistic (prev_runnable_sum) is fed to
Hi,
I went through all the users of complete_all() in order to figure out if
we can change the completion code using swait instead of wait. The
motivation for this is to remove another source of non preemptable
unbounded work for -rt.
The complete_all() code uses __wake_up_locked(..., 0) whi
Hi,
Here are some further fixes to our FCSR handling. Just 2 changes at this
time.
The first, very small one, closes an issue where a write made with
ptrace(PTRACE_POKEUSR, ...) to FCSR does not mark the FP context as used.
This is the legacy interface, seldom used these days, having been
Complement commit ac9ad83bc318 ("MIPS: prevent FP context set via ptrace
being discarded") and also initialize the FP context whenever FCSR alone
is written with a PTRACE_POKEUSR request addressing FPC_CSR, rather than
along with the full FPU register set in the case of the PTRACE_SETFPREGS
reque
Sanitize FCSR Cause bit handling, following a trail of past attempts:
* commit 4249548454f7 ("MIPS: ptrace: Fix FP context restoration FCSR
regression"),
* commit 443c44032a54 ("MIPS: Always clear FCSR cause bits after
emulation"),
* commit 64bedffe4968 ("MIPS: Clear [MSA]FPE CSR.Cause after
On Fri, Oct 28, 2016 at 08:43:51AM +0200, Vincent Guittot wrote:
[...]
> > running with? Also do you have any details about the card in case its
> > card specific?
>
> The sdcard is quite common: sandisk ultra 16GB
> and my rootfs is on the sdcard
I'm using rootfs in emmc also have same failure
On Fri, Oct 28, 2016 at 11:00:21AM +0530, Rajesh P8 wrote:
> Hi all,
> I am currently working on porting eas features using 3.18 common
> android kernel. In file kernel/sched/fair.c there is no definition
> for the function "trace_sched_boost_task(task, util, margin);" which
> is present in line
On Fri, Oct 28, 2016 at 12:10:39AM -0700, Vikram Mulukutla wrote:
>
> We propose Window-Assisted Load Tracking (WALT) as an alternative or
> additional
> load tracking scheme in lieu of or along with PELT, one that in our estimation
> better tracks task demand and CPU utilization especially for u
On Thu, Oct 27, 2016 at 05:37:06PM -0200, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> This new function should be used by drivers when setting a implicit
> fence for the plane. It abstracts the fact that the user might have
> chosen explicit fencing instead.
>
> Signed-off-by: Gustavo Pad
On Fri, Oct 28, 2016 at 09:30:26AM +0200, Daniel Vetter wrote:
> On Thu, Oct 27, 2016 at 05:37:06PM -0200, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > This new function should be used by drivers when setting a implicit
> > fence for the plane. It abstracts the fact that the user migh
On Thu, Oct 27, 2016 at 05:37:08PM -0200, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> drm_atomic_set_fence_for_plane() is smart and won't overwrite
> plane_state->fence if the user already set an explicit fence there.
>
> Signed-off-by: Gustavo Padovan
Reviewed-by: Daniel Vetter
> ---
On Thu, Oct 27, 2016 at 05:37:07PM -0200, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> drm_atomic_set_fence_for_plane() is smart and won't overwrite
> plane_state->fence if the user already set an explicit fence there.
>
> Signed-off-by: Gustavo Padovan
Process nit: Please make sure you
Jerome Glisse writes:
> On Wed, Oct 26, 2016 at 04:39:19PM +0530, Aneesh Kumar K.V wrote:
>> Jerome Glisse writes:
>>
>> > On Tue, Oct 25, 2016 at 09:56:35AM +0530, Aneesh Kumar K.V wrote:
>> >> Jerome Glisse writes:
>> >>
>> >> > On Mon, Oct 24, 2016 at 10:01:49AM +0530, Anshuman Khandual wr
On 10/27/2016 05:29 AM, Kirti Wankhede wrote:
> Added blocking notifier to IOMMU TYPE1 driver to notify vendor drivers
> about DMA_UNMAP.
> Exported two APIs vfio_register_notifier() and vfio_unregister_notifier().
> Vendor driver should register notifer using these APIs.
> Vendor driver should use
On Fri, Oct 28, 2016 at 12:10:41AM -0700, Vikram Mulukutla wrote:
> +static int cpu_is_waiting_on_io(struct rq *rq)
> +{
> + if (!walt_io_is_busy)
> + return 0;
> +
> + return atomic_read(&rq->nr_iowait);
> +}
This is just drug induced nonsense. The per-cpu nr_iowait number is
On Fri, Oct 28, 2016 at 04:33:41PM +0900, Jaehoon Chung wrote:
[...]
> >>> Guodong: Is there any bootloader dependency on that change?
> >>
> >> FYI, I use firmwares available in AOSP
> >
> > I tried latest firmware [1], still cannot boot up until revert the
> > patch "arm64: dts: hi6220: add re
On Thu, Oct 27, 2016 at 05:37:09PM -0200, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> There is now a new property called FENCE_FD attached to every plane
> state that receives the sync_file fd from userspace via the atomic commit
> IOCTL.
>
> The fd is then translated to a fence (that may
> -Original Message-
> From: Y.B. Lu
> Sent: Friday, October 28, 2016 2:06 PM
> To: Y.B. Lu; 'Scott Wood'; 'linux-...@vger.kernel.org';
> 'ulf.hans...@linaro.org'; 'Arnd Bergmann'
> Cc: 'linuxppc-...@lists.ozlabs.org'; 'devicet...@vger.kernel.org';
> 'linux-arm-ker...@lists.infradead.org';
On Thu, Oct 27, 2016 at 05:37:10PM -0200, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> Create one timeline context for each CRTC to be able to handle out-fences
> and signal them. It adds a few members to struct drm_crtc: fence_context,
> where we store the context we get from fence_context
On Fri, Oct 28, 2016 at 12:10:41AM -0700, Vikram Mulukutla wrote:
> +u64 walt_ktime_clock(void)
> +{
> + if (unlikely(walt_ktime_suspended))
> + return ktime_to_ns(ktime_last);
> + return ktime_get_ns();
> +}
> +static int walt_suspend(void)
> +{
> + ktime_last = ktime_get(
On Fri, Oct 28, 2016 at 12:10:41AM -0700, Vikram Mulukutla wrote:
> +void walt_finish_migrate(struct task_struct *p, struct rq *dest_rq, bool
> locked)
> +{
> + u64 wallclock;
> + unsigned long flags;
> +
> + if (!p->on_rq && p->state != TASK_WAKING)
> + return;
> +
> +
On Fri, Oct 28, 2016 at 12:10:39AM -0700, Vikram Mulukutla wrote:
> This RFC patch has been tested on live X86 machines with the following sanity
> and benchmark results (thanks to Juri Lelli, Dietmar Eggeman, Patrick Bellasi
> for initial code reviews):
>
> (Tested on an Intel i7 2nd generation C
On Fri, Oct 28, 2016 at 12:10:41AM -0700, Vikram Mulukutla wrote:
> +static int account_cpu_busy_time(struct rq *rq, struct task_struct *p,
> + u64 irqtime, int event)
> +{
> + if (is_idle_task(p)) {
> + /* TASK_WAKE && TASK_MIGRATE is not possible o
On Thu, Oct 27, 2016 at 10:23:24PM +0200, Vincent Stehlé wrote:
> video_device_release() takes a pointer to struct video_device as argument.
> Fix two call sites where the address of the pointer is passed instead.
Sorry, I messed up: please ignore that "fix". The 0day robot made me
realize this is
Hi Laura,
On 28 October 2016 at 01:18, Laura Abbott wrote:
> x86 has an option CONFIG_DEBUG_VIRTUAL to do additional checks
> on virt_to_phys calls. The goal is to catch users who are calling
> virt_to_phys on non-linear addresses immediately. As features
> such as CONFIG_VMAP_STACK get enabled f
Thanks Thomas for the valuable comments.
Changelog for the updated patchset:
v1->v2 - Update pvinfo.name.
v2->v3 - Address comments from Thomas G,
* Created separate function: vmware_sched_clock_setup() (patch 3/3)
* Updated commit descriptions for 1/3 and 3/3
Alexey Makhalov (
Commit aa297292d708 ("x86/tsc: Enumerate SKL cpu_khz and tsc_khz via
CPUID") separated the calibration mechanisms for cpu_khz and tsc_khz.
Since the vmware hypervisor provides a constant frequency TSC to the guest,
this change can lead to divergence between the tsc and the cpu frequency
after vmot
The default sched_clock() implementation is native_sched_clock(). It
contains code to handle non constant frequency TSCs, which creates
overhead for systems with constant frequency TSCs.
The vmware hypervisor guarantees a constant frequency TSC, so
native_sched_clock() is not required and slower t
Add basic paravirt support:
1. set pv_info.name to "VMware hypervisor" to have proper boot log message
Booting paravirtualized kernel on VMware hypervisor
instead of "... on bare hardware"
2. set pv_cpu_ops.io_delay() to empty function - paravirt_nop() to
avoid vm-exits on IO dela
On 2016-10-28 00:29, Peter Zijlstra wrote:
On Fri, Oct 28, 2016 at 12:10:39AM -0700, Vikram Mulukutla wrote:
We propose Window-Assisted Load Tracking (WALT) as an alternative or
additional
load tracking scheme in lieu of or along with PELT, one that in our
estimation
better tracks task demand
On 2016-10-28 00:49, Peter Zijlstra wrote:
On Fri, Oct 28, 2016 at 12:10:39AM -0700, Vikram Mulukutla wrote:
This RFC patch has been tested on live X86 machines with the following
sanity
and benchmark results (thanks to Juri Lelli, Dietmar Eggeman, Patrick
Bellasi
for initial code reviews):
(
On Fri, Oct 28, 2016 at 12:10:42AM -0700, Vikram Mulukutla wrote:
> @@ -2072,13 +2078,19 @@ try_to_wake_up(struct task_struct *p, unsigned int
> state, int wake_flags)
>*/
> smp_cond_load_acquire(&p->on_cpu, !VAL);
>
> + raw_spin_lock(&task_rq(p)->lock);
> + walt_update_tas
On 2016-10-28 00:43, Peter Zijlstra wrote:
On Fri, Oct 28, 2016 at 12:10:41AM -0700, Vikram Mulukutla wrote:
+u64 walt_ktime_clock(void)
+{
+ if (unlikely(walt_ktime_suspended))
+ return ktime_to_ns(ktime_last);
+ return ktime_get_ns();
+}
+static int walt_suspend(vo
On Thu, Oct 27, 2016 at 05:37:11PM -0200, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> Support DRM out-fences by creating a sync_file with a fence for each CRTC
> that sets the OUT_FENCE_PTR property.
>
> We use the out_fence pointer received in the OUT_FENCE_PTR prop to send
> the sync_fi
On Thu 27-10-16 10:26:18, Jens Axboe wrote:
> On 10/27/2016 03:26 AM, Jan Kara wrote:
> >On Wed 26-10-16 10:12:38, Jens Axboe wrote:
> >>On 10/26/2016 10:04 AM, Paolo Valente wrote:
> >>>
> Il giorno 26 ott 2016, alle ore 17:32, Jens Axboe ha
> scritto:
>
> On 10/26/2016 09:29 AM
On 2016-10-27 15:00:32 [-0400], Charles (Chas) Williams wrote:
> > I assume "init_rapl_pmus: maxpkg 4" is from init_rapl_pmus() returning
> > topology_max_packages(). So it says 4 but then returns 65535 for CPU 2
> > and 3. That -1 comes probably from topology_update_package_map(). Could
> > you pl
Hi,
On 10/28/2016 04:26 PM, Leo Yan wrote:
> On Fri, Oct 28, 2016 at 08:43:51AM +0200, Vincent Guittot wrote:
>
> [...]
>
>>> running with? Also do you have any details about the card in case its
>>> card specific?
>>
>> The sdcard is quite common: sandisk ultra 16GB
>> and my rootfs is on the s
On 2016-10-28 00:46, Peter Zijlstra wrote:
On Fri, Oct 28, 2016 at 12:10:41AM -0700, Vikram Mulukutla wrote:
+void walt_finish_migrate(struct task_struct *p, struct rq *dest_rq,
bool locked)
+{
+ u64 wallclock;
+ unsigned long flags;
+
+ if (!p->on_rq && p->state != TASK_WAKIN
On 2016-10-27 11:09:06 [-0600], Shuah Khan wrote:
> diff --git a/Makefile b/Makefile
> index 82a36ab..0a01ad1 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -651,6 +651,11 @@ ifneq ($(CONFIG_FRAME_WARN),0)
> KBUILD_CFLAGS += $(call cc-option,-Wframe-larger-than=${CONFIG_FRAME_WARN})
> endif
>
> +
On 25 October 2016 at 21:58, Zach Brown wrote:
> On some systems the sdhci capabilty registers are incorrect for one
> reason or another.
>
> The sdhci-caps-mask property specifies which bits in the registers
> are incorrect and should be turned off before using sdhci-caps to turn
> on bits.
>
> T
On Friday, October 28, 2016 1:56 PM Huang, Ying wrote:
>
> @@ -109,9 +118,16 @@ int __add_to_swap_cache(struct page *page, swp_entry_t
> entry)
>* So add_to_swap_cache() doesn't returns -EEXIST.
>*/
> VM_BUG_ON(error == -EEXIST);
> - set_p
If a DAI specifies "#sound-dai-cells = <0>" in device-tree then
hdmi_of_xlate_dai_name() will be called with zero args, which it isn't
implemented to cope with. The resulting use of an uninitialised variable
for the id will usually result in an error like:
asoc-simple-card sound: parse error -11
Drivers using pinconf_generic_params tables cannot be built with
CONFIG_OF disabled:
drivers/pinctrl/pinctrl-max77620.c:53:44: error: array type has incomplete
element type ‘struct pinconf_generic_params’
drivers/pinctrl/pinctrl-max77620.c:55:3: error: field name not in record or
union initializ
Hi Andy,
On Thu, Oct 27, 2016 at 07:56:10PM +0300, Andy Shevchenko wrote:
> On Thu, 2016-10-27 at 17:38 +0100, Ed Blake wrote:
> > Add a set_ldisc function to enable/disable IrDA SIR mode according to
> > the new line discipline.
>
> Thanks for the patch.
>
> Consider that not all implementation
On Wednesday 26 October 2016 09:38 PM, David Lechner wrote:
> On 10/25/2016 10:06 PM, David Lechner wrote:
>> Add a syscon node for the SoC CFGCHIPn registers. This is needed for
>> the new usb phy driver.
>>
>> Signed-off-by: David Lechner
>> ---
>> arch/arm/boot/dts/da850.dtsi | 4
>> 1 fi
I'm announcing the release of the 4.4.28 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.8.5 kernel.
All users of the 4.8 kernel series must upgrade.
The updated 4.8.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.8.y
and can be browsed at the normal kernel.org git web browser:
Introduce defines for shifting and mask under the config register for
better readability. Also, introduce helper variables for index
calculation.
Signed-off-by: Eva Rachel Retuya
---
This patch might cause a conflict with this patch:
staging: iio: cdc/ad7746: fix missing return value
https://marc
Linus,
Please pull the latest core-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-urgent-for-linus
# HEAD: 56fb2d6eb63acd48b50437b415b6f7d2fcffe75d objtool: Fix rare switch
jump table pattern detection
One more objtool fixlet for GCC6 code
From: Markus Elfring
Date: Fri, 28 Oct 2016 10:18:10 +0200
Some update suggestions were taken into account
from static source code analysis.
Markus Elfring (10):
bin2c: Complete error handling in main()
fixdep: Complete error handling in print_deps()
fixdep: Use the symbol "MAP_FAILED" in
Hi, Hillf,
Hillf Danton writes:
> On Friday, October 28, 2016 1:56 PM Huang, Ying wrote:
>>
>> @@ -109,9 +118,16 @@ int __add_to_swap_cache(struct page *page, swp_entry_t
>> entry)
>> * So add_to_swap_cache() doesn't returns -EEXIST.
>> */
>> VM_BUG_ON(
Am Donnerstag, 13. Oktober 2016, 12:42:13 CEST schrieb Shawn Lin:
> The deassert of phy_rst from exit callback is incorrect as when
> doing phy_exit, we expect the phy_rst is on asserted state which was
> done by power_off callback, but not deasserted state. Meanwhile when
> disabling clk_pciephy_r
On Thu, Oct 27, 2016 at 10:35 PM GMT, Tom Herbert wrote:
> On Mon, Oct 24, 2016 at 2:28 AM, Jakub Sitnicki wrote:
>> Same as for the transmit path, let's do our best to ensure that received
>> ICMP errors that may be subject to forwarding will be routed the same
>> path as flow that triggered the
From: Markus Elfring
Date: Thu, 27 Oct 2016 16:15:04 +0200
Return values were not checked from five calls of the function "printf".
This issue was detected also by using the Coccinelle software.
* Add a bit of exception handling there.
* Optimise this function implementation a bit.
- Repla
From: Markus Elfring
Date: Thu, 27 Oct 2016 18:18:54 +0200
Check the return value from a call of the function "mmap" by using
the preprocessor symbol "MAP_FAILED".
Signed-off-by: Markus Elfring
---
scripts/basic/fixdep.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scrip
Linus,
Please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
# HEAD: 62c61514191bfe5731b43619b9b1bf4b423beeb0 doc: Add missing parameter
for msi_setup
A DocBook fix.
Thanks,
Ingo
From: Markus Elfring
Date: Thu, 27 Oct 2016 18:08:30 +0200
Return values were not checked from calls of the functions "close"
and "munmap".
This issue was detected also by using the Coccinelle software.
Add a bit of exception handling there.
Signed-off-by: Markus Elfring
---
scripts/basic/f
From: Markus Elfring
Date: Thu, 27 Oct 2016 19:04:01 +0200
The function "perror" was called after a call of the function "fprintf"
in two if branches. So it could happen that an error message was displayed
for a failed print operation instead of the failure according to the call
of the function "
Hi, Matthias:
Even though OVL HW would not be enabled before component_add() in
current design, your patch would be safe for any situation.
Acked-by CK Hu
Regards,
CK
On Wed, 2016-10-26 at 16:09 +0200, Matthias Brugger wrote:
> The probe function requests the interrupt before initializing
> th
Linus,
Please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
# HEAD: f5d6d2da0d9098a4aa0ebcc187aa0fc167045d6b sched/fair: Remove unused
but set variable 'rq'
An unused variable warning fix.
Thanks,
From: Markus Elfring
Date: Thu, 27 Oct 2016 19:43:43 +0200
Return values were not checked from five calls of the function "printf".
This issue was detected also by using the Coccinelle software.
* Add a bit of exception handling there.
* Combine these calls into three.
Signed-off-by: Markus
From: Markus Elfring
Date: Thu, 27 Oct 2016 22:02:42 +0200
Return values were not checked from four calls of the function "close".
This issue was detected also by using the Coccinelle software.
Add a bit of exception handling there.
Signed-off-by: Markus Elfring
---
scripts/basic/fixdep.c |
Linus,
Please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
# HEAD: 6bad6bccf2d717f652d37e63cf261eaa23466009 timers: Prevent base clock
corruption when forwarding
Fix four timer locking races: two
From: Markus Elfring
Date: Thu, 27 Oct 2016 22:45:03 +0200
Return values were not checked from calls of the function "printf"
and "putchar".
This issue was detected also by using the Coccinelle software.
* Add a bit of exception handling there.
* Optimise this function implementation a bit by
From: Markus Elfring
Date: Thu, 27 Oct 2016 22:15:14 +0200
The function "perror" was called after a call of the function "fprintf"
in two if branches. So it could happen that an error message was displayed
for a failed print operation instead of the failure according to the call
of the function "
Commit-ID: 1c27f646b18fb56308dff82784ca61951bad0b48
Gitweb: http://git.kernel.org/tip/1c27f646b18fb56308dff82784ca61951bad0b48
Author: Borislav Petkov
AuthorDate: Thu, 27 Oct 2016 14:36:23 +0200
Committer: Ingo Molnar
CommitDate: Fri, 28 Oct 2016 10:29:59 +0200
x86/microcode/AMD: Fix m
From: Markus Elfring
Date: Fri, 28 Oct 2016 09:29:59 +0200
A return value was not checked from a call of the function "printf".
This issue was detected also by using the Coccinelle software.
Add a bit of exception handling there.
Signed-off-by: Markus Elfring
---
scripts/basic/fixdep.c | 7
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
# HEAD: 1c27f646b18fb56308dff82784ca61951bad0b48 x86/microcode/AMD: Fix more
fallout from CONFIG_RANDOMIZE_MEMORY=y
Misc fixes: three build fi
Now when we have properly working performance counters in nSIM
even with interrupt support (fix should be a part of upcoming
nSIM engineering build 2016.12-005) we may enable perf support
by default for all platforms that use nSIM for ARC cores simulation.
Note all defconfigs were regenerated with
From: Markus Elfring
Date: Fri, 28 Oct 2016 09:45:30 +0200
Some data were printed by two separate function calls.
Print the same data by a single call of the function "fputs" instead.
This issue was detected also by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
scripts/basi
This cleanup patch just adds pr_fmt style logging for cacheinfo.
Cc: Greg Kroah-Hartman
Signed-off-by: Sudeep Holla
---
drivers/base/cacheinfo.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/base/cacheinfo.c b/drivers/base/cacheinfo.c
index 70e13cf06ed0..f19d50bd8925 100644
---
Hi Greg,
Since the couple of fixes here are not too severe, I am considering as
updates only.
Now the x86 allow CONFIG_OF to be enabled and ACPI on arm64, we have
couple of minor bugs in those configurations. The first 2 patches fixes
them. The 3rd patch is cosmetic update to help identify the lo
Few architectures like x86, ia64 and s390 derive the cache topology and
all the properties using a specific architected mechanism while some
other architectures like powerpc all those information id derived from
the device tree.
On ARM, both the mechanism is used. While all the cache properties ca
With CONFIG_OF enabled on x86, we get the following error on boot:
"
Failed to find cpu0 device node
Unable to detect cache hierarchy from DT for CPU 0
"
and the cacheinfo fails to get populated in the corresponding sysfs
entries. This is because cache_setup_of_node looks for of_nod
ARM64 enables both CONFIG_OF and CONFIG_ACPI and the firmware can pass
both ACPI tables and the device tree. Based on the kernel parameter, one
of the two will be chosen. If acpi is enabled, then device tree is not
unflattened.
Currently ARM64 platforms report:
"
Failed to find cpu0 device
On Fri, Oct 28, 2016 at 12:57:05AM -0700, Vikram Mulukutla wrote:
> On 2016-10-28 00:49, Peter Zijlstra wrote:
> >On Fri, Oct 28, 2016 at 12:10:39AM -0700, Vikram Mulukutla wrote:
> >>This RFC patch has been tested on live X86 machines with the following
> >>sanity
> >>and benchmark results (thanks
On Fri 2016-10-28 09:07:01, Ingo Molnar wrote:
>
> * Pavel Machek wrote:
>
> > +static void rh_overflow(struct perf_event *event, struct perf_sample_data
> > *data, struct pt_regs *regs)
> > +{
> > + u64 *ts = this_cpu_ptr(&rh_timestamp); /* this is NMI context */
> > + u64 now = ktime_get_
On Fri, Oct 28, 2016 at 09:42:12AM +0200, Daniel Vetter wrote:
On Thu, Oct 27, 2016 at 05:37:10PM -0200, Gustavo Padovan wrote:
From: Gustavo Padovan
Create one timeline context for each CRTC to be able to handle out-fences
and signal them. It adds a few members to struct drm_crtc: fence_conte
On 10/27/2016 06:28 PM, Cong Wang wrote:
>>> Hmm, bo->bound should guarantee it, so never mind, your patch
>>> looks fine.
>>
>> Can I add your Acked-by?
>
> Of course.
>
> Acked-by: Cong Wang
Thanks,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux S
* Pavel Machek wrote:
> On Fri 2016-10-28 09:07:01, Ingo Molnar wrote:
> >
> > * Pavel Machek wrote:
> >
> > > +static void rh_overflow(struct perf_event *event, struct
> > > perf_sample_data *data, struct pt_regs *regs)
> > > +{
> > > + u64 *ts = this_cpu_ptr(&rh_timestamp); /* this is NMI
On Fri, Oct 28, 2016 at 10:50:39AM +0200, Pavel Machek wrote:
> On Fri 2016-10-28 09:07:01, Ingo Molnar wrote:
> >
> > * Pavel Machek wrote:
> >
> > > +static void rh_overflow(struct perf_event *event, struct
> > > perf_sample_data *data, struct pt_regs *regs)
> > > +{
> > > + u64 *ts = this_cp
On 10/27/2016 08:50 PM, Allan Tsakuhhin wrote:
> I am trying to build Linux system on Fujitsu PrimePower 450 running by
> SPARC64 V CPUs. Does anyone have supportive materials (manuals,
> overviews, specs) about Fujitsu PP450 and SPARC64 V CPUs. Every kind
> of source material may be useful!
>
>
1 - 100 of 675 matches
Mail list logo
