Hi Benjamin,
[auto build test ERROR on abelloni/rtc-next]
[also build test ERROR on v4.12-rc6 next-20170620]
[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/Benjamin-Gaignard/rtc-stop-using-rtc
Ram Pai writes:
> diff --git a/arch/powerpc/mm/hugetlbpage-hash64.c
> b/arch/powerpc/mm/hugetlbpage-hash64.c
> index a84bb44..239ca86 100644
> --- a/arch/powerpc/mm/hugetlbpage-hash64.c
> +++ b/arch/powerpc/mm/hugetlbpage-hash64.c
> @@ -22,6 +22,7 @@ int __hash_page_huge(unsigned long ea,
On 2017/6/20 21:08, Alexander Shishkin wrote:
Zhou Chengming writes:
The else branch are broken for taskctx:
This is not a good way to open a commit message.
two events can on the same taskctx, but on different cpu.
How?
fd1 = perf_open_event(attr, pid, 0, -1, flags);
fd2 = perf_open_eve
Ram Pai writes:
> Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6
> in the 64K backed hpte pages. This along with the earlier
> patch will entirely free up the four bits from 64K PTE.
>
> This patch does the following change to 64K PTE that is
> backed by 64K hpte.
>
> H_PAGE_F_SECOND w
On Tue, Jun 20, 2017 at 01:45:36PM +0200, Corentin Labbe wrote:
> On Tue, Jun 20, 2017 at 11:59:47AM +0200, Maxime Ripard wrote:
> > Hi,
> >
> > On Tue, Jun 20, 2017 at 10:58:19AM +0200, Corentin Labbe wrote:
> > > The Security System have a PRNG, this patch add support for it via
> > > crypto_rng
Hi Paul,
After merging the rcu tree, today's linux-next build (x86_64 allnoconfig)
produced this warning:
kernel/cpu.c: In function 'boot_cpu_state_init':
kernel/cpu.c:1778:6: warning: unused variable 'cpu' [-Wunused-variable]
int cpu;
^
Introduced by commit
faeb334286b7 ("rcu: Migrat
Add optional properties for power sequence.
Signed-off-by: Peter Chen
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/usb/usb-device.txt | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/usb/usb-device.txt
b/Documentatio
From: Joshua Clayton
Previously the onboard hub was made to work by treating its
reset gpio as a regulator enable.
Get rid of that kludge now that pwseq has added reset gpio support
Move pin muxing the hub reset pin into the usbh1 group
Signed-off-by: Joshua Clayton
Signed-off-by: Peter Chen
-
From: Joshua Clayton
Give usb nodes #address and #size attributes, so that a child node
representing a permanently connected device such as an onboard hub may
be addressed with a attribute
Signed-off-by: Joshua Clayton
Signed-off-by: Peter Chen
---
arch/arm/boot/dts/imx6qdl.dtsi | 6 ++
The current dts describes USB HUB's property at USB controller's
entry, it is improper. The USB HUB should be the child node
under USB controller, and power sequence properties are under
it. Besides, using gpio pinctrl setting for USB2415's reset pin.
Signed-off-by: Peter Chen
Signed-off-by: Josh
Some hard-wired USB devices need to do power sequence to let the
device work normally, the typical power sequence like: enable USB
PHY clock, toggle reset pin, etc. But current Linux USB driver
lacks of such code to do it, it may cause some hard-wired USB devices
works abnormal or can't be recogniz
Add binding doc for generic power sequence library.
Signed-off-by: Peter Chen
Acked-by: Philipp Zabel
Acked-by: Rob Herring
---
.../bindings/power/pwrseq/pwrseq-generic.txt | 53 ++
1 file changed, 53 insertions(+)
create mode 100644
Documentation/devicetree/binding
We have an well-known problem that the device needs to do some power
sequence before it can be recognized by related host, the typical
example like hard-wired mmc devices and usb devices.
This power sequence is hard to be described at device tree and handled by
related host driver, so we have crea
This is a follow-up for my last power sequence framework patch set [1].
According to Rob Herring and Ulf Hansson's comments[2]. The kinds of
power sequence instances will be added at postcore_initcall, the match
criteria is compatible string first, if the compatible string is not
matched between dt
Ram Pai writes:
> Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6
> in the 4K backed hpte pages. These bits continue to be used
> for 64K backed hpte pages in this patch, but will be freed
> up in the next patch.
>
> The patch does the following change to the 64K PTE format
>
> H_PAGE_B
Hi Will,
On Tue, Jun 20, 2017 at 11:30 PM, Will Deacon wrote:
> On Tue, Jun 20, 2017 at 07:47:39PM +0530, Geetha sowjanya wrote:
>> From: Geetha Sowjanya
>>
>> Cavium ThunderX2 SMMU doesn't support MSI and also doesn't have unique irq
>> lines for gerror, eventq and cmdq-sync.
>>
>> SHARED_IRQ o
__list_lru_walk_one() acquires nlru spin lock (nlru->lock) for
longer duration if there are more number of items in the lru list.
As per the current code, it can hold the spin lock for upto maximum
UINT_MAX entries at a time. So if there are more number of items in
the lru list, then "BUG: spinlock
On 2017年06月21日 14:31, Bhumika Goyal wrote:
Add const to drm_encoder_helper_funcs structures as they are only passed
as an argument to the function drm_encoder_helper_add and this argument
is of type const. So, add const to these structures.
Signed-off-by: Bhumika Goyal
---
Changes in v2 -
* Let
On Wed, Jun 21, 2017 at 8:33 AM, Hoegeun Kwon wrote:
> Remove the error handling of bridge_node because the bridge_node is
> optionally.
"is optional"
>
> For example, In case of Exynos SoC, a bridge device such as mDNIe and
> MIC could be placed between Display Controller and MIPI DSI device bu
On Wed, Jun 21, 2017 at 11:05:33AM +0530, Anshuman Khandual wrote:
> On 06/21/2017 04:53 AM, Ram Pai wrote:
> > On Tue, Jun 20, 2017 at 03:50:25PM +0530, Anshuman Khandual wrote:
> >> On 06/17/2017 09:22 AM, Ram Pai wrote:
> >>> Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6
> >>> in the
Remove the error handling of bridge_node because the bridge_node is
optionally.
For example, In case of Exynos SoC, a bridge device such as mDNIe and
MIC could be placed between Display Controller and MIPI DSI device but
the bridge device is optionally.
Signed-off-by: Hoegeun Kwon
---
Hi all,
Add const to drm_encoder_helper_funcs structures as they are only passed
as an argument to the function drm_encoder_helper_add and this argument
is of type const. So, add const to these structures.
Signed-off-by: Bhumika Goyal
---
Changes in v2 -
* No change
drivers/gpu/drm/sun4i/sun4i_rgb.c |
Add const to drm_encoder_helper_funcs structures as they are only passed
as an argument to the function drm_encoder_helper_add and this argument
is of type const. So, add const to these structures.
Signed-off-by: Bhumika Goyal
---
Changes in v2 -
* Let the line exceed over 80 characters while add
Add const to drm_encoder_helper_funcs structures.
Changes in v2 -
* Let the line exceed over 80 characters while adding const
in analogix_dp-rockchip.c file.
Bhumika Goyal (2):
drm/rockchip: add const to drm_encoder_helper_funcs structures
drm/sun4i: add const to drm_encoder_helper_funcs stru
Hi Kees,
Today's linux-next merge of the kspp tree got a conflict in:
include/linux/fs.h
between commits:
7356fd927059 ("fs: new infrastructure for writeback error handling and
reporting")
c7fe314be636 ("fs: add f_md_wb_err field to struct file for tracking metadata
errors")
from the f
On 2017-06-20 13:38, Linus Walleij wrote:
> On Tue, Jun 20, 2017 at 10:54 AM, Jan Kiszka wrote:
>> On 2017-06-20 10:19, Linus Walleij wrote:
>>> On Fri, Jun 9, 2017 at 8:33 PM, Jan Kiszka wrote:
>>>
This makes the gpio-exar driver usable, which was prevented by a number
of fatal bugs, a
On 06/21/2017 02:11 PM, Kalle Valo wrote:
David Miller writes:
From: Jia-Ju Bai
Date: Mon, 19 Jun 2017 10:48:53 +0800
The driver may sleep under a spin lock, and the function call path is:
netxen_nic_pci_mem_access_direct (acquire the lock by spin_lock)
ioremap --> may sleep
To fix it,
On Wed, Jun 21, 2017 at 09:24:36AM +0530, Anshuman Khandual wrote:
> On 06/21/2017 05:13 AM, Ram Pai wrote:
> > On Tue, Jun 20, 2017 at 12:54:45PM +0530, Anshuman Khandual wrote:
> >> On 06/17/2017 09:22 AM, Ram Pai wrote:
> >>> Handle Data and Instruction exceptions caused by memory
> >>> protecti
On Tue, Jun 20, 2017 at 11:11 PM, Paul Mackerras wrote:
> On Tue, Jun 20, 2017 at 10:21:31PM -0700, John Stultz wrote:
>> CONFIG_GENERIC_TIME_VSYSCALL_OLD was introduced five years ago
>> to allow a transition from the old vsyscall implementations to
>> the new method (which simplified internal ac
Hi Rob,
Michael has an issue that means this patch series is not OK in the
current form. I will work on a v7 to see if I can resolve the
issue.
-Frank
On 06/20/17 21:57, Michael Ellerman wrote:
> Hi Frank,
>
> frowand.l...@gmail.com writes:
>> From: Frank Rowand
>>
>> Remove "phandle", "linu
On Wed, 21 Jun 2017 16:09:34 +1000
Stephen Rothwell wrote:
> Hi Linus,
>
> After merging the gpio tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/gpio/gpio-dwapb.c: In function 'dwapb_irq_set_type':
> drivers/gpio/gpio-dwapb.c:291:2: error: stray '\357' i
ACPI 6.2 have added SRAT subtable to define proximity domain for ITS
devices. This patchset updates acpi header file from acpica repo and
adds numa node mapping for ITS devices.
v3:
- Use static array to stash parsed data from srat its table.
v2:
- Incorporated comments from Lorenzo Pieralisi
Add code to parse SRAT ITS Affinity sub table as defined in ACPI 6.2
Later in per device probe, ITS devices are mapped to
numa node using ITS id to proximity domain mapping.
Signed-off-by: Ganapatrao Kulkarni
---
drivers/irqchip/irq-gic-v3-its.c | 80 +++-
1 f
Add GIC ITS Affinity (ACPI 6.2) subtable to SRAT table.
ACPICA commit 5bc67f63918da249bfe279ee461d152bb3e6f55b
Link: https://github.com/acpica/acpica/commit/5bc67f6
Signed-off-by: Ganapatrao Kulkarni
---
include/acpi/actbl1.h | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
d
John Stultz writes:
> CONFIG_GENERIC_TIME_VSYSCALL_OLD was introduced five years ago
> to allow a transition from the old vsyscall implementations to
> the new method (which simplified internal accounting and made
> timekeeping more precise).
>
> However, PPC and IA64 have yet to make the transit
David Miller writes:
> From: Jia-Ju Bai
> Date: Mon, 19 Jun 2017 10:48:53 +0800
>
>> The driver may sleep under a spin lock, and the function call path is:
>> netxen_nic_pci_mem_access_direct (acquire the lock by spin_lock)
>> ioremap --> may sleep
>>
>> To fix it, the lock is released before
On Tue, Jun 20, 2017 at 10:21:31PM -0700, John Stultz wrote:
> CONFIG_GENERIC_TIME_VSYSCALL_OLD was introduced five years ago
> to allow a transition from the old vsyscall implementations to
> the new method (which simplified internal accounting and made
> timekeeping more precise).
>
> However, P
On Wed, 21 Jun 2017, Willy Tarreau wrote:
> On Tue, Jun 20, 2017 at 10:49:16PM -0700, Hugh Dickins wrote:
> > On Mon, 19 Jun 2017, Greg Kroah-Hartman wrote:
> >
> > > 3.18-stable review patch. If anyone has any objections, please let me
> > > know.
> > >
> > > --
> > >
> > > Fr
On Wed, Jun 21, 2017 at 08:48:20AM +0530, Anshuman Khandual wrote:
> On 06/21/2017 05:26 AM, Ram Pai wrote:
> > On Tue, Jun 20, 2017 at 12:24:53PM +0530, Anshuman Khandual wrote:
> >> On 06/17/2017 09:22 AM, Ram Pai wrote:
> >>> The value of the AMR register at the time of exception
> >>> is made a
mit
a9d21d8da766 ("gpio: dwapb: fix missing first irq for edgeboth irq type")
It looks like those '(' ')' chars are not what they seem ...
I have used the gpio tree from next-20170620 for today.
--
Cheers,
Stephen Rothwell
On Wed, Jun 21, 2017 at 6:18 AM, Mark yao wrote:
> On 2017年06月20日 21:07, Bhumika Goyal wrote:
>>
>> Add const to drm_encoder_helper_funcs structures as they are only passed
>> as an argument to the function drm_encoder_helper_add and this argument
>> is of type const. So, add const to these struct
"Jason A. Donenfeld" writes:
> This enables an important dmesg notification about when drivers have
> used the crng without it being seeded first. Prior, these errors would
> occur silently, and so there hasn't been a great way of diagnosing these
> types of bugs for obscure setups. By adding thi
Hi Jeremy,
On Mon, Jun 19, 2017 at 6:56 PM, Jeremy Kerr wrote:
> This change introduces an 'external mode' for GPIO-based FSI masters,
> +static ssize_t external_mode_show(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + struct fsi_master_gpio *master
On Tue, Jun 20, 2017 at 10:49:16PM -0700, Hugh Dickins wrote:
> On Mon, 19 Jun 2017, Greg Kroah-Hartman wrote:
>
> > 3.18-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Hugh Dickins
> >
> > commit 1be7107fbe18eed3e319a6c3e83c782
The ELF_ET_DYN_BASE position was originally intended to keep loaders
away from ET_EXEC binaries. (For example, running "/lib/ld-linux.so.2
/bin/cat" might cause the subsequent load of /bin/cat into where the
loader had been loaded.) With the advent of PIE (ET_DYN binaries with
an INTERP Program Hea
Hi all,
Today's linux-next merge of the scsi tree got a conflict in:
drivers/scsi/scsi_lib.c
between commit:
ca18d6f769d2 ("block: Make most scsi_req_init() calls implicit")
from the block tree and commit:
2dd6fb5957a7 ("scsi: Only add commands to the device command list if required
by
On Mon, 19 Jun 2017, Greg Kroah-Hartman wrote:
> 3.18-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Hugh Dickins
>
> commit 1be7107fbe18eed3e319a6c3e83c78254b693acb upstream.
Here's a few adjustments to the 3.18 patch: no doubt you'll
If 'wiphy_new()' fails, we leak 'ops'. Add a new label in the error
handling path to free it in such a case.
Cc: sta...@vger.kernel.org
Fixes: 5c22fb85102a7 ("brcmfmac: add wowl gtk rekeying offload support")
Signed-off-by: Christophe JAILLET
---
v2: Add CC tag
Change prefix
---
drivers/net/
On Mon, 19 Jun 2017, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Hugh Dickins
>
> commit 1be7107fbe18eed3e319a6c3e83c78254b693acb upstream.
The 4.11 and 4.9 patches are fine, but I noticed a couple of
On 20-06-17, 17:31, Saravana Kannan wrote:
> On 06/19/2017 11:17 PM, Viresh Kumar wrote:
> >On Thu, Jun 8, 2017 at 1:25 PM, Dietmar Eggemann
> > wrote:
> >
> >>diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
> >
> >> static int __init register_cpufreq_notifier(void)
> >>
On 06/21/2017 04:53 AM, Ram Pai wrote:
> On Tue, Jun 20, 2017 at 03:50:25PM +0530, Anshuman Khandual wrote:
>> On 06/17/2017 09:22 AM, Ram Pai wrote:
>>> Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6
>>> in the 4K backed hpte pages. These bits continue to be used
>>> for 64K backed hpte
In the lm3630a_chip_init we try to write to 0x50 register, which is
higher value then the max_register value, this resulted in regmap_write
return -EIO.
Fix this by bumping REG_MAX value to 0x50.
Signed-off-by: Bhushan Shah
Suggested-by: Bjorn Andersson
---
Changes since v1:
- Fix the lm36
In the lm3630a_chip_init we try to write to 0x50 register, which is
higher value then the max_register value, this resulted in regmap_write
return -EIO.
Fix this by bumping REG_MAX value to 0x50.
Signed-off-by: Bhushan Shah
Suggested-by: Bjorn Andersson
---
drivers/video/backlight/lm3630a_bl.c
Document the maintainership of the Qualcomm pinctrl drivers to improve the
hitrate.
Signed-off-by: Bjorn Andersson
---
MAINTAINERS | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 75cd0dc8e93f..c2e3a349ca7c 100644
--- a/MAINTAINERS
+++ b/
Originally, Linux reloaded the LDT whenever the prev mm or the next
mm had an LDT. It was changed in 0bbed3beb4f2 ("[PATCH]
Thread-Local Storage (TLS) support") (from the historical tree) like
this:
- /* load_LDT, if either the previous or next thread
-* has a non-de
CONFIG_GENERIC_TIME_VSYSCALL_OLD was introduced five years ago
to allow a transition from the old vsyscall implementations to
the new method (which simplified internal accounting and made
timekeeping more precise).
However, PPC and IA64 have yet to make the transition, despite
in some cases me sen
There are two kernel features that would benefit from tracking
how up-to-date each CPU's TLB is in the case where IPIs aren't keeping
it up to date in real time:
- Lazy mm switching currently works by switching to init_mm when
it would otherwise flush. This is wasteful: there isn't fundamenta
The parameter is only present on x86_64 systems to save a few bytes,
as PCID is always disabled on x86_32.
Signed-off-by: Andy Lutomirski
---
Documentation/admin-guide/kernel-parameters.txt | 2 ++
arch/x86/kernel/cpu/common.c| 18 ++
2 files changed, 20 inse
The only call site also calls idle_task_exit(), and idle_task_exit()
puts us into a clean state by explicitly switching to init_mm.
Reviewed-by: Rik van Riel
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/tlbflush.h | 8
arch/x86/kernel/smpboot.c | 1 -
2 files changed,
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
On Tue, Jun 20, 2017 at 10:21 PM, John Stultz wrote:
> Just a small set of changes, the biggest changes being the
> MONOTONIC_RAW handling cleanup, and a new kselftest from
> Miroslav. Also a a clear warning deprecating
> CONFIG_GENERIC_TIME_VSYSCALL_OLD, which affects ppc and ia64.
I forgot to n
We can use PCID if the CPU has PCID and PGE and we're not on Xen.
By itself, this has no effect. The next patch will start using
PCID.
Cc: Juergen Gross
Cc: Boris Ostrovsky
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/tlbflush.h | 8
arch/x86/kernel/cpu/common.c| 15
x86's lazy TLB mode used to be fairly weak -- it would switch to
init_mm the first time it tried to flush a lazy TLB. This meant an
unnecessary CR3 write and, if the flush was remote, an unnecessary
IPI.
Rewrite it entirely. When we enter lazy mode, we simply remove the
cpu from mm_cpumask. Thi
It was historically possible to have two concurrent TLB flushes
targetting the same CPU: one initiated locally and one initiated
remotely. This can now cause an OOPS in leave_mm() at
arch/x86/mm/tlb.c:47:
if (this_cpu_read(cpu_tlbstate.state) == TLBSTATE_OK)
BUG();
with t
From: Miroslav Lichvar
When the first timestamp in the list of clock readings was later than
the second timestamp and all other timestamps were in order, the
inconsistency was not reported because the index of the out-of-order
timestamp was equal to the default value.
Cc: Thomas Gleixner
Cc: In
Now that lazy TLB suppresses all flush IPIs (as opposed to all but
the first), there's no need to leave_mm() when going idle.
This means we can get rid of the rcuidle hack in
switch_mm_irqs_off() and we can unexport leave_mm().
This also removes acpi_unlazy_tlb() from the x86 and ia64 headers,
si
There are three performance benefits here:
1. TLB flushing is slow. (I.e. the flush itself takes a while.)
This avoids many of them when switching tasks by using PCID. In
a stupid little benchmark I did, it saves about 100ns on my laptop
per context switch. I'll try to improve that ben
Just a small set of changes, the biggest changes being the
MONOTONIC_RAW handling cleanup, and a new kselftest from
Miroslav. Also a a clear warning deprecating
CONFIG_GENERIC_TIME_VSYSCALL_OLD, which affects ppc and ia64.
Let me know if you have any thoughts or objections!
thanks
-john
Cc: Thom
This adds two new variables to mmu_context_t: ctx_id and tlb_gen.
ctx_id uniquely identifies the mm_struct and will never be reused.
For a given mm_struct (and hence ctx_id), tlb_gen is a monotonic
count of the number of times that a TLB flush has been requested.
The pair (ctx_id, tlb_gen) can be u
32-bit kernels on new hardware will see PCID in CPUID, but PCID can
only be used in 64-bit mode. Rather than making all PCID code
conditional, just disable the feature on 32-bit builds.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/disabled-features.h | 4 +++-
arch/x86/kernel/cpu/bug
From: Miroslav Lichvar
This test checks the response of the system clock to frequency
steps made with adjtimex(). The frequency error and stability of
the CLOCK_MONOTONIC clock relative to the CLOCK_MONOTONIC_RAW clock
is measured in two intervals following the step. The test fails if
values from
Now that we fixed the sub-ns handling for CLOCK_MONOTONIC_RAW,
remove the duplicitive tk->raw_time.tv_nsec, which can be
stored in tk->tkr_raw.xtime_nsec (similarly to how its handled
for monotonic time).
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Miroslav Lichvar
Cc: Richard Cochran
Cc: Prarit B
Hi all,
After merging the percpu tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
In file included from include/linux/kernel.h:13:0,
from include/linux/bitmap.h:9,
from mm/percpu.c:58:
mm/percpu.c: In function 'pcpu_alloc':
include/l
On Tue, Jun 20, 2017 at 6:40 PM, Dave Chinner wrote:
> Your mangling terminology here. We don't "break COW" - we *use*
> copy-on-write to break *extent sharing*. We can break extent sharing
> in page_mkwrite - that's exactly what we do for normal pagecache
> based mmap writes, and it's done in pag
Hi Benjamin,
[auto build test ERROR on abelloni/rtc-next]
[also build test ERROR on v4.12-rc6 next-20170620]
[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/Benjamin-Gaignard/rtc-stop-using-rtc
On Wed, Jun 14, 2017 at 09:29:20AM -0400, Theodore Ts'o wrote:
> We will use the rest of names that Linus had mentioned as being part
> of his secondary list to preseed the list of people to be considered.
> People who suggest topics that should be discussed on the Maintainer's
> summit will be add
On 2017-06-17 02:41, Stephen Boyd wrote:
On 06/14, kgu...@codeaurora.org wrote:
On 2017-06-01 02:09, Stephen Boyd wrote:
>On 05/30, Kiran Gunda wrote:
>>From: Abhijeet Dharmapurikar
>>
>>The driver currently invokes the apid handler (periph_handler())
>
>You mean periph_interrupt()?
>
Yes.
>>on
Hi all,
We are pleased to announce an update of Intel GVT-g for Xen.
Intel GVT-g is a full GPU virtualization solution with mediated pass-through,
starting from 4th generation Intel Core(TM) processors with Intel processor
graphics. A virtual GPU instance is maintained for each VM, with part of
Hi all,
We are pleased to announce an update of Intel GVT-g for KVM.
Intel GVT-g for KVM (a.k.a. KVMGT) is a full GPU virtualization solution with
mediated pass-through, starting from 5th generation Intel Core(TM) processors
with Intel processor graphics. A virtual GPU instance is maintained f
On 20-06-17, 14:08, Stephen Boyd wrote:
> On 06/20, Viresh Kumar wrote:
> > + */
> > +struct opp_table *dev_pm_opp_set_clkname(struct device *dev, const char
> > *name)
> > +{
> > + struct opp_table *opp_table;
> > + int ret;
> > +
> > + opp_table = dev_pm_opp_get_opp_table(dev);
> > + if
In order to support OPP switching, OPP layer needs to get pointer to the
clock for the device. Simple cases work fine without using the routines
added by this patch (i.e. by passing connection-id as NULL), but for a
device with multiple clocks available, the OPP core needs to know the
exact name o
Hi Frank,
frowand.l...@gmail.com writes:
> From: Frank Rowand
>
> Remove "phandle", "linux,phandle", and "ibm,phandle" properties from
> the internal device tree. The phandle will still be in the struct
> device_node phandle field and will still be displayed as if it is
> a property in /proc/dev
Tahsin, when you think we've closed on the reviews, could you send out
a complete set of all of the patches on a new mail thread, using git
send-email so I can make sure I'm grabbing the final version of all of
the patches in this patch series?
It's great that you are using separate versions for e
We can reuse "cap_parsing_failed" instead of keeping an additional
variable here.
Signed-off-by: Viresh Kumar
---
drivers/base/arch_topology.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
index d1c33a85059e..
Hi Greg,
You weren't included in the first [1] version of this series, as it was
targeting arch/arm*/ directories then.
Here are some cleanups for the arch_topology core.
Tested on ARM64 Hikey board by setting following in cpu nodes in DT:
capacity-dmips-mhz = <1000>;
V1->V2:
- based ov
Use the standard way of returning errors instead of returning 0(failure)
OR 1(success) and making it hard to read.
Signed-off-by: Viresh Kumar
---
arch/arm/kernel/topology.c | 2 +-
drivers/base/arch_topology.c | 8
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/arch/a
We only need to take care of one case here (CPUFREQ_NOTIFY) and there is
no need to add an extra level of indentation to the case specific code
by using a switch block. Use an if block instead.
Also add some blank lines to make the code look better.
Signed-off-by: Viresh Kumar
---
drivers/base/
cap_parsing_failed is only required in topology_parse_cpu_capacity() to
know if we have already tried to allocate raw_capacity and failed, or if
at least one of the cpu_node didn't had the required
"capacity-dmips-mhz" property.
All other users can use raw_capacity instead of cap_parsing_failed.
There is no need of line break at few places, avoid them.
Signed-off-by: Viresh Kumar
---
drivers/base/arch_topology.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
index 8239a6232808..2f1d9921ee54 100644
Hi Benjamin,
[auto build test ERROR on abelloni/rtc-next]
[also build test ERROR on v4.12-rc6 next-20170620]
[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/Benjamin-Gaignard/rtc-stop-using-rtc
Hi Benjamin,
[auto build test ERROR on abelloni/rtc-next]
[also build test ERROR on v4.12-rc6 next-20170620]
[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/Benjamin-Gaignard/rtc-stop-using-rtc
linux/sound/soc/fsl/mpc5200_dma.c:305:18: warning: unused variable \
psc_dma’ [-Wunused-variable]
Signed-off-by: Kuninori Morimoto
---
sound/soc/fsl/mpc5200_dma.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/sound/soc/fsl/mpc5200_dma.c b/sound/soc/fsl/mpc5200_dma.c
index 93885d9..
On Tue, Jun 20, 2017 at 02:45:56PM -0700, Darren Hart wrote:
> On Tue, Jun 20, 2017 at 10:46:12PM +0200, Pali Rohár wrote:
> > On Tuesday 20 June 2017 19:22:46 Andy Shevchenko wrote:
> > > On Tue, Jun 20, 2017 at 7:48 PM, Pali Rohár
> > > wrote:
> > > > On Tuesday 20 June 2017 17:06:23 Lee, Chun-Y
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
Documentation/DocBook/kernel-hacking.tmpl
between commit:
c4fcd7cabb83 ("docs-rst: convert kernel-hacking to ReST")
from the jc_docs tree and commit:
ac6424b981bc ("sched/wait: Rename wait_queue_t => wait_queue_entry_t"
Add a new IORESOURCE_ALLOCATED flag that is automatically used
when alloc_resource() is used internally in kernel/resource.c
and free_resource() now takes this flag into account.
The core of __request_region() was factored out into a new function
called __request_declared_region() that needs struc
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/next
head: faeb334286b762ba6b829ad62e3d39a97674bb56
commit: faeb334286b762ba6b829ad62e3d39a97674bb56 [116/116] rcu: Migrate
callbacks earlier in the CPU-offline timeline
config: x86_64-randconfig-b0-06210849 (atta
Use the new request_declared_muxed_region() macro to synchronize
accesses to the SB800 I/O port pair (0xcd6 / 0xcd7) with the
PCI quirk for isochronous USB transfers and with the i2c-piix4
driver.
At the same time, remove the long lifetime request_region() call
to reserve these I/O ports, similarl
This patch series fixes a regression introduced by:
commit 2fee61d22e606fc99ade9079fda15fdee83ec33e
Author: Christian Fetzer
Date: Thu Nov 19 20:13:48 2015 +0100
i2c: piix4: Add support for multiplexed main adapter in SB800
The regression caused sp5100_tco fail to load:
piix4_smbus :
This patch uses the previously introduced macro called
request_declared_muxed_region() to synchronize access to
the I/O port pair 0xcd6 / 0xcd7 on SB800.
These I/O ports are also used by i2c-piix4 and sp5100_tco,
the next two patches port these drivers to use the new macro.
Signed-off-by: Zoltán
Use the new request_declared_muxed_region() macro to
synchronize access to the I/O port pair 0xcd6 / 0xcd7.
At the same time, remove the long lifetime request_region()
call to reserve these I/O ports, so the sp5100_tco watchdog
driver can also load.
This fixes an old regression in Linux 4.4-rc4,
1 - 100 of 1130 matches
Mail list logo
