calc_lanman_hash() could return -ENOMEM or other errors, we should check
that everything went fine before using the calculated key.
Signed-off-by: Luis de Bethencourt
---
fs/cifs/sess.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/cifs/sess.c b/fs/cifs/sess.c
index a42e99c..538d9b5 1
On Wed, Jun 08, 2016 at 04:39:44PM +0900, Minchan Kim wrote:
> On Mon, Jun 06, 2016 at 03:48:31PM -0400, Johannes Weiner wrote:
> > @@ -832,9 +854,9 @@ static void __pagevec_lru_add_fn(struct page *page,
> > struct lruvec *lruvec,
> > * Add the passed pages to the LRU, then drop the caller's ref
On Wednesday, June 8, 2016 2:47:48 AM CEST Tony Lindgren wrote:
>
> * Arnd Bergmann [160607 01:11]:
> > A lot of these options are typical for all ARMv7 machines: AEABI, I2C, NEON,
> > PM, REGULATOR and VFP are things that we probably want to default to enabled
> > whenever we build a MULTI_V7 ke
On Wed 08-06-16 23:55:24, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > On Wed 08-06-16 06:49:24, Tetsuo Handa wrote:
> > > Michal Hocko wrote:
> > > > OK, so you are arming the timer for each mark_oom_victim regardless
> > > > of the oom context. This means that you have replaced one potential
> >
This is MT2701 DRM support RFC v3, based on 4.7-rc1.
Most codes are the same, except some register changed.
For example:
- DISP_OVL address offset changed, color format definition changed.
- DISP_RDMA fifo size changed.
- DISP_COLOR offset changed.
We add a new component DISP_BLS, and the conn
We need to acquire mutex before using the resources,
and need to release it after finished.
So we don't need to write registers in the blanking period.
Signed-off-by: YT Shen
---
drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 75 +++
drivers/gpu/drm/mediatek/mtk_drm_ddp.
There are some hardware settings changed, between MT8173 & MT2701:
DISP_OVL address offset changed, color format definition changed.
DISP_RDMA fifo size changed.
DISP_COLOR offset changed.
And add prefix for mtk_ddp_main & mtk_ddp_ext & mutex_mod.
Signed-off-by: YT Shen
---
drivers/gpu/drm/media
Add MT8173 prefix for hardware related macros.
Signed-off-by: YT Shen
---
drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 60
1 file changed, 30 insertions(+), 30 deletions(-)
diff --git a/drivers/gpu/drm/mediatek/mtk_drm_ddp.c
b/drivers/gpu/drm/mediatek/mtk_drm_ddp
On Wed, Jun 08, 2016 at 05:14:21PM +0900, Minchan Kim wrote:
> On Mon, Jun 06, 2016 at 03:48:33PM -0400, Johannes Weiner wrote:
> > @@ -249,15 +249,10 @@ void rotate_reclaimable_page(struct page *page)
> > }
> > }
> >
> > -static void update_page_reclaim_stat(struct lruvec *lruvec,
> > -
This patch adds the device nodes for the DISP function blocks for MT2701
Signed-off-by: YT Shen
---
arch/arm/boot/dts/mt2701.dtsi | 106 +
1 file changed, 106 insertions(+)
diff --git a/arch/arm/boot/dts/mt2701.dtsi b/arch/arm/boot/dts/mt2701.dtsi
index
This patch add support for the Mediatek MT2701 DISP subsystem.
There is only one OVL engine in MT2701.
Signed-off-by: YT Shen
---
drivers/gpu/drm/mediatek/mtk_disp_ovl.c |6
drivers/gpu/drm/mediatek/mtk_disp_rdma.c|6
drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 42 +
On Wed 08-06-16 08:31:21, Dave Hansen wrote:
> On 06/08/2016 07:35 AM, Lukasz Odzioba wrote:
> > diff --git a/mm/swap.c b/mm/swap.c
> > index 9591614..3fe4f18 100644
> > --- a/mm/swap.c
> > +++ b/mm/swap.c
> > @@ -391,9 +391,8 @@ static void __lru_cache_add(struct page *page)
> > struct pagevec
Vitaly Kuznetsov writes:
> I'm hitting 5 second timeout in rndis_filter_set_rss_param() while setting
> RSS parameters for the device. When this happens we end up returning
> -ETIMEDOUT from the function and rndis_filter_device_add() falls back to
> setting
>
> net_device->max_chn = 1;
>
On 06/08/2016 08:56 AM, Prasun Maiti wrote:
Please help me how to test this one?? It will be great to me if you help me.
I do not have time or interest, sorry. You basically need access to
firmware source to do any useful development on this driver in my opinion,
and I do not have access to th
On Jun 8, 2016, at 6:58 AM, Jeff Layton wrote:
> A simple way to confirm that might be to convert all of the read locks
> on the st_rwsem to write locks. That will serialize all of the open
> operations and should prevent that particular race from occurring.
>
> If that works, we'd probably want
On Wednesday 08 June 2016 09:20 PM, Lee Jones wrote:
On Wed, 11 May 2016, Keerthy wrote:
mfd_add_devices enables parsing device tree nodes without compatibles
for child nodes. Replace of_platform_populate with mfd_add_devices.
Signed-off-by: Keerthy
---
drivers/mfd/tps65218.c | 10 +++
On Fri, 13 May 2016, Keerthy wrote:
> The LP873X chip is a power management IC for Portable Navigation Systems
> and Tablet Computing devices. It contains the following components:
>
> - Regulators.
> - Configurable General Purpose Output Signals(GPO).
>
> PMIC interacts with the m
On Wednesday 08 June 2016 09:21 PM, Lee Jones wrote:
On Fri, 13 May 2016, Keerthy wrote:
Add information for the mfd and regulator drivers.
Acked-by: Rob Herring
Signed-off-by: Keerthy
---
Changes in v3:
* Changed the example node lable to pmic from lp8733.
Documentation/devicetree
On Wed, Jun 08, 2016 at 11:21:16AM -0400, Neil Leeder wrote:
>
>
> On 6/6/2016 05:04 AM, Mark Rutland wrote:
> > On Fri, Jun 03, 2016 at 05:03:30PM -0400, Neil Leeder wrote:
> >> This adds a new dynamic PMU to the Perf Events framework to program
> >> and control the L2 cache PMUs in some Qualcom
On 06/08/2016 08:46 AM, Kees Cook wrote:
On Tue, Jun 7, 2016 at 6:02 PM, Laura Abbott wrote:
On 06/07/2016 02:57 PM, Kees Cook wrote:
This adds a function that lives in the .rodata section. The section
flags are corrected using objcopy since there is no way with gcc to
declare section flags i
On Wed, Jun 08, 2016 at 02:51:37PM +0200, Michal Hocko wrote:
> On Mon 06-06-16 15:48:33, Johannes Weiner wrote:
> > Rename struct zone_reclaim_stat to struct lru_cost, and move from two
> > separate value ratios for the LRU lists to a relative LRU cost metric
> > with a shared denominator.
>
> I
On Wednesday 08 June 2016 09:41 PM, Lee Jones wrote:
On Fri, 13 May 2016, Keerthy wrote:
The LP873X chip is a power management IC for Portable Navigation Systems
and Tablet Computing devices. It contains the following components:
- Regulators.
- Configurable General Purpose
We saw a list corruption in the list all_detected_devices:
WARNING: CPU: 16 PID: 226 at lib/list_debug.c:29 __list_add+0x3c/0xa9()
list_add corruption. next->prev should be prev (880859d58320), but was
880859ce74c0. (next=81abfdb0).
Modules linked in: ahci libahci libata sd_mod
On Wed, Jun 08, 2016 at 06:57:37PM +0300, Pantelis Antoniou wrote:
> Hi Mark,
>
> > On Jun 8, 2016, at 18:17 , Mark Rutland wrote:
> >
> > On Wed, Jun 08, 2016 at 04:16:32PM +0200, Jan Kiszka wrote:
> >> Hi all,
> >>
> >> already started the discussion off-list with Pantelis, but it's better
>
Hi Ashwin,
On Wed, Jun 8, 2016 at 5:18 AM, Ashwin Chaugule
wrote:
> + Prashanth (Can you please have a look as well?)
>
> On 31 May 2016 at 15:35, Hoan Tran wrote:
>> Hi Ashwin,
>
> Hi,
>
> Sorry about the delay. I'm in the middle of switching jobs and
> locations, so its been a bit crazy lately
* Vince Weaver wrote:
> eventually you can get them to send /proc/cpuinfo so you can try to find
> out what processor they really have, and in that case you can get
> the family/model numbers in plain decimal, and you can easily look up
> if things are supported in the various files.
If only i
With CONFIG_NVMEM, nvmem_cell_read() returns void *. With !CONFIG_NVMEM
it returns char *. Let's make that consistent. Also drop the
incorrect/inconsistent comment about char * above the nvmem_cell_read()
definition.
drivers/thermal/mtk_thermal.c is already working around this by casting
to (u32 *
On Wed, 08 Jun 2016 10:49:47 -0500 Greg KH
wrote
> On Wed, Jun 08, 2016 at 08:46:06AM -0500, Jaime Arrocha wrote:
> > From: Jaime Arrocha
> >
> > Replaced deprecated goto statements.
>
> Since when is 'goto' deprecated?
>
> Were you able to test these changes?
>
Python doesn't do automatic expansion of paths. In case one passes
path of the from ~/foo/bar the gdb scripts won't automatically expand
that and as a result the symbols files won't be loaded. Fix this
by explicitly expanding all paths which begin with "~"
Signed-off-by: Nikolay Borisov
---
scri
Yakir,
On Wed, Jun 8, 2016 at 4:52 AM, Yakir Yang wrote:
> The Sharp LQ123P1JX31 is an 12.3" 2400x1600 TFT-LCD panel
> connected using eDP interfaces.
>
> Signed-off-by: Yakir Yang
> ---
> Changes in v2:
> - Add dt-bindings of Sharp LQ123P1JX31 panel in v2
>
> .../devicetree/bindings/display/pa
Hi Mark,
> On Jun 8, 2016, at 19:23 , Mark Rutland wrote:
>
> On Wed, Jun 08, 2016 at 06:57:37PM +0300, Pantelis Antoniou wrote:
>> Hi Mark,
>>
>>> On Jun 8, 2016, at 18:17 , Mark Rutland wrote:
>>>
>>> On Wed, Jun 08, 2016 at 04:16:32PM +0200, Jan Kiszka wrote:
Hi all,
alread
On Wed, Jun 08, 2016 at 05:28:53PM +0200, Grigori Goronzy wrote:
> Are you sure it is using accelerated decoding? CPU load should be just 1-2%.
Ha, good point. So with mplayer vo=vdpau, CPU load was at something over 12%.
Doing:
$ mpv --vo=vdpau --hwdec=vdpau $file
(+) Video --vid=1 (*) (h264)
On 06/08/2016 09:06 AM, Michal Hocko wrote:
>> > Do we have any statistics that tell us how many pages are sitting the
>> > lru pvecs? Although this helps the problem overall, don't we still have
>> > a problem with memory being held in such an opaque place?
> Is it really worth bothering when we
Hello,
This patch series series aims at adding two important features to the
pwm-regulator driver.
The first one is the support for 'smooth handover' between the
bootloader and the kernel. This is mainly solving problems we have when
the PWM is controlling a critical regulator (like the one power
On Wed, Jun 08, 2016 at 06:25:29PM +0200, Ingo Molnar wrote:
> model string: IvyBridge_X
>
> ... or something like that. The string could even be auto-generated from the
> list
> in intel-family.h?
Yap, that sounds cool too. And then we should issue that too during boot:
[0.542398] sm
The pwm_prepare_new_state() helper prepares a new state object
containing the current PWM state except for the polarity and period
fields which are set to the reference values.
This is particurly useful for PWM users who want to apply a new
duty-cycle expressed relatively to the reference period wi
Use the atomic API wherever appropriate and get rid of pwm_apply_args()
call (the reference period and polarity are now explicitly set when
calling pwm_apply_state()).
We also make use of the pwm_set_relative_duty_cycle() helper to ease
relative to absolute duty_cycle conversion.
Note that change
The ->state field is currently initialized to 0, thus referencing the
voltage selector at index 0, which might not reflect the current voltage
value.
If possible, retrieve the current voltage selector from the PWM state, else
return -EINVAL.
Signed-off-by: Boris Brezillon
Tested-by: Brian Norris
Yakir,
On Wed, Jun 8, 2016 at 4:52 AM, Yakir Yang wrote:
> The Sharp LQ123P1JX31 is an 12.3", 2400x1600 TFT-LCD panel connected
> using eDP interfaces.
>
> Signed-off-by: Yakir Yang
> ---
> Changes in v2:
> - Add detail timing of Sharp LQ123P1JX31 panel in v2
>
> drivers/gpu/drm/panel/panel-sim
Document the pwm-dutycycle-unit and pwm-dutycycle-range properties.
Signed-off-by: Boris Brezillon
Acked-by: Brian Norris
---
.../devicetree/bindings/regulator/pwm-regulator.txt | 19 +++
1 file changed, 19 insertions(+)
diff --git a/Documentation/devicetree/bindings/regulato
The continuous mode allows one to declare a PWM regulator without having
to declare the voltage <-> dutycycle association table. It works fine as
long as your voltage(dutycycle) function is linear, but also has the
following constraints:
- dutycycle for min_uV = 0%
- dutycycle for max_uV = 100%
-
The continuous PWM voltage regulator is caching the voltage value in
the ->volt_uV field. While most of the time this value should reflect the
real voltage, sometime it can be sightly different if the PWM device
rounded the set_duty_cycle request.
Moreover, this value is not valid until someone has
The current implementation always round down the duty and period
values, while it would be better to round them to the closest integer.
These changes are needed in preparation of atomic update support to
prevent a period/duty cycle drift when executing several time the
'pwm_get_state() / modify /
Implement the ->apply() function to add support for atomic update.
Signed-off-by: Boris Brezillon
Tested-by: Heiko Stuebner
Reviewed-by: Brian Norris
Tested-by: Brian Norris
---
drivers/pwm/pwm-rockchip.c | 84 --
1 file changed, 43 insertions(+), 4
Implement ->get_state() to provide support for initial state retrieval.
Signed-off-by: Boris Brezillon
---
drivers/pwm/pwm-sti.c | 38 ++
1 file changed, 38 insertions(+)
diff --git a/drivers/pwm/pwm-sti.c b/drivers/pwm/pwm-sti.c
index 92abbd5..6300d3e 100644
The current logic will disable the PWM clk even if a PWM was left
enabled by the bootloader (because it's controlling a critical device
like a regulator for example).
Keep the PWM clk enabled if at least one PWM is enabled to avoid any
glitches.
Signed-off-by: Boris Brezillon
---
drivers/pwm/pwm
Copy the config fragments from the AOSP common kernel tree. It is
becoming possible to run mainline kernels with Android, but the kernel
defconfigs don't work as-is and debugging missing config options is a
pain. Adding the config fragments into the kernel tree, makes
configuring a mainline kernel
On 2016-06-08 18:31, Pantelis Antoniou wrote:
> Hi Mark,
>
>> On Jun 8, 2016, at 19:23 , Mark Rutland wrote:
>>
>> On Wed, Jun 08, 2016 at 06:57:37PM +0300, Pantelis Antoniou wrote:
>>> Hi Mark,
>>>
On Jun 8, 2016, at 18:17 , Mark Rutland wrote:
On Wed, Jun 08, 2016 at 04:16:32PM
The current logic will disable the PWM clk even if the PWM was left
enabled by the bootloader (because it's controlling a critical device
like a regulator for example).
Keep the PWM clk enabled if the PWM is enabled to avoid any glitches.
Signed-off-by: Boris Brezillon
Reviewed-by: Brian Norris
Implement the ->get_state() function to expose initial state.
Signed-off-by: Boris Brezillon
Reviewed-by: Brian Norris
Tested-by: Brian Norris
---
drivers/pwm/pwm-rockchip.c | 67 ++
1 file changed, 67 insertions(+)
diff --git a/drivers/pwm/pwm-rock
On Wed, Jun 08, 2016 at 09:26:46AM -0700, Brian Norris wrote:
> With CONFIG_NVMEM, nvmem_cell_read() returns void *. With !CONFIG_NVMEM
> it returns char *. Let's make that consistent. Also drop the
> incorrect/inconsistent comment about char * above the nvmem_cell_read()
> definition.
>
> drivers
The PWM attached to a PWM regulator device might have been previously
configured by the bootloader.
Make sure the bootloader and linux config are in sync, and adjust the PWM
config if that's not the case.
Signed-off-by: Boris Brezillon
Acked-by: Mark Brown
Acked-by: Brian Norris
Tested-by: Bria
The clocks group properties and the clock@0 node have been obsolete for two
years, remove them.
Cc: Sergio Tanzilli
Cc: Douglas Gilbert
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/at91-foxg20.dts | 9 -
1 file changed, 9 deletions(-)
diff --git a/arch/arm/boot/dts/at91-foxg
The clocks group properties and the clock@0 node have been obsolete for two
years, remove them.
Cc: Fabio Porcedda
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/ge863-pro3.dtsi | 9 -
1 file changed, 9 deletions(-)
diff --git a/arch/arm/boot/dts/ge863-pro3.dtsi
b/arch/arm/boo
The clocks group properties and the clock@0 node have been obsolete for two
years, remove them.
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/animeo_ip.dts | 9 -
1 file changed, 9 deletions(-)
diff --git a/arch/arm/boot/dts/animeo_ip.dts b/arch/arm/boot/dts/animeo_ip.dts
index
The clocks group properties and the clock@0 node have been obsolete for two
years, remove them.
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/at91-qil_a9260.dts| 9 -
arch/arm/boot/dts/tny_a9260_common.dtsi | 9 -
arch/arm/boot/dts/tny_a9263.dts | 9 -
The clocks group properties and the clock@0 node have been obsolete for two
years, remove them.
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/pm9g45.dts | 9 -
1 file changed, 9 deletions(-)
diff --git a/arch/arm/boot/dts/pm9g45.dts b/arch/arm/boot/dts/pm9g45.dts
index 66afcff6
The clocks group properties and the clock@0 node have been obsolete for two
years, remove them.
Cc: Sergio Tanzilli
Cc: Douglas Gilbert
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/at91-ariag25.dts | 9 -
1 file changed, 9 deletions(-)
diff --git a/arch/arm/boot/dts/at91-ari
The clocks group properties and the clock@0 node have been obsolete for two
years, remove them.
Cc: Rodolfo Giometti
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/at91-cosino.dtsi | 9 -
1 file changed, 9 deletions(-)
diff --git a/arch/arm/boot/dts/at91-cosino.dtsi
b/arch/arm
On Wed, Jun 8, 2016 at 12:32 PM, Borislav Petkov wrote:
> On Wed, Jun 08, 2016 at 05:28:53PM +0200, Grigori Goronzy wrote:
>> Are you sure it is using accelerated decoding? CPU load should be just 1-2%.
>
> Ha, good point. So with mplayer vo=vdpau, CPU load was at something over 12%.
>
> Doing:
>
The clocks group properties and the clock@0 node have been obsolete for two
years, remove them.
Cc: Joachim Eastwood
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/mpa1600.dts | 9 -
1 file changed, 9 deletions(-)
diff --git a/arch/arm/boot/dts/mpa1600.dts b/arch/arm/boot/dts/m
Hi Pramod,
On 05/06/2016 02:46 AM, Pramod Gurav wrote:
> uart_change_pm is used to turn on the UART controller resources and
> change UART's PM status. On failure to allocate pages the controller
> be left in ON state. This will change the state to OFF on failure.
>
> Signed-off-by: Pramod Gurav
On 08/06/16 16:44, Rob Herring wrote:
On Wed, Jun 1, 2016 at 1:06 AM, Kefeng Wang wrote:
The of_iommu_init() is called multiple times by arch code,
make it postcore_initcall_sync, then we can drop relevant
calls fully.
Note, the IOMMUs should have a chance to perform some basic
initialisation
On Wed, Jun 08, 2016 at 12:44:12PM -0400, Alex Deucher wrote:
> If the ring and IB tests pass on resume, you should be good to go.
Yap, they do. I pasted that output earlier but here it is again:
[ 64.745988] [drm] ring test on 0 succeeded in 1 usecs
[ 64.920633] [drm] ring test on 5 succeede
Le 08/06/2016 18:41, Alexandre Belloni a écrit :
> The clocks group properties and the clock@0 node have been obsolete for two
> years, remove them.
>
> Signed-off-by: Alexandre Belloni
On the whole series:
Acked-by: Nicolas Ferre
> ---
> arch/arm/boot/dts/animeo_ip.dts | 9 -
> 1 fil
Enable ARMv5 platforms in multi_v5
Signed-off-by: Alexandre Belloni
---
arch/arm/configs/multi_v5_defconfig | 54 -
1 file changed, 53 insertions(+), 1 deletion(-)
diff --git a/arch/arm/configs/multi_v5_defconfig
b/arch/arm/configs/multi_v5_defconfig
index 4
POWER ISA v3 defines a new idle processor core mechanism. In summary,
a) new instruction named stop is added. This instruction replaces
instructions like nap, sleep, rvwinkle.
b) new per thread SPR named PSSCR is added which controls the behavior
of stop instruction.
Use cpuidle's CPUIDLE_STATE_MAX macro instead of powernv specific
MAX_POWERNV_IDLE_STATES.
Cc: Rafael J. Wysocki
Cc: Daniel Lezcano
Cc: linux...@vger.kernel.org
Suggested-by: Daniel Lezcano
Signed-off-by: Shreyas B. Prabhu
---
- No changes after v5
Changes in v5
=
- New in v5
pnv_powersave_common does common steps needed before entering idle
state and eventually changes MSR to MSR_IDLE and does rfid to
pnv_enter_arch207_idle_mode.
Move the updation of HSTATE_HWTHREAD_STATE to pnv_powersave_common
from pnv_enter_arch207_idle_mode and make it more generic by passing the
If hardware supports stop state, use the deepest stop state when
the cpu is offlined.
Reviewed-by: Gautham R. Shenoy
Signed-off-by: Shreyas B. Prabhu
---
- No changes since v1
arch/powerpc/platforms/powernv/idle.c| 15 +--
arch/powerpc/platforms/powernv/powernv.h | 1 +
arch/
Functions like power7_wakeup_loss, power7_wakeup_noloss,
power7_wakeup_tb_loss are used by POWER7 and POWER8 hardware. They can
also be used by POWER9. Hence rename these functions hardware agnostic
names.
Suggested-by: Gautham R. Shenoy
Signed-off-by: Shreyas B. Prabhu
---
- No changes since v
idle_power7.S handles idle entry/exit for POWER7, POWER8 and in next
patch for POWER9. Rename the file to a non-hardware specific
name.
Reviewed-by: Gautham R. Shenoy
Signed-off-by: Shreyas B. Prabhu
---
- No changes since v3
Changes in v3:
==
- Instead of moving few common functi
In the current code, when the thread wakes up in reset vector, some
of the state restore code and check for whether a thread needs to
branch to kvm is duplicated. Reorder the code such that this
duplication is avoided.
At a higher level this is what the change looks like-
Before this patch -
powe
Signed-off-by: Shreyas B. Prabhu
---
-No changes since v4
Changes in v4
=
- New in v4
arch/powerpc/kernel/idle_power7.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/idle_power7.S
b/arch/powerpc/kernel/idle_power7.S
index 470ceeb..705c867 1
POWER ISA v3 defines a new idle processor core mechanism. In summary,
a) new instruction named stop is added.
b) new per thread SPR named PSSCR is added which controls the behavior
of stop instruction.
Supported idle states and value to be written to PSSCR register to enter
any idle stat
pnv_init_idle_states discovers supported idle states from the
device tree and does the required initialization. Set power_save
function pointer only after this initialization is done
Reviewed-by: Gautham R. Shenoy
Signed-off-by: Shreyas B. Prabhu
---
- No changes since v1
arch/powerpc/platform
POWER ISA v3 defines a new idle processor core mechanism. In summary,
a) new instruction named stop is added. This instruction replaces
instructions like nap, sleep, rvwinkle.
b) new per thread SPR named Processor Stop Status and Control Register
(PSSCR) is added which controls th
Create a function for saving SPRs before entering deep idle states.
This function can be reused for POWER9 deep idle states.
Reviewed-by: Gautham R. Shenoy
Signed-off-by: Shreyas B. Prabhu
---
- No changes since v3
Changes in v3:
=
- Newly added in v3
arch/powerpc/kernel/idle_po
On 06/03/2016 11:41 PM, Guenter Roeck wrote:
> On 05/31/2016 09:27 AM, Andrew F. Davis wrote:
>> Signed-off-by: Andrew F. Davis
>> ---
>> Documentation/hwmon/tmp401 | 18 +--
>> drivers/hwmon/Kconfig | 2 +-
>> drivers/hwmon/tmp401.c | 81
>> ++
Signed-off-by: Andrew F. Davis
---
Changes from v1:
- Dropped n-factor correction until a generic solution is developed
- Removed double empty line
Documentation/hwmon/tmp401 | 14 --
drivers/hwmon/Kconfig | 2 +-
drivers/hwmon/tmp401.c | 35 +-
Hi Ben,
Sorry for the delayed response.
On 06/06/2016 03:58 AM, Benjamin Herrenschmidt wrote:
> On Thu, 2016-06-02 at 07:38 -0500, Shreyas B. Prabhu wrote:
>> @@ -61,8 +72,13 @@ save_sprs_to_stack:
>> * Note all register i.e per-core, per-subcore or per-thread is saved
>> * here
On 06/03/2016 08:19 AM, Mark Rutland wrote:
> Commit cda64e6824026575 ("serial: earlycon: Fixup earlycon console name
> and index") added code to decompose an earlycon driver name into a
> string prefix and numeric suffix, and place this into console::name and
> console::index, such that we'd get a
When a large enough area in the iommu bitmap is found but would
span a boundary we continue the search starting from the next
bit position. For large allocations this can lead to several
useless invocations of bitmap_find_next_zero_area() and
iommu_is_span_boundary().
Continue the search from the
On Wed, Jun 08, 2016 at 11:28:11AM -0500, Jaime Arrocha wrote:
>
> On Wed, 08 Jun 2016 10:49:47 -0500 Greg KH
> wrote
>
> > On Wed, Jun 08, 2016 at 08:46:06AM -0500, Jaime Arrocha wrote:
> > > From: Jaime Arrocha
> > >
> > > Replaced deprecated goto statements.
> >
> >
On Wed, Jun 08, 2016 at 09:34:09AM +0800, zhouchengming wrote:
> On 2016/5/24 8:04, Yury Norov wrote:
> >Here new aarch32 ptrace syscall handler is introsuced to avoid run-time
> >detection of the task type.
> >
> >Signed-off-by: Yury Norov
[...]
> Hello, I found ilp32 will use sys_ptrace, not co
On Mon, May 09, 2016 at 03:05:08PM +0800, WEN Pingbo wrote:
> In some platforms, critical shared regulator is initialized in
> bootloader. But during kernel booting, the driver probing order and
> conflicting operations from other regulator consumers, may set the
> regulator in a undefined state,
I'm hitting 5 second timeout in rndis_filter_set_rss_param() while setting
RSS parameters for the device. When this happens we end up returning
-ETIMEDOUT from the function and rndis_filter_device_add() falls back to
setting
net_device->max_chn = 1;
net_device->num_chn = 1;
On Wed, Jun 8, 2016 at 12:25 PM, Marek Szyprowski
wrote:
> From: Krzysztof Kozlowski
>
> Allow drivers registering for certain runtime PM events of other
> devices. Some drivers in power domain are more or less coupled. When one
> driver is suspending (thus leading to power domain being also turn
On 2016/06/07 03:56PM, Alexei Starovoitov wrote:
> On Tue, Jun 07, 2016 at 07:02:23PM +0530, Naveen N. Rao wrote:
> > PPC64 eBPF JIT compiler.
> >
> > Enable with:
> > echo 1 > /proc/sys/net/core/bpf_jit_enable
> > or
> > echo 2 > /proc/sys/net/core/bpf_jit_enable
> >
> > ... to see the generated
On Wed, Jun 08, 2016 at 10:06:22AM -0700, Peter Hurley wrote:
> On 06/03/2016 08:19 AM, Mark Rutland wrote:
> > Commit cda64e6824026575 ("serial: earlycon: Fixup earlycon console name
> > and index") added code to decompose an earlycon driver name into a
> > string prefix and numeric suffix, and pl
Add CONFIG_EXYNOS_IOMMU in not set mode to make it easier to enable it.
Signed-off-by: Shuah Khan
---
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/exynos_defconfig
b/arch/arm/configs/exynos_defconfig
index daf9762..16c2957 100644
--- a/a
On Wed, Jun 8, 2016 at 7:31 AM, Lee Jones wrote:
>
> Please use full buffer width. Wrapping at 50 chars is not necessary.
But then how would you be able to review patches on your phone?! :)
>> --- a/drivers/mfd/hi655x-pmic.c
>> +++ b/drivers/mfd/hi655x-pmic.c
>> @@ -39,6 +39,11 @@ static const
On Wed, 2016-06-08 at 12:10 -0400, Oleg Drokin wrote:
> On Jun 8, 2016, at 6:58 AM, Jeff Layton wrote:
>
> > A simple way to confirm that might be to convert all of the read locks
> > on the st_rwsem to write locks. That will serialize all of the open
> > operations and should prevent that particu
On Wed, Jun 8, 2016 at 2:15 PM, Mark Brown wrote:
> On Thu, Jan 14, 2016 at 02:52:11AM +0100, Rafael J. Wysocki wrote:
>
>> What follows is my prototype implementation of this. It took some time
>> to develop (much more than I was hoping for), but here it goes at last.
>
> Might be worth posting
This mount option is to enable original log-structured filesystem forcefully.
So, there should be no random writes for main area.
Especially, this supports host-managed SMR device.
Signed-off-by: Jaegeuk Kim
---
Documentation/filesystems/f2fs.txt | 3 +++
fs/f2fs/data.c |
From: Dave Hansen
There were at least 3 features added to the __SI_FAULT area of the
siginfo struct that did not make it to the compat siginfo:
1. The si_addr_lsb used in SIGBUS's sent for machine checks
2. The upper/lower bounds for MPX SIGSEGV faults
3. The protection
If EIO occurred, we need to set all the mapping to avoid any further IOs.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index c9d6fe2..30dc448 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -
mkdirsync_dirty_inode
- init_inode_metadata
- lock_page(node)
- make_empty_dir
- filemap_fdatawrite()
- do_writepages
- lock_page(data)
- write_page(
Changes from v1:
* lots of style fixups to the MPX selftests. No
Functional changes.
---
We have not been updating the x86 compat_siginfo when updating the
generic one. These patches fix the issue, and then add a bunch
of build-time checks to try to avoid this happening again in the
future
We don't need to flush any dentry pages used by unlinked directory.
They will be truncated by f2fs_evict_inode.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
index 4179c7b..e67
301 - 400 of 1227 matches
Mail list logo
