> On 01/11/17 15:12, Winkler, Tomas wrote:
>
> >>> On 01/11/17 10:24, Winkler, Tomas wrote:
> >
> > On Wed, Jan 11, 2017 at 01:27:21AM +0200, Tomas Winkler wrote:
> >> On older platforms the command should be just ignored by the
> >> firmware but some older platforms misbehave so
SPARC M7 processor introduces a new feature - Application Data
Integrity (ADI). ADI allows MMU to catch rogue accesses to memory.
When a rogue access occurs, MMU blocks the access and raises an
exception. In response to the exception, kernel sends the offending
task a SIGSEGV with si_code that ind
SPARC M7 processor adds new control register fields, ASIs and a new
trap to support the ADI (Application Data Integrity) feature. This
patch adds definitions for these register fields, ASIs and a handler
for the new precise memory corruption detected trap.
Signed-off-by: Khalid Aziz
Cc: Khalid Az
On Wed 11-01-17 19:55:20, Tetsuo Handa wrote:
> Currently, warn_alloc() prints warning messages only if __GFP_NOWARN
> is not specified. When warn_alloc() was proposed, I asserted that
> warn_alloc() should print stall warning messages even if __GFP_NOWARN
> is specified, but that assertion was not
On Wed, Jan 11, 2017 at 10:06 AM, Vitaly Wool wrote:
> This patch converts pages_nr per-pool counter to atomic64_t.
>
> Signed-off-by: Vitaly Wool
Acked-by: Dan Streetman
> ---
> mm/z3fold.c | 20 +---
> 1 file changed, 9 insertions(+), 11 deletions(-)
>
> diff --git a/mm/z3fo
Den 11.01.2017 15:43, skrev Andy Shevchenko:
On Tue, 2017-01-03 at 20:29 +0200, Andy Shevchenko wrote:
This series enables 64x48 OLED display and fixes the driver to work
with DMA
enabled SPI properly.
Has been tested on Intel Edison board with Adafruit 2'8" and SSD1306
64x48
(Sparkfun for Int
Hi,
On Saturday, October 29, 2016 09:36:58 PM Julia Lawall wrote:
> Use DEVICE_ATTR_RW for read-write attributes. This simplifies the
> source code, improves readbility, and reduces the chance of
> inconsistencies.
>
> The semantic patch that makes this change is as follows:
> (http://coccinell
On Mon, Jan 09, 2017 at 03:39:03PM +0100, Michal Hocko wrote:
> From: Michal Hocko
>
> try_release_extent_state reduces the gfp mask to GFP_NOFS if it is
> compatible. This is true for GFP_KERNEL as well. There is no real
> reason to do that though. There is no new lock taken down the
> the only
On Wed, Jan 11, 2017 at 02:59:20PM +, Mark Rutland wrote:
> Hi Peter,
>
> Sorry for the delay; this fell into my backlog over the holiday.
>
> On Fri, Dec 09, 2016 at 02:59:00PM +0100, Peter Zijlstra wrote:
> > So while I went back and forth trying to make that less ugly, I figured
> > there
On 01/11/2017 08:19 AM, Linus Walleij wrote:
> On Tue, Jan 10, 2017 at 3:07 PM, Shuah Khan wrote:
>> On 01/10/2017 02:29 AM, Linus Walleij wrote:
>>> On Thu, Jan 5, 2017 at 10:32 PM, Shuah Khan wrote:
>>>
Add .gitignore for generated files.
Signed-off-by: Shuah Khan
---
This patch updates the AMD uncore driver to support AMD Family17h
processors. In Family17h, there are two extra last level cache counters.
The counters are, therefore, allocated dynamically based on the family.
The cpu hotplug up callback function is refactored to better manage
failure conditions.
This patch updates the sysfs attributes for AMD Family17h processors. In
Family17h, the event bit position is changed for both the NorthBridge
and Last level cache counters.
The sysfs attributes are assigned based on the family and the type of
the counter.
Signed-off-by: Janakarajan Natarajan
--
This patch renames L2 counters to LLC counters. In AMD Family17h
processors, L3 cache counter is supported.
Since older families have at most L2 counters, last level cache (LLC)
indicates L2/L3 based on the family.
Signed-off-by: Janakarajan Natarajan
---
arch/x86/events/amd/uncore.c | 98 +
This patchset updates the AMD uncore driver to support AMD Family17h processors.
First, the current L2 counters are renamed to Last level cache (LLC) counter to
reflect either L2 or L3 counters depending on the family. Then, it also
dynamically allocates the counters since they vary between Famil
From: "Ivan T. Ivanov"
Add initial set of CoreSight components found on Qualcomm msm8916 and
apq8016 based platforms, including the DragonBoard 410c board.
Signed-off-by: Ivan T. Ivanov
Acked-by: Mathieu Poirier
Signed-off-by: Georgi Djakov
---
Changes since v4: (https://lkml.org/lkml/2016/1
On 01/11/2017, 04:56 PM, Bronek Kozicki wrote:
> On 11/01/2017 15:50, Jiri Slaby wrote:
>> On 01/08/2017, 03:28 PM, Bronek Kozicki wrote:
>>> Hello,
>>>
>>> any particular reason why this fix
>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=79dc7e3f1cd323be4c81aa1a94fa
On 11/01/2017 15:50, Jiri Slaby wrote:
On 01/08/2017, 03:28 PM, Bronek Kozicki wrote:
Hello,
any particular reason why this fix
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=79dc7e3f1cd323be4c81aa1a94faa1b3ed987fb2
was missed from stable 4.8 line? Apparently the bug
On Wednesday, January 11, 2017 2:47:20 PM CET David Howells wrote:
> Arnd Bergmann wrote:
>
> > > Is it worth abstracting out in-kernel UUID generation?
> >
> > Do you mean moving it out of AFS into lib/*.c? I think the 'afs_uuid'
> > structure is quite different from other UUID definitions, so
Grygorii,
On 10/01/17 22:00, Grygorii Strashko wrote:
> Hi
>
> On 01/10/2017 06:18 AM, Roger Quadros wrote:
>> Hi Linus,
>>
>> I see the following lockdep warning on v4.10-rc3 on TI's dra7-evm.
>>
>> reverting (d245b3f9bd3 "gpio: simplify adding threaded interrupts") seems to
>> fix it.
>>
>>
>>
From: Keerthy
Date: Wed, 11 Jan 2017 09:03:29 +0530
> Commit: bc1f44709cf2 - net: make ndo_get_stats64 a void function
> and
> Commit: 6a8162e99ef3 - net: netcp: store network statistics in 64 bits.
>
> The commit 6a8162e99ef3 adds ndo_get_stats64 function as per old
> signature which causes com
On 11/01/17 17:38, Linus Walleij wrote:
> On Tue, Jan 10, 2017 at 1:18 PM, Roger Quadros wrote:
>
>> Hi Linus,
>>
>> I see the following lockdep warning on v4.10-rc3 on TI's dra7-evm.
>>
>> reverting (d245b3f9bd3 "gpio: simplify adding threaded interrupts") seems to
>> fix it.
>
> I sent out a
On Wed 11-01-17 08:52:50, Minchan Kim wrote:
[...]
> > @@ -2055,8 +2055,8 @@ static bool inactive_list_is_low(struct
> > if (!file && !total_swap_pages)
> > return false;
> >
> > - inactive = lruvec_lru_size(lruvec, file * LRU_FILE);
> > - active = lruvec_lru_size(lruvec, file
On Wed, Jan 11, 2017 at 1:40 PM, Keerthy wrote:
> On Wednesday 11 January 2017 04:34 PM, Linus Walleij wrote:
>> On Wed, Jan 4, 2017 at 9:26 AM, Keerthy wrote:
>>
>>> gpio2regs is written making an assumption that driver supports only
>>> one instance of gpio controller. Removing this and adding
From: Arnd Bergmann
Date: Wed, 11 Jan 2017 15:36:09 +0100
> There are lots of #ifdefs in this file, and a recent patch got one
> of them wrong, leading to a harmless warning in some randconfig
> builds:
>
> ethernet/broadcom/bnxt/bnxt.c:4956:21: error: 'bnxt_get_max_func_vnics'
> defined but no
To follow iio guidelines Where possible we stick to the raw SI unit, so
specify meters for proximity.
Signed-off-by: Enric Balletbo i Serra
---
Documentation/ABI/testing/sysfs-bus-iio | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/ABI/testing/sysfs-bus-iio
b
From: Gwendal Grignou
Handle Light and Proximity sensors presented by the ChromeOS EC Sensor hub.
Creates an IIO device for each functions.
Signed-off-by: Gwendal Grignou
Signed-off-by: Guenter Roeck
Signed-off-by: Enric Balletbo i Serra
---
drivers/iio/common/cros_ec_sensors/Kconfig
On 17-01-11 17:05:04, Ville Syrjälä wrote:
On Thu, Jan 05, 2017 at 02:45:37PM +0100, Christian König wrote:
Am 05.01.2017 um 12:37 schrieb Ville Syrjälä:
> On Wed, Jan 04, 2017 at 07:38:55PM +0100, Rainer Hochecker wrote:
>> From: Rainer Hochecker
>>
>> This adds fourcc codes for 16bit planes r
On 01/08/2017, 03:28 PM, Bronek Kozicki wrote:
> Hello,
>
> any particular reason why this fix
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=79dc7e3f1cd323be4c81aa1a94faa1b3ed987fb2
> was missed from stable 4.8 line? Apparently the bug being fixed has its
> own https
From: "Ivan T. Ivanov"
Add initial set of CoreSight components found on Qualcomm apq8064 based
platforms, including the IFC6410 board.
Signed-off-by: Ivan T. Ivanov
Acked-by: Mathieu Poirier
Signed-off-by: Georgi Djakov
---
Changes since v2 (https://lkml.org/lkml/2016/11/21/522)
* Rebase to
On Wed, Jan 11, 2017 at 03:02:22PM +0100, Luis R. Rodriguez wrote:
> On Wed, Jan 11, 2017 at 09:32:26AM +0100, Greg KH wrote:
> > On Fri, Dec 16, 2016 at 03:10:37AM -0800, Luis R. Rodriguez wrote:
> > > Even though most distributions today disable the fallback mechanism
> > > by default we've deter
On Wed, Jan 11, 2017 at 12:34 AM, Guenter Roeck wrote:
> Use device managed functions to simplify error handling, reduce
> source code size, improve readability, and reduce the likelyhood of bugs.
>
> The conversion was done automatically with coccinelle using the
> following semantic patches. Th
Commit-ID: ad5013d5699d30ded0cdbbc68b93b2aa28222c6e
Gitweb: http://git.kernel.org/tip/ad5013d5699d30ded0cdbbc68b93b2aa28222c6e
Author: Colin King
AuthorDate: Wed, 11 Jan 2017 11:43:10 +
Committer: Thomas Gleixner
CommitDate: Wed, 11 Jan 2017 16:43:30 +0100
perf/x86/intel: Use ULL c
On Wed, Jan 11, 2017 at 07:24:45AM -0800, Dave Hansen wrote:
> On 01/10/2017 11:43 PM, Daniel Vetter wrote:
> > On Tue, Jan 10, 2017 at 08:52:47AM -0800, Dave Hansen wrote:
> >> On 01/10/2017 02:31 AM, Daniel Vetter wrote:
> >>> commit e73ab00e9a0f1731f34d0620a9c55f5c30c4ad4e
> >>> Author: Daniel V
On Tue, Jan 10, 2017 at 10:45 PM, William Breathitt Gray
wrote:
> On Tue, Jan 10, 2017 at 09:13:02PM +, Jonathan Cameron wrote:
>>On 10/01/17 18:51, William Breathitt Gray wrote:
>>> PC/104 drivers should be hidden on machines which do not support PC/104
>>> devices. This patch adds the PC104
PCI: Enumerate switches below PCI-to-PCIe bridges
A PCI-to-PCIe bridge (a "reverse bridge") has a PCI or PCI-X primary
interface and a PCI Express secondary interface. The PCIe interface is a
Downstream Port that originates a Link. See the "PCI Express to PCI/PCI-X
Bridge Specification", rev 1.0
On Wed, Jan 11, 2017 at 02:58:44PM +0100, M'boumba Cedric Madianga wrote:
> Hi Uwe,
>
> 2017-01-11 9:22 GMT+01:00 Uwe Kleine-König :
> > Hello Cedric,
> >
> > On Thu, Jan 05, 2017 at 10:07:23AM +0100, M'boumba Cedric Madianga wrote:
> >> +/*
> >> + * In standard mode:
> >> + * SCL period = SCL hig
On Wed, Jan 11, 2017 at 4:24 PM, Dave Hansen wrote:
> On 01/10/2017 11:43 PM, Daniel Vetter wrote:
>> On Tue, Jan 10, 2017 at 08:52:47AM -0800, Dave Hansen wrote:
>>> On 01/10/2017 02:31 AM, Daniel Vetter wrote:
commit e73ab00e9a0f1731f34d0620a9c55f5c30c4ad4e
Author: Daniel Vetter
On Tuesday, January 10, 2017 4:39:43 PM CET Andrew Duggan wrote:
> On 01/10/2017 04:16 AM, Arnd Bergmann wrote:
> > If CONFIG_INPUT=m, we get a build error for the rmi4-f03 driver,
> > added in linux-4.10:
> >
> > drivers/input/built-in.o: In function `rmi_f03_attention':
> > rmi_f03.c:(.text+0xcfe
On Wed, 2017-01-11 at 13:34 +0200, Jarkko Sakkinen wrote:
> On Tue, Jan 10, 2017 at 01:05:58PM -0700, Jason Gunthorpe wrote:
> > On Tue, Jan 10, 2017 at 01:16:35AM +0200, Jarkko Sakkinen wrote:
> > > On Wed, Jan 04, 2017 at 10:12:41AM -0600, Dr. Greg Wettstein
> > > wrote:
> > > > The kernel needs
Hello Cedric,
On Wed, Jan 11, 2017 at 03:20:41PM +0100, M'boumba Cedric Madianga wrote:
> >
> >> + */
> >> + reg = i2c_dev->base + STM32F4_I2C_CR1;
> >> + stm32f4_i2c_clr_bits(reg, STM32F4_I2C_CR1_ACK);
> >> + stm32f4_i2c_set_bits(reg, STM32F4_I2C_C
On Tue, Jan 10, 2017 at 1:18 PM, Roger Quadros wrote:
> Hi Linus,
>
> I see the following lockdep warning on v4.10-rc3 on TI's dra7-evm.
>
> reverting (d245b3f9bd3 "gpio: simplify adding threaded interrupts") seems to
> fix it.
I sent out a patch today:
"gpio: provide lockdep keys for nested/un
From: Colin Ian King
The range min_uV > 135 && min_uV <= 15 is never reachable
because of a typo in the previous range check and hence vsel = 59
is never reached. Fix the previous range check to enable the
vsel = 59 setting.
Fixes CoverityScan CID#728454 ("Logially dead code")
Signed-o
On Tue, Jan 10, 2017 at 8:29 PM, Steve Longerbeam wrote:
> Add optional reset-gpios pin control. If present, de-assert the
> specified reset gpio pin to bring the chip out of reset.
>
> Signed-off-by: Steve Longerbeam
> Cc: Linus Walleij
> Cc: Alexandre Courbot
> Cc: linux-g...@vger.kernel.org
The MIPS remote processor driver allows non-Linux firmware to take
control of and execute on one of the systems VPEs. The CPU must be
offlined from Linux first. A sysfs interface is created which allows
firmware to be loaded and changed at runtime. A full description is
available at [1]. An exampl
On Tue, Jan 10, 2017 at 8:19 PM, Tony Lindgren wrote:
> Below is an experimental fix to intorduce pinctrl_start() that I've
> tested with pinctrl-single. Then we should probably make all pin controller
> drivers call pinctrl_start() to properly fix the issue of struct pinctrl_dev
> handle not bei
The MIPS remote processor driver allows non-Linux firmware to take
control of and execute on one of the systems VPEs. If that VPE is
brought back under Linux, it is necessary to ensure that all GIC
interrupts are routed and masked as Linux expects them, as the firmware
can have done anything it lik
The MIPS remote processor driver (CONFIG_MIPS_REMOTEPROC) provides a
more standard mechanism for using one or more VPs as coprocessors
running separate firmware.
Here we deprecate this mechanism before it is removed.
Signed-off-by: Matt Redfearn
---
Changes in v5: None
Changes in v4: None
Chang
From: Lisa Parratt
VP(E) stealing provides a mechanism for removing an offline Virtual
Processor from the Linux kernel such that it is available to run bare
metal code.
Once the CPU has been offlined from Linux, the CPU can be given a task
to run via mips_cps_steal_cpu_and_execute(). The CPU is r
This driver allows a MIPS processor offlined from Linux to be used as a
remote processor. Firmware may be loaded via the sysfs interface and
changed at runtime, allowing the processor to handle real-time tasks or
perform coprocessing while remaining processors are available to Linux.
Coprocessor f
On Wed, Jan 11, 2017 at 05:07:29PM +0800, zhangyi (F) wrote:
>
> (1) The file we want to unlink have many hard links, but only one dcache
> entry in memory.
> (2) open this file, but it's inode->i_nlink read from disk was 1 (too low).
> (3) some one call rename and drop it's i_nlink to zero.
> (4
Matt Fleming wrote:
> > + movb$0, BP_secure_boot(%rsi)
> > #ifdef CONFIG_EFI_STUB
> > /*
> > * The entry point for the PE/COFF executable is efi_pe_entry, so
>
> Is clearing ::secure_boot really necessary? Any code path that goes
> via efi_main() will set it correctly and all oth
On Wed, Jan 11, 2017 at 07:41:07AM -0700, Shuah Khan wrote:
> On 01/11/2017 01:48 AM, Stafford Horne wrote:
> > On Wed, Jan 11, 2017 at 12:07:55AM -0800, Darren Hart wrote:
> >> On Wed, Jan 11, 2017 at 01:37:19PM +0900, Stafford Horne wrote:
> >>> On Tue, Jan 10, 2017 at 02:17:18PM -0800, Darren Ha
Matt Fleming wrote:
> Before we add more efi.flags bits I'd like this series to include the
> patch that makes use of EFI_SECURE_BOOT. Alternatively, you move this
> last patch to a new series.
Are you willing to take the kernel lock-down patches also?
David
On Tue, Jan 10, 2017 at 8:25 PM, Stefano Stabellini
wrote:
> On Tue, 10 Jan 2017, Dan Streetman wrote:
>> On Tue, Jan 10, 2017 at 2:03 PM, Stefano Stabellini
>> wrote:
>> > On Tue, 10 Jan 2017, Dan Streetman wrote:
>> >> On Tue, Jan 10, 2017 at 10:57 AM, Dan Streetman wrote:
>> >> > On Mon, Jan
>>> +
>>> +
>>> +static bool test_reply(struct xb_req_data *req)
>>> +{
>>> + if (req->state == xb_req_state_got_reply || !xenbus_ok())
>>> + return true;
>>> +
>>> + /* Make sure to reread req->state each time. */
>>> + cpu_relax();
>> I don't think I understand why this is needed
On Tue, Jan 3, 2017 at 4:16 PM, Icenowy Zheng wrote:
> V3s SoC features only a pin controller (for the lack of CPUs part).
>
> Add a driver for this controller.
>
> Signed-off-by: Icenowy Zheng
Patch applied with Maxime's ACK.
Yours,
Linus Walleij
On 11/01/2017 15:25, Guenter Roeck wrote:
> On 01/11/2017 04:31 AM, Marc Gonzalez wrote:
>> On 11/01/2017 11:52, Guenter Roeck wrote:
>>
>>> On 01/11/2017 01:07 AM, Marc Gonzalez wrote:
>>>
> @@ -134,12 +134,15 @@ static int tangox_wdt_probe(struct platform_device
> *pdev)
> err = cl
On Wed, Jan 11, 2017 at 04:18:28PM +0100, Petr Mladek wrote:
> On Tue 2017-01-10 14:46:46, Josh Poimboeuf wrote:
> > On Tue, Jan 10, 2017 at 02:00:58PM +0100, Petr Mladek wrote:
> > > On Thu 2016-12-22 12:31:37, Josh Poimboeuf wrote:
> > > > On Thu, Dec 22, 2016 at 03:34:52PM +0100, Petr Mladek wro
On 01/10/2017 11:43 PM, Daniel Vetter wrote:
> On Tue, Jan 10, 2017 at 08:52:47AM -0800, Dave Hansen wrote:
>> On 01/10/2017 02:31 AM, Daniel Vetter wrote:
>>> commit e73ab00e9a0f1731f34d0620a9c55f5c30c4ad4e
>>> Author: Daniel Vetter
>>> Date: Sun Dec 18 14:35:45 2016 +0100
>>>
>>> drm: prev
On Tue, Jan 10, 2017 at 7:50 PM, William Breathitt Gray
wrote:
> PC/104 form factor devices serve a specific niche of embedded system
> users. Since PC/104 devices and hardware are typically used by just a
> subset of Linux users, it would be appropriate to filter PC/104 related
> Kconfig options
Most of z3fold operations are in-page, such as modifying z3fold page
header or moving z3fold objects within a page. Taking per-pool spinlock
to protect per-page objects is therefore suboptimal, and the idea of
having a per-page spinlock (or rwlock) has been around for some time.
This patch implem
Rearrange header file includes to alphabetic order. As acpi_iort.h
includes acpi.h so remove the duplidate acpi.h inclusion as well.
Signed-off-by: Hanjun Guo
Cc: Marc Zyngier
Cc: Tomasz Nowicki
---
drivers/irqchip/irq-gic-v3-its.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff
The use of any kind of wait queue is an overkill for pcpu-rwsems.
While one option would be to use the less heavy simple (swait)
flavor, this is still too much for what pcpu-rwsems needs. For one,
we do not care about any sort of queuing in that the only (rare) time
writers (and readers, for that m
rcuwait provides support for (single) rcu-safe task wait/wake functionality,
with the caveat that it must not be called after exit_notify(), such that
we avoid racing with rcu delayed_put_task_struct callbacks, task_struct
being rcu unaware in this context -- for which we similarly have
task_rcu_de
Changes from v1:
- Renamed trywake to wake_up.
- Added Oleg's review tags.
Hi,
Here's an updated version of the pcpu rwsem writer wait/wake changes
with the abstractions wanted by Oleg. Patch 1 adds rcuwait (for a lack
of better name), and patch 2 trivially makes use of it.
Has survived tortu
1) Fix rtlwifi crash, from Larry Finger.
2) Memory disclosure in appletalk ipddp routing code, from
Vlad Tsyrklevich.
3) r8152 can erroneously split an RX packet into multiple URBs if the
Rx FIFO is not empty when we suspend. Fix this by waiting for the
FIFO to empty before suspending.
Hi All,
Please ignore this, its a dup of the patch with the same name.
I had an slight issue with reordering patches and this got send out.
On Thu, Jan 12, 2017 at 12:11:15AM +0900, Stafford Horne wrote:
> The intel_pstate kselftest expects that the output of
> `cpupower frequency-info -l | tail
On Tue, Jan 10, 2017 at 3:07 PM, Shuah Khan wrote:
> On 01/10/2017 02:29 AM, Linus Walleij wrote:
>> On Thu, Jan 5, 2017 at 10:32 PM, Shuah Khan wrote:
>>
>>> Add .gitignore for generated files.
>>>
>>> Signed-off-by: Shuah Khan
>>> ---
>>> tools/gpio/.gitignore | 4
>>> 1 file changed, 4
On Tue 2017-01-10 14:46:46, Josh Poimboeuf wrote:
> On Tue, Jan 10, 2017 at 02:00:58PM +0100, Petr Mladek wrote:
> > On Thu 2016-12-22 12:31:37, Josh Poimboeuf wrote:
> > > On Thu, Dec 22, 2016 at 03:34:52PM +0100, Petr Mladek wrote:
> > > > On Wed 2016-12-21 15:25:05, Josh Poimboeuf wrote:
> > > >
This test was missing from the TARGETS list. The test requires patches
to cpupower to pass correctly.
Cc: Prarit Bhargava
Signed-off-by: Stafford Horne
---
tools/testing/selftests/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/Makefile b/tools/testing/self
The build was showing the warning:
aperf.c:60:27: warning: iteration 2147483647 invokes undefined behavior
[-Waggressive-loop-optimizations]
for (i=0; i<0x8fff; i++) {
This change sets i, cpu and fd to unsigned int as they should not need
to be signed.
Cc: Prarit Bhargava
Signed-off-by:
The intel_pstate kselftest expects that the output of
`cpupower frequency-info -l | tail -1 | awk ' { print $1 } '`
to get frequency limits. This does not work after the following two
changes.
- 562e5f1a3: rework the "cpupower frequency-info" command
(Jacob Tanenbaum) removed parsable limit o
Recent changes from Bamvor (88baa78d1f318) have standardized the
variable names like TEST_GEN_FILES and removed the need for make targets
all and clean.
These changes bring the intel_pstate test inline with those changes.
Cc: Prarit Bhargava
Signed-off-by: Stafford Horne
---
tools/testing/self
With the preparation of platform msi support and interrupt producer
in DSDT, we can add mbigen ACPI support now.
We are using _PRS methd to indicate number of irq pins instead
of num_pins in DT to avoid _DSD usage in this case.
For mbi-gen,
Device(MBI0) {
Name(_HID, "HISI0152")
On Mon, Jan 9, 2017 at 4:00 PM, Imran Khan wrote:
> Add initial pinctrl driver to support pin configuration with
> pinctrl framework for msm8998.
>
> Signed-off-by: Imran Khan
You need review from the Qcom pinctrl maintainer Bjorn Andersson
for this patch.
+#define NORTH 0x50
+#define WE
Add missing req_id parameter to the iort_dev_find_its_id() function
kernel-doc comment.
Signed-off-by: Hanjun Guo
Cc: Lorenzo Pieralisi
Cc: Tomasz Nowicki
---
drivers/acpi/arm64/iort.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c
ind
I am working on doing selftests for openrisc and found issues with the
futex test not building after changes to the tests source.
The futex makefile did not contain dependencies for all headers, so if
we make changes to logging.h rebuild will not happen. Add headers to
fix it up.
Signed-off-by: S
On Mon, Jan 9, 2017 at 9:02 PM, David Daney wrote:
>> if (test_bit(line, gpio->invert_mask))
>>return !(read_bits & BIT(bank_bit));
>> else
>>return !!(read_bits & BIT(bank_bit));
>>
>> OK maybe not much clearer but seems clearer to me.
>
> As I really dislike the "!!" idiom, would you se
The indentation is wrong when return the iort_node, fix it.
Signed-off-by: Hanjun Guo
---
drivers/acpi/arm64/iort.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c
index ba156c5..ce3084b 100644
--- a/drivers/acpi/arm64/ior
On Wed, Jan 11, 2017 at 02:43:31PM +0100, Linus Walleij wrote:
> On Sat, Jan 7, 2017 at 9:54 PM, Clemens Gruber
> wrote:
>
> > I observed the following lockdep warning when booting an i.MX6Q board
> > with several PCAL9555A gpio expanders connected over I2C. They are
> > connected to 3 separate b
The intel_pstate kselftest expects that the output of
`cpupower frequency-info -l | tail -1 | awk ' { print $1 } '`
to get frequency limits. This does not work after the following two
changes.
- 562e5f1a3: rework the "cpupower frequency-info" command
(Jacob Tanenbaum) removed parsable limit o
From: Andy Lutomirski
> Sent: 10 January 2017 23:25
> There are some hashes (e.g. sha224) that have some internal trickery
> to make sure that only the correct number of output bytes are
> generated. If something goes wrong, they could potentially overrun
> the output buffer.
>
> Make the test mo
On Wed, Jan 11, 2017 at 02:59:26PM +, Mark Brown wrote:
> On Wed, Jan 11, 2017 at 12:49:36PM +0100, Nicholas Mc Guire wrote:
>
> > if (!rt5651->hp_mute)
> > - usleep_range(8, 85000);
> > + msleep(85);
>
> If you're doing conversions like thi
Adding ACPI support for platform MSI, we need to retrieve the
dev id in ACPI way instead of device tree, we already have
a well formed function its_pmsi_prepare() to get the dev id
but it's OF dependent, so collect OF related code and put them
into a single function to make its_pmsi_prepare() more
z3fold_compact_page() currently only handles the situation when
there's a single middle chunk within the z3fold page. However it
may be worth it to move middle chunk closer to either first or
last chunk, whichever is there, if the gap between them is big
enough.
This patch adds the relevant code,
This patch converts pages_nr per-pool counter to atomic64_t.
Signed-off-by: Vitaly Wool
---
mm/z3fold.c | 20 +---
1 file changed, 9 insertions(+), 11 deletions(-)
diff --git a/mm/z3fold.c b/mm/z3fold.c
index 207e5dd..2273789 100644
--- a/mm/z3fold.c
+++ b/mm/z3fold.c
@@ -80,7 +
Introduce its_pmsi_init_one() to refactor the code to isolate
ACPI&DT common code to prepare for ACPI later.
Signed-off-by: Hanjun Guo
Cc: Marc Zyngier
Cc: Tomasz Nowicki
Cc: Thomas Gleixner
---
drivers/irqchip/irq-gic-v3-its-platform-msi.c | 45 ---
1 file changed, 27
With the platform msi domain created, we can set up the msi domain
for a platform device when it's probed.
In order to do that, we need to get the domain that the platform
device connecting to, so the iort_get_platform_device_domain() is
introduced to retrieve the domain from iort.
After the doma
On Wed, 11 Jan 2017, Mathias Nyman wrote:
> On 17.11.2016 13:43, Sriram Dash wrote:
> > From: Arnd Bergmann
> >
> > For xhci-hcd platform device, all the DMA parameters are not
> > configured properly, notably dma ops for dwc3 devices. So, set
> > the dma for xhci from sysdev. sysdev is pointing
With the introduction of its_pmsi_init_one(), we can add some code
on top for ACPI support of platform MSI.
We are scanning the MADT table to get the ITS entry(ies), then use
the information to create the platform msi domain for devices connect
to it, just like the PCI MSI for ITS did.
Signed-off
On Wed, Jan 11, 2017 at 04:00:35PM +0100, Roman Sommer wrote:
> Note that this patch does not fix all checkpatch warnings for the
> affected files.
>
> Signed-off-by: Christian Bewermeyer
> Signed-off-by: Roman Sommer
Next time I suggest you drop "checkpatch: " from your subject since
that's no
platform_msi_create_device_domain() is used to ctreate
irqdomain for the device such as irqchip mbigen generating
the MSIs, it's almost ready for ACPI use except
of_node_to_fwnode() is for dt only, make it ACPI aware then
things will work in both DTS and ACPI.
Signed-off-by: Hanjun Guo
Cc: Marc Z
iort_node_map_platform_id() includes the function of
iort_node_get_id(), so update current iort_node_get_id()
users and move them over to iort_node_map_platform_id().
type handing in iort_node_get_id() is duplicate with
iort_node_map_platform_id(), so clean up a little
bit to make the code simpler
From: Kefeng Wang
Introduce mbigen_of_create_domain() to consolidate OF related
code and prepare for ACPI later, no funtional change.
Signed-off-by: Kefeng Wang
Signed-off-by: Hanjun Guo
Reviewed-by: Ma Jun
Cc: Marc Zyngier
Cc: Thomas Gleixner
---
drivers/irqchip/irq-mbigen.c | 42
Without this I am getting warnings of printf missing when compiling
selftests.
Signed-off-by: Stafford Horne
---
tools/testing/selftests/futex/include/logging.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/futex/include/logging.h
b/tools/testing/selftests/futex/in
This is followup to my previous patch [1] which was a very simple makefile
change. After a comment from Darren Hart I updated intel_pstate as well,
but noticed a few issues with running intel_pstate. That caused the change
to expand a bit.
- fix build deps for futex test *original*
- update make
From: Kefeng Wang
Module owner will be set by driver core, so drop it.
Signed-off-by: Kefeng Wang
Signed-off-by: Hanjun Guo
Reviewed-by: Ma Jun
Cc: Marc Zyngier
Cc: Thomas Gleixner
---
drivers/irqchip/irq-mbigen.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/irqchip/irq-mbige
iort_node_map_rid() was designed for both PCI and platform
device, but the rid means requester id is for ITS mappings,
rename iort_node_map_rid() to iort_node_map_id() and update
its argument names to make it more generic.
Signed-off-by: Hanjun Guo
Cc: Lorenzo Pieralisi
Cc: Tomasz Nowicki
---
For devices connecting to ITS, it needs dev id to identify itself, and
this dev id is represented in the IORT table in named component node
[1] for platform devices, so in this patch we will scan the IORT to
retrieve device's dev id.
For named components we know that there are always two steps
inv
Cleanup iort_match_node_callback() a little bit to reduce
some lines of code.
Signed-off-by: Hanjun Guo
Cc: Lorenzo Pieralisi
Cc: Tomasz Nowicki
---
drivers/acpi/arm64/iort.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/ar
501 - 600 of 934 matches
Mail list logo
