From: Peter Rosin
Allocate an explicit i2c mux core to handle parent and child adapters
etc. Update the select/deselect ops to be in terms of the i2c mux core
instead of the child adapter.
Signed-off-by: Peter Rosin
---
drivers/iio/imu/inv_mpu6050/inv_mpu_acpi.c | 2 +-
drivers/iio/imu/inv_mp
From: Peter Rosin
Allocate an explicit i2c mux core to handle parent and child adapters
etc. Update the select/deselect ops to be in terms of the i2c mux core
instead of the child adapter.
Signed-off-by: Peter Rosin
---
drivers/media/dvb-frontends/rtl2832.c | 22 +++---
dr
From: Peter Rosin
Allocate an explicit i2c mux core to handle parent and child adapters
etc. Update the select/deselect ops to be in terms of the i2c mux core
instead of the child adapter.
Signed-off-by: Peter Rosin
---
drivers/i2c/muxes/i2c-mux-pinctrl.c | 86 +
From: Peter Rosin
Allocate an explicit i2c mux core to handle parent and child adapters
etc. Update the select/deselect ops to be in terms of the i2c mux core
instead of the child adapter.
Signed-off-by: Peter Rosin
---
drivers/i2c/muxes/i2c-arb-gpio-challenge.c | 47 +-
From: Peter Rosin
All i2c-muxes have a parent adapter and one or many child
adapters. A mux also has some means of selection. Previously,
this was stored per child adapter, but it is only needed
to keep track of this per mux.
Add an i2c mux core, that keeps track of this consistently.
Also add
From: Peter Rosin
Allocate an explicit i2c mux core to handle parent and child adapters
etc. Update the select/deselect ops to be in terms of the i2c mux core
instead of the child adapter.
Signed-off-by: Peter Rosin
---
drivers/i2c/muxes/i2c-mux-gpio.c | 54
From: Peter Rosin
Allocate an explicit i2c mux core to handle parent and child adapters
etc. Update the select/deselect ops to be in terms of the i2c mux core
instead of the child adapter.
Add a mask to handle the case where not all child adapters should
cause a mux deselect to happen, now that
From: Peter Rosin
Allocate an explicit i2c mux core to handle parent and child adapters
etc. Update the select/deselect ops to be in terms of the i2c mux core
instead of the child adapter.
Signed-off-by: Peter Rosin
---
drivers/i2c/muxes/i2c-mux-pca9541.c | 55 -
From: Peter Rosin
Hi!
I have a pair of boards with this i2c topology:
GPIO ---| -- BAT1
| v /
I2C -+--B---+ MUX
| \
EEPROM -- BAT2
(B denotes the bound
Hi Khalid,
On Fri, Mar 4, 2016 at 4:42 AM, Khalid Aziz wrote:
> On 03/02/2016 06:33 PM, Julian Calaby wrote:
>>
>> Hi Khalid,
>>
>> A couple of other comments:
>>
>> On Thu, Mar 3, 2016 at 5:54 AM, Khalid Aziz
>> wrote:
>>>
>>>
>>> Enable Application Data Integrity (ADI) support in the sparc
>>>
On Wed, 2016-03-02 at 20:21 -0800, John Stultz wrote:
> From: "Christopher S. Hall"
>
> Modern Intel systems supports cross timestamping of the network
> device
> clock and Always Running Timer (ART) in hardware. This allows the
> device time and system time to be precisely correlated. The times
On Thu, Mar 3, 2016 at 2:21 AM, Thomas Gleixner wrote:
> On Wed, 2 Mar 2016, John Stultz wrote:
>
> Subject: x86: tsc: Always Running ...
>
> Please make that:
>
> Subject: x86/tsc: Always Running ...
Will do.
>
>>
>> +#else
>> +
>> +#define detect_art()
>
> Inline stub if at all. Why sits detec
Stephen Warren writes:
> On 02/26/2016 11:19 AM, Eric Anholt wrote:
>> The BCM2835-ARM-Peripherals.pdf documentation specifies what the
>> function selects do for the pins, and there are a bunch of obvious
>> groupings to be made. With these created, we'll be able to replace
>> bcm2835-rpi.dtsi'
From: Arnd Bergmann
Date: Wed, 2 Mar 2016 20:06:46 +0100
> The icn, act2000 and pcbit drivers are all for very old hardware,
> and it is highly unlikely that anyone is actually still using them
> on modern kernels, if at all.
>
> All three drivers apparently are for hardware that predates PCI
>
From: Lada Trimasova
Date: Thu, 3 Mar 2016 17:07:46 +0300
> Since ezchip network driver is written with big endian EZChip platform it
> is necessary to add support for little endian architecture.
>
> The first issue is that the order of the bits in a bit field is
> implementation specific. So a
On Sun, Feb 28, 2016 at 03:32:33PM +0200, Yaniv Gardi wrote:
> Different platform may have different number of lanes
> for the UFS link.
> Add parameter to device tree specifying how many lanes
> should be configured for the UFS link.
>
> Signed-off-by: Gilad Broner
> Signed-off-by: Yaniv Gardi
On Thu, 3 Mar 2016 07:52:51 -0600
Rob Herring wrote:
> On Wed, Mar 2, 2016 at 3:35 PM, David Rivshin (Allworx)
> wrote:
> > From: David Rivshin
> >
> > The of_property_{read,count,match}_string* family of functions never
> > modify the struct device_node pointer that is passed in, so there is n
Hello,
I'm using btrfs on am ARMv7 and it turns out, that the kernel has to
fixup a lot of kernel originated alignment issues.
See /proc/cpu/alignment (~4h of uptime):
> System: 22304815 (btrfs_get_token_64+0x13c/0x148 [btrfs])
For example, when compiling the kernel on a btrfs volume the counter
Hi Nicolas,
sorry for the late review.
Dne 29.2.2016 v 04:48 Nicolas Pitre napsal(a):
> +set -e
> +
> +cur_ksyms_file="include/generated/autoksyms.h"
> +new_ksyms_file="include/generated/autoksyms.h.tmpnew"
> +
> +info() { [ "$quiet" != "silent_" ] && printf " %-7s %s\n" "$1" "$2"; }
Using && a
On Sat, Feb 27, 2016 at 06:56:01PM +0300, Sergei Ianovich wrote:
> ICP DAS LP-8x4x contains FPGA chip. The chip functions as an interrupt
> source providing 16 additional interrupts among other things. The
> interrupt lines are muxed to a GPIO pin of a 2nd level PXA-GPIO
> interrupt controller. GPI
Adding a bit more context, in Android when we receive a uevent about a
new disk we use a separate userspace utility (sgdisk) to inspect the
partitions it contains, and we construct our own mknod() for the
partitions that we're interested in. (We're doing this manually
because Android doesn't have
On Fri, Feb 26, 2016 at 09:51:56AM -0500, Rik van Riel wrote:
> On Thu, 2016-02-25 at 22:17 -0800, Hugh Dickins wrote:
> > On Fri, 26 Feb 2016, Ebru Akagunduz wrote:
> > > in Thu, Feb 25, 2016 at 05:35:50PM -0500, Rik van Riel wrote:
> >
> > > > Am I forgetting anything obvious?
> > > >
> > > > I
On Sat, Feb 27, 2016 at 12:29:54PM +0530, Raveendra Padasalagi wrote:
> In Cygnus SOC touch screen controller registers are shared
> with ADC and flex timer. Using readl/writel could lead to
> race condition. So touch screen driver is enhanced to support
> register access using syscon framework API
On Fri, Feb 26, 2016 at 03:05:39PM -0800, Eric Anholt wrote:
> This is the other SD controller on the platform, which can be swapped
> to the role of SD card host using pin muxing.
>
> Signed-off-by: Eric Anholt
Acked-by: Rob Herring
Hi Sasha,
When I test v3.18.27 in the stable line, I'm suffering from the following soft
lockups.
This occurs during xfstests/013, which is 100% reproducile.
I've confirmed that the latest kernel has no problem.
[26459.346781] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s!
[kworker/u2:3:5
On a platform where 'Persistent Memory' and 'System RAM' are mixed
within a given sparsemem section, trim the namespace and notify about the
sub-optimal alignment.
Cc: Toshi Kani
Cc: Ross Zwisler
Signed-off-by: Dan Williams
---
drivers/nvdimm/namespace_devs.c |7 ++
drivers/nvdimm/pfn.h
On Thu, Mar 03 2016, Jens Axboe wrote:
> >No way do I want things like cgroup writeback changes outside the
> >merge window, for example, unless it's a major performance regression
> >(with numbers) or something like that.
> >
> >No way do I want any lightnvm stuff.
> >
> >No way do I want big "cle
Currenty with a raw mode pmem namespace the physical memory address range for
the device can be obtained via /sys/block/pmemX/device/{resource|size}. Add
similar attributes for pfn instances that takes the struct page memmap and
section padding into account.
Reported-by: Haozhong Zhang
Signed-of
On 03/03/2016 04:49 PM, Luck, Tony wrote:
retry:
- rc = erst_get_record_id_next(&pos, record_id);
- if (rc)
- goto out;
+ /*
+* Some hardware is broken and doesn't actually advance the record id
I'd blame this on firmware rather than hardware.
Yup sor
Permit platforms with section-misaligned persistent memory to establish
memory-mode (pfn) namespaces. This sacrifices 64-128MB of pmem to gain
third-party DMA/RDMA support.
Changes since v1 [1]:
1/ Dropped "mm: fix mixed zone detection in devm_memremap_pages" since
it was pulled into Andrew's
The altmap for a section-misaligned namespace needs to arrange for the
base_pfn to be section-aligned. As a result the 'reserve' region (pfns
from base that do not have a struct page) must be increased. Otherwise
we trip the altmap validation check in __add_pages:
if (altmap->base_pfn !=
> retry:
> - rc = erst_get_record_id_next(&pos, record_id);
> - if (rc)
> - goto out;
> + /*
> + * Some hardware is broken and doesn't actually advance the record id
I'd blame this on firmware rather than hardware.
> + * returned by ACPI_ERST_GET_RECORD_ID when
> + /*
> + * There are cases where, even though, the PEBS ovfl bit is set
> in
> + * GLOBAL_OVF_STATUS, the PEBS events may also have their
> overflow bits
> + * set for their counters. We must clear them here because they
> have
> +
From: Arnd Bergmann
Date: Wed, 2 Mar 2016 10:40:54 +0100
> The new NET_DEVLINK infrastructure can be a loadable module, but the drivers
> using it might be built-in, which causes link errors like:
>
> drivers/net/built-in.o: In function `mlx4_load_one':
> :(.text+0x2fbfda): undefined reference
On Thu, Mar 3, 2016 at 3:54 PM, Rob Clark wrote:
> On Thu, Mar 3, 2016 at 11:17 AM, Greg Kroah-Hartman
> wrote:
>> On Thu, Mar 03, 2016 at 11:37:17AM -0300, Gustavo Padovan wrote:
>>> From: Gustavo Padovan
>>>
>>> Play safe and add flags member to all structs. So we don't need to
>>> break API o
Certain code in the boot path may require the ability to determine whether
UEFI Secure Boot is definitely enabled, for example printing status to the
console. Other code may need to know when UEFI Secure Boot is definitely
disabled, for example restricting use of kernel parameters.
If an unexpecte
According to the UEFI specification (version 2.5 Errata A, page 87):
The platform firmware is operating in secure boot mode if the value of
the SetupMode variable is 0 and the SecureBoot variable is set to 1. A
platform cannot operate in secure boot mode if the SetupMode variable
i
This series modifies the function that queries the status of UEFI Secure Boot
in the EFI stub to match the UEFI specification, and allow the caller to
determine if it is enabled, disabled, or in an unknown state due to an
unexpected error from GetVariable().
v2:
- Add return values for unexpected
On Thu, Mar 03, 2016 at 01:21:48PM -0800, Luis R. Rodriguez wrote:
> The current documentation refers to using set_memor_wc() as a
> possible hole strategy when you have overlapping ioremap() regions,
> that's incorrect as set_memory_*() helpers can only be used on RAM,
> not IO memory. This fixes
On 03/03/2016 12:20 PM, Rafael J. Wysocki wrote:
>> Here is a comparison, with frequency invariance, of ondemand and
>> interactive with schedfreq and schedutil. The first two columns (run and
>> period) are omitted so the table will fit.
>>
>> ondemandinteractive schedfreq
On Thu, Mar 03, 2016 at 01:22:59PM -0800, H. Peter Anvin wrote:
> reason I can see for -8 though.
... and keeping the -8 won't hurt us or anything. I'll add a small
comment about it.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
On Tue, Jan 26, 2016 at 07:14:40PM +0300, Dmitriy Baranov wrote:
> Add I2C slave provider using the generic slave interface.
> It also supports master transactions when the slave in the idle mode.
>
> Issues:
> Changes work only in PIO mode (when driver doesn`t use DMA)
This is fine with me. We d
On Thu, Mar 3, 2016 at 10:53 AM, Radim Krčmář wrote:
> Linux guests on Haswell (and also SandyBridge and Broadwell, at least)
> would crash if you decided to run a host command that uses PEBS, like
> perf record -e 'cpu/mem-stores/pp' -a
>
> This happens because KVM is using VMX MSR switching to
On Mon, Jan 25, 2016 at 03:48:32PM +0300, Dmitriy Baranov wrote:
> Signed-off-by: Dmitriy Baranov
Applied to for-next, thanks! Please make sure to use a proper prefix in
the subject, like "i2c: imx:"
signature.asc
Description: PGP signature
On 03/03/2016 02:20 PM, Linus Torvalds wrote:
On Thu, Mar 3, 2016 at 1:11 PM, Jens Axboe wrote:
It does fix a regression - the change is that NVMe now uses the block layer
for these types of requests, and they don't have to adhere to the regular fs
limits of sizing. Hence we broke real use cas
At kernel summit, during the semantics of ioremap() session, Paul
mentioned we'd write something up to help get some notes out on what
we need to do and help clarify things. I've run into an issue (just a
warning) with a user on some odd system that I suspect may be the
result of a driver using ove
On 02/26/2016 11:19 AM, Eric Anholt wrote:
Since all of these pins were documented, we can use their names to
explain what's going on.
diff --git a/arch/arm/boot/dts/bcm2835-rpi-a-plus.dts
b/arch/arm/boot/dts/bcm2835-rpi-a-plus.dts
&gpio {
+ pinctrl-0 = <&i2c0_gpio0
+
On 03/03/16 12:54, Borislav Petkov wrote:
> On Thu, Mar 03, 2016 at 12:22:06PM -0800, H. Peter Anvin wrote:
>> The only thing I can think of is that the -8 creates a null pointer that
>> terminates a stack trace.
>
> Probably not needed anymore as print_context_stack()->valid_stack_ptr()
> in dump
The current documentation refers to using set_memor_wc() as a
possible hole strategy when you have overlapping ioremap() regions,
that's incorrect as set_memory_*() helpers can only be used on RAM,
not IO memory. This fixes that, and updates the documention to
*strongly* discourage overlapping iore
On 02/26/2016 11:19 AM, Eric Anholt wrote:
The BCM2835-ARM-Peripherals.pdf documentation specifies what the
function selects do for the pins, and there are a bunch of obvious
groupings to be made. With these created, we'll be able to replace
bcm2835-rpi.dtsi's main "set all of these pins to alt0
On Thu, Mar 3, 2016 at 1:11 PM, Jens Axboe wrote:
>
> It does fix a regression - the change is that NVMe now uses the block layer
> for these types of requests, and they don't have to adhere to the regular fs
> limits of sizing. Hence we broke real use cases, of (for instance) pulling
> logs off d
On Thu, Mar 3, 2016 at 6:14 PM, Diego Viola wrote:
> On Thu, Mar 3, 2016 at 2:55 AM, Diego Viola wrote:
>> On Thu, Mar 3, 2016 at 12:19 AM, Diego Viola wrote:
>>> On Wed, Mar 2, 2016 at 2:14 AM, Guo-Fu Tseng
>>> wrote:
On Wed, 24 Feb 2016 23:58:56 -0500 (EST), David Miller wrote
> Fro
On Fri, Feb 26, 2016 at 01:35:39AM +0800, Liguo Zhang wrote:
> Send the next transfer in the i2c irq handler, and only signal
> complete() when the entire transaction has been completed.
This describes what you do. But not why. Is this an improvment of
throughput? Is there a downside of interrupt
[runtime regression with "x86/mm/pat: Emulate PAT when it is disabled"] On
03/03/2016 (Thu 15:59) Paul Gortmaker wrote:
> So, the yocto folks moved from 4.1 to 4.4 and one of their automated
> qemu x86-32 boot tests started failing. None of the yocto details seem
> to matter since I offered to h
On 03/03/2016 01:57 PM, Linus Torvalds wrote:
On Thu, Mar 3, 2016 at 9:25 AM, Jens Axboe wrote:
=>
A set of fixes for 4.5-rc6 - it's a lot bigger than I would like at this
point, but there's really nothing in here that we should not merge for
4.5 final - with a possible exception [..]
With th
On Thu, Mar 3, 2016 at 3:07 PM, Rob Herring wrote:
> On Fri, Feb 26, 2016 at 10:19:27AM -0700, Joshua Henderson wrote:
>> Document the devicetree bindings for the watchdog peripheral found on
>> Microchip PIC32 SoC class devices.
>>
>> Signed-off-by: Joshua Henderson
>> Cc: Ralf Baechle
>> ---
>
On Thu, Mar 3, 2016 at 2:55 AM, Diego Viola wrote:
> On Thu, Mar 3, 2016 at 12:19 AM, Diego Viola wrote:
>> On Wed, Mar 2, 2016 at 2:14 AM, Guo-Fu Tseng wrote:
>>> On Wed, 24 Feb 2016 23:58:56 -0500 (EST), David Miller wrote
From: Diego Viola
Date: Tue, 23 Feb 2016 12:04:04 -0300
On Fri, Feb 26, 2016 at 09:28:54PM +0530, Sricharan R wrote:
> After the addition of V2 support, there was a regression observed
> when testing it on MSM8996. The reason is driver puts the controller
> in to RUN state and writes the data to be 'tx' ed in fifo. But controller
> has to be put in to '
On 03/03/2016 02:11 PM, Linus Torvalds wrote:
On Thu, Mar 3, 2016 at 12:57 PM, Linus Torvalds
wrote:
Feel free to resend the parts that are actually critical, but explain
exactly why they are so critical when you do.
Just to clarify: anything that contains "lightnvm" is definitely not
critic
On Thu, Mar 03, 2016 at 09:56:40PM +0100, Rafael J. Wysocki wrote:
> On Thu, Mar 3, 2016 at 12:16 PM, Peter Zijlstra wrote:
> > On Wed, Mar 02, 2016 at 03:12:33AM +0100, Rafael J. Wysocki wrote:
> >> The most important change from the previous version is that the
> >> ->fast_switch() callback take
On Thu, Mar 3, 2016 at 12:57 PM, Linus Torvalds
wrote:
>
> Feel free to resend the parts that are actually critical, but explain
> exactly why they are so critical when you do.
Just to clarify: anything that contains "lightnvm" is definitely not
critical enough. Are there even any users? I'm done
On Fri, Feb 26, 2016 at 04:24:11PM -0600, Nishanth Menon wrote:
> Message Manager is a hardware block used to communicate with various
> processor systems within certain Texas Instrument's Keystone
> generation SoCs.
>
> This hardware engine is used to transfer messages from various compute
> enti
On 02/29/2016 06:30 PM, Eric Anholt wrote:
From: Phil Elwell
The DT bindings for pinctrl-bcm2835 allow both the function and pull
to contain either one entry or one per pin. However, an error in the
DT parsing can cause failures if the number of pulls differs from the
number of functions.
Sign
On Thu, 2016-03-03 at 21:02 +0100, John Crispin wrote:
> Add ethernet support for MediaTek SoCs from the MT7623 family.
[]
> diff --git a/drivers/net/ethernet/mediatek/mtk_eth_soc.h
> b/drivers/net/ethernet/mediatek/mtk_eth_soc.h
[]
> +/* ugly macro hack to make sure hw_stats and ethtool strings a
On Fri, Feb 26, 2016 at 10:19:27AM -0700, Joshua Henderson wrote:
> Document the devicetree bindings for the watchdog peripheral found on
> Microchip PIC32 SoC class devices.
>
> Signed-off-by: Joshua Henderson
> Cc: Ralf Baechle
> ---
> Note: Please merge this patch series through the MIPS tree
So, the yocto folks moved from 4.1 to 4.4 and one of their automated
qemu x86-32 boot tests started failing. None of the yocto details seem
to matter since I offered to help and I've repropduced it using 100%
mainline kernels and a generic distro toolchain as well.
The test case is slightly compl
On Thu, 3 Mar 2016, Michal Hocko wrote:
> On Thu 03-03-16 01:54:43, Hugh Dickins wrote:
> > On Tue, 1 Mar 2016, Michal Hocko wrote:
> [...]
> > > So I have tried the following:
> > > diff --git a/mm/compaction.c b/mm/compaction.c
> > > index 4d99e1f5055c..7364e48cf69a 100644
> > > --- a/mm/compacti
On Thu, Mar 3, 2016 at 9:25 AM, Jens Axboe wrote:
=>
> A set of fixes for 4.5-rc6 - it's a lot bigger than I would like at this
> point, but there's really nothing in here that we should not merge for
> 4.5 final - with a possible exception [..]
With the possible exception of pretty much everythi
From: Anatol Pomazau
Some systems have a lot of power sensors and having an way to label sensor
makes easier to use sensor information.
Add dts property 'label' that is readable via device sysfs file 'label'.
Signed-off-by: Anatol Pomozov
---
Documentation/devicetree/bindings/hwmon/ina2xx.txt
On Thu, Mar 3, 2016 at 12:16 PM, Peter Zijlstra wrote:
> On Wed, Mar 02, 2016 at 03:12:33AM +0100, Rafael J. Wysocki wrote:
>> The most important change from the previous version is that the
>> ->fast_switch() callback takes an additional "relation" argument
>> and now the governor can use it to c
On Thu, Mar 03, 2016 at 12:22:06PM -0800, H. Peter Anvin wrote:
> The only thing I can think of is that the -8 creates a null pointer that
> terminates a stack trace.
Probably not needed anymore as print_context_stack()->valid_stack_ptr()
in dumpstack.c look at the stack boundaries instead of chec
On Thu, Mar 3, 2016 at 11:17 AM, Greg Kroah-Hartman
wrote:
> On Thu, Mar 03, 2016 at 11:37:17AM -0300, Gustavo Padovan wrote:
>> From: Gustavo Padovan
>>
>> Play safe and add flags member to all structs. So we don't need to
>> break API or create new IOCTL in the future if new features that requi
Hello.
On 03/03/2016 11:16 PM, Laurent Pinchart wrote:
Noticed a few typos as well, some alreayd reported...
The pm_runtime_force_suspend() and pm_runtime_force_resume() helpers are
designed to help driver being RPM-centric by offering an easy way to
manager runtime PM state during system s
On Sun, Jan 10, 2016 at 03:31:13PM -0800, richard.dor...@gmail.com wrote:
> From: Richard Vidal-Dorsch
>
> Signed-off-by: Richard Vidal-Dorsch
Well, most of the comments for the other drivers regarding the style
apply to this driver as well. I'll wait and see if the MFD core parts
get improved
On Wed, 2016-03-02 at 13:16 +0100, Alessio Igor Bogani wrote:
> Signed-off-by: Alessio Igor Bogani
> ---
> v2 -> v3
> Use appropriate git format-patch flag "-M" to detect renames
>
> v1 -> v2
> Address suggestion made by Scott Wood
> Split the second patch in two
> Don
On Thu, Mar 03, 2016 at 07:46:32PM +0100, Michał Kępień wrote:
> > Your description below helped explain why the KE_KEY change was necessary,
> > the
> > commit message didn't do that for me. Just explicitly stating "when there
> > is no
> > i8042 interrupt, the WMI even must generate a valid KE_
On Mon, Feb 29, 2016 at 9:57 PM, Masahiro Yamada
wrote:
> The "arm,amba-bus" string in the of_default_bus_match_table is
> ambiguous. This prepares for killing it off in a long run.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> arch/arm/boot/dts/axm55xx.dtsi | 2 +-
> arch/arm/boot/d
Hi Kevin,
(CC'ing Ulf)
Thank you for the review.
On Thursday 03 March 2016 12:35:53 Kevin Hilman wrote:
> Laurent Pinchart writes:
> > The pm_runtime_force_suspend() and pm_runtime_force_resume() helpers are
> > designed to help driver being RPM-centric by offering an easy way to
> > manager ru
Hi Rafael,
On Thursday 03 March 2016 21:34:04 Rafael J. Wysocki wrote:
> On Thu, Mar 3, 2016 at 9:32 PM, Rafael J. Wysocki wrote:
> > On Thu, Mar 3, 2016 at 9:24 PM, Kevin Hilman wrote:
> >> Laurent Pinchart writes:
> >>> During runtime resume the return values of the start and restore steps
>
Laurent Pinchart writes:
> The pm_runtime_force_suspend() and pm_runtime_force_resume() helpers are
> designed to help driver being RPM-centric by offering an easy way to
> manager runtime PM state during system suspend and resume. The first
s/manager/manage/
> function will force the device in
On Thu, Mar 3, 2016 at 9:32 PM, Rafael J. Wysocki wrote:
> On Thu, Mar 3, 2016 at 9:24 PM, Kevin Hilman wrote:
>> Laurent Pinchart writes:
>>
>>> During runtime resume the return values of the start and restore steps
>>> are ignored. As a result drivers are not notified of runtime resume
>>> fai
Hi Kevin,
Thank you for the review.
On Thursday 03 March 2016 12:24:23 Kevin Hilman wrote:
> Laurent Pinchart writes:
> > During runtime resume the return values of the start and restore steps
> > are ignored. As a result drivers are not notified of runtime resume
> > failures and can't propagat
On Thu, Mar 3, 2016 at 9:24 PM, Kevin Hilman wrote:
> Laurent Pinchart writes:
>
>> During runtime resume the return values of the start and restore steps
>> are ignored. As a result drivers are not notified of runtime resume
>> failures and can't propagate them up. Fix it by returning an error i
On Thu, Mar 3, 2016 at 4:12 AM, Jon Medhurst (Tixy) wrote:
> On Thu, 2016-03-03 at 12:07 +0900, Masahiro Yamada wrote:
> [...]
>> This patch is derived from Rob Herring' comment
>> "BTW, we should also kill off "amba-bus" which is an ambiguous term"
>> in the following thread:
>> http://lkml.iu.ed
Laurent Pinchart writes:
> During runtime resume the return values of the start and restore steps
> are ignored. As a result drivers are not notified of runtime resume
> failures and can't propagate them up. Fix it by returning an error if
> either the start or restore step fails, and clean up pr
On 03/03/16 08:29, Borislav Petkov wrote:
> On Thu, Mar 03, 2016 at 07:26:06AM -0800, H. Peter Anvin wrote:
>> Why -8?
>
> GLOBAL(stack_start)
> .quad init_thread_union+THREAD_SIZE-8
> ^^^
>
> But I don't see why it needed the -8 then. It
On Thu, Mar 3, 2016 at 9:06 PM, Steve Muckle wrote:
> On 03/03/2016 05:07 AM, Vincent Guittot wrote:
>> I mainly want to prevent any useless and periodic frequency switch
>> because of an utilization that changes with the current frequency (if
>> frequency invariance is not used) and that can make
The pm_runtime_force_suspend() and pm_runtime_force_resume() helpers are
designed to help driver being RPM-centric by offering an easy way to
manager runtime PM state during system suspend and resume. The first
function will force the device into runtime suspend at system suspend
time, while the se
Fabio Estevam writes:
> On Sat, Feb 20, 2016 at 12:48 PM, Robert Jarzmik
> wrote:
>
>> Hello,
>>
>> I'll reping once more, to see if any of you could give this patch a try.
>> So far Hitoshi doesn't have the hardware anymore, so it leaves only Guennadi
>> and
>> Fabio.
>>
>> If you could give
Add ethernet support for MediaTek SoCs from the MT7623 family. These have
dual GMAC. Depending on the exact version, there might be a built-in
Gigabit switch (MT7530). The core does not have the typical DMA ring setup.
Instead there is a linked list that we add descriptors to. There is only
one lin
> The same arguments would seem to apply to TASK_ISOLATION_ALL;
> note that applications don't actually go into task isolation mode
> without issuing the appropriate prctl(), so it shouldn't be too
That's a fair point. If it's entirely opt-in it's probably ok.
-Andi
On 21/02/16 03:41, Álvaro Fernández Rojas wrote:
> BCM6358 has a shared TLB which conflicts with current SMP support, so it must
> be disabled for now.
> BCM6358 uses >= 0xfffe addresses for internal registers, which need to be
> remapped (by using a simplified version of BRCM63xx ioremap.h).
>
Hi Al,
Somehow your email was filtered. Apologies for that.
On 02/10/2016 03:39 PM, Al Stone wrote:
> On 01/27/2016 05:17 AM, Aleksey Makarov wrote:
>>
>>
>> On 01/25/2016 07:11 PM, Peter Hurley wrote:
>>> On 01/25/2016 03:45 AM, Aleksey Makarov wrote:
This patchset is based on the patchset
On 21/02/16 03:41, Álvaro Fernández Rojas wrote:
> This adds a device tree example for SFR Neufbox4 (Sercomm version), which
> also serves as a real example for brcm,bcm6358-leds.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
[snip]
> + periph_intc: periph_intc@fffe000c {
Other exa
On 03/03/2016 05:07 AM, Vincent Guittot wrote:
> I mainly want to prevent any useless and periodic frequency switch
> because of an utilization that changes with the current frequency (if
> frequency invariance is not used) and that can make the formula
> selects another frequency than the current
Add myself and Felix as the Maintainers for the MediaTek ethernet driver.
Signed-off-by: Felix Fietkau
Signed-off-by: John Crispin
---
MAINTAINERS |7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9c4d157..b5293f3 100644
--- a/MAINTAINERS
+++ b/MAINTA
This adds the binding documentation for the MediaTek Ethernet
controller.
Signed-off-by: John Crispin
Cc: devicet...@vger.kernel.org
---
.../devicetree/bindings/net/mediatek-net.txt | 77
1 file changed, 77 insertions(+)
create mode 100644 Documentation/devicetree/b
This series adds support for the Mediatek ethernet core found on current ARM
based SoCs. The driver works on MT2701 and MT7623 SoCs
Instead of trying to upstream everything at once I decided to concentrate on
the important parts required to make current generation silicon work. The V3
series only
From: Gabriel Fernandez
Date: Mon, 29 Feb 2016 17:18:22 +0100
> This patch manages the case when you have an Ethernet MAC with
> a "fixed link", and not connected to a normal MDIO-managed PHY device.
>
> The test of phy_bus_name was not helpful because it was never affected
> and replaced by the
This patch adds the Makefile and Kconfig required to make the driver build.
Signed-off-by: John Crispin
---
drivers/net/ethernet/Kconfig |1 +
drivers/net/ethernet/Makefile |1 +
drivers/net/ethernet/mediatek/Kconfig | 17 +
drivers/net/ethernet/medi
301 - 400 of 1116 matches
Mail list logo
