On Mon, 14 Aug 2017, Steve Twiss wrote:
> On 06 June 2017 08:16, Lee Jones wrote:
> > > drivers/mfd/da9062-core.c | 6 --
> > > 1 file changed, 6 deletions(-)
> >
> > Applied, thanks.
>
> $ git describe
> v4.13-rc5
>
> Looking at linux-mainline today, I noticed a commit that seems to be ap
These snd_rawmidi_ops structures are only passed as the third
argument of snd_rawmidi_set_ops. This argument is const, so the
snd_rawmidi_ops structures can be const too.
Done with the help of Coccinelle.
Signed-off-by: Julia Lawall
---
sound/firewire/motu/motu-midi.c |4 ++--
1 file chan
These snd_rawmidi_ops structures are only passed as the third
argument of snd_rawmidi_set_ops. This argument is const, so the
snd_rawmidi_ops structures can be const too.
Done with the help of Coccinelle.
Signed-off-by: Julia Lawall
---
drivers/usb/gadget/function/f_midi.c |4 ++--
1 file
This snd_rawmidi_ops structure is only passed as the third
argument of snd_rawmidi_set_ops. This argument is const, so the
snd_rawmidi_ops structure can be const too.
Done with the help of Coccinelle.
Signed-off-by: Julia Lawall
---
drivers/hid/hid-prodikeys.c |2 +-
1 file changed, 1 ins
CONFIG_DEBUG_SHIRQ will fire extra irq action to call the registered
irq callback after driver is removed or failed to probe. In general,
the irq callback provided by driver should read its internal registers
to see who fires the irq. So this leads a situation that we access the
registers with a p
With CONFIG_DEBUG_SHIRQ enabled, the irq tear down routine
would still access the irq handler registed as a shard irq.
Per the comment within the function of __free_irq, it says
"It's a shared IRQ -- the driver ought to be prepared for
an IRQ event to happen even now it's being freed". However
when
On Mon 14-08-17 09:14:42, Dan Williams wrote:
> On Mon, Aug 14, 2017 at 5:40 AM, Jan Kara wrote:
> > On Sun 13-08-17 13:31:45, Dan Williams wrote:
> >> On Sun, Aug 13, 2017 at 2:24 AM, Christoph Hellwig wrote:
> >> > Thay being said I think we absolutely should support RDMA memory
> >> > registra
This patch was applied to the MFD twice, causing unwanted behavour.
This reverts commit b77eb79acca3203883e8d8dbc7f2b842def1bff8.
Fixes: b77eb79acca3 ("mfd: da9061: Fix to remove BBAT_CONT register from chip
model")
Reported-by: Steve Twiss
Signed-off-by: Lee Jones
---
drivers/mfd/da9062-core
Move dev_pm_domain_detach after devres_release_all to avoid
accessing device's registers with genpd been powered off.
Signed-off-by: Shawn Lin
---
Changes in v2: None
drivers/base/dd.c | 35 ++-
drivers/base/platform.c | 18 ++
2 files chan
On Tue 15-08-17 07:51:02, Tetsuo Handa wrote:
> Michal Hocko wrote:
[...]
> > Were you able to reproduce with other filesystems?
>
> Yes, I can reproduce this problem using both xfs and ext4 on
> 4.11.11-200.fc25.x86_64
> on Oracle VM VirtualBox on Windows.
Just a quick question.
http://lkml.ker
* Paul E. McKenney wrote:
> Hello, Ingo,
>
> This pull request is for an RCU change that permits waiting for grace
> periods started by CPUs late in the process of going offline. Lack of
> this capability is causing failures:
>
> http://lkml.kernel.org/r/db9c91f6-1b17-6136-84f0-03c3c2581...@c
Am Dienstag, 15. August 2017, 00:21:05 CEST schrieb Theodore Ts'o:
Hi Theodore,
> Have you looked at section 3.1.1 of the above cited paper?
>
> http://eprint.iacr.org/2012/251.pdf
Thanks for the hint, but that does not seem to solve the mystery either.
When I use magma with GF(2^32), I
On ppc64le machines the opal-rtc, resp rtc-generic in guest is used. They only
support minimal set of functionality and fail this test in not-yet treated
way. This extends the checks and skips to the next test when feature is not
supported.
Changes in v2:
- Removed the double EINVAL check
- Added
There is significant overhead in cache bouncing caused by zone counters
(NUMA associated counters) update in parallel in multi-threaded page
allocation (suggested by Dave Hansen).
This patch updates NUMA counter threshold to a fixed size of 32765, as a
small threshold greatly increases the update
Each page allocation updates a set of per-zone statistics with a call to
zone_statistics(). As discussed in 2017 MM submit, these are a substantial
source of overhead in the page allocator and are very rarely consumed. This
significant overhead in cache bouncing caused by zone counters (NUMA
associ
The rtc-generic and opal-rtc are failing to run this test as they do not
support all the features. Let's treat the error returns and skip to the
following test.
Theoretically the test_DATE should be also adjusted, but as it's enabled
on demand I think it makes sense to fail in such case.
Signed-o
In this patch, NUMA statistics is separated from zone statistics
framework, all the call sites of NUMA stats are changed to use
numa-stats-specific functions, it does not have any functionality change
except that the value of NUMA stats is shown behind zone page stats, and
the threshold size of NU
Commit-ID: a58163d8ca2c8d288ee9f95989712f98473a5ac2
Gitweb: http://git.kernel.org/tip/a58163d8ca2c8d288ee9f95989712f98473a5ac2
Author: Paul E. McKenney
AuthorDate: Tue, 20 Jun 2017 12:11:34 -0700
Committer: Paul E. McKenney
CommitDate: Tue, 25 Jul 2017 13:03:43 -0700
rcu: Migrate callb
On 2017/8/15 14:42, Thomas-Mich Richter wrote:
On 08/14/2017 06:39 PM, Arnaldo Carvalho de Melo wrote:
Em Mon, Aug 14, 2017 at 01:46:44PM +0200, Thomas Richter escreveu:
Perf BPF prologue generator unconditionally fetches 8 bytes for function
parameters, which causes problem on big endian mac
Hi,
On Aug 15 2017 17:09, Julia Lawall wrote:
These snd_rawmidi_ops structures are only passed as the third
argument of snd_rawmidi_set_ops. This argument is const, so the
snd_rawmidi_ops structures can be const too.
Done with the help of Coccinelle.
Signed-off-by: Julia Lawall
---
sound/
在 2017-08-15 13:55，Icenowy Zheng 写道：
Allwinner R40 SoC have a clock controller module in the style of the
SoCs beyond sun6i, however, it's more rich and complex.
Add support for it.
Signed-off-by: Icenowy Zheng
---
Changes in v5:
- Added TODO's for PLL constraints.
- Forced OHCI12M mux to 0.
-
Commit-ID: fa2016a8e7d846b306e431646d250500e1da0c33
Gitweb: http://git.kernel.org/tip/fa2016a8e7d846b306e431646d250500e1da0c33
Author: Andy Lutomirski
AuthorDate: Mon, 14 Aug 2017 22:36:19 -0700
Committer: Ingo Molnar
CommitDate: Tue, 15 Aug 2017 10:10:58 +0200
x86/xen/64: Fix the repo
On Tue, 15 Aug 2017 10:09:54 +0200,
Julia Lawall wrote:
>
> These snd_rawmidi_ops structures are only passed as the third
> argument of snd_rawmidi_set_ops. This argument is const, so the
> snd_rawmidi_ops structures can be const too.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Jul
On Thu, 10 Aug 2017, Dmitry Torokhov wrote:
> The power_supply subsystem tends to emit uevent every time
> power_supply_changed() is called, so we should call this API only when
> battery strength reported by the device is actually different from the
> previous readings, otherwise we'll drown the
On Tue, 15 Aug 2017, Takashi Iwai wrote:
> On Tue, 15 Aug 2017 10:09:54 +0200,
> Julia Lawall wrote:
> >
> > These snd_rawmidi_ops structures are only passed as the third
> > argument of snd_rawmidi_set_ops. This argument is const, so the
> > snd_rawmidi_ops structures can be const too.
> >
> >
On Tue, 8 Aug 2017, Joe Lawrence wrote:
> Hi folks,
>
> This is v2 of the livepatch (un)patch hook/notifier/callback/etc code.
>
> The documentation is still a little rough, but I wanted to post up the
> code for feedback before getting too far in revising it.
>
> This implements the pre and po
On Mon, Aug 14, 2017 at 11:12:05PM -0700, Dan Williams wrote:
> Changes since v3 [1]:
> * Move from an fallocate(2) interface to a new mmap(2) flag and rename
> 'immutable' to 'sealed'.
>
> * Do not record the sealed state in permanent metadata it is now purely
> a temporary state for as long
On Sun, 13 Aug 2017, Arvind Yadav wrote:
> platform_device_id are not supposed to change at runtime. All functions
> working with platform_device_id provided by
> work with const platform_device_id. So mark the non-const structs as
> const.
>
> Signed-off-by: Arvind Yadav
> ---
> drivers/hid/h
Le Fri, 11 Aug 2017 15:55:03 +0300,
Anton Vasilyev a écrit :
> Use api pair of request_mem_region and release_mem_region
> instead of release_resource.
>
> Found by Linux Driver Verification project (linuxtesting.
>
> Signed-off-by: Anton Vasilyev
> ---
> drivers/mtd/maps/plat-ram.c | 5 +++--
These snd_rawmidi_ops structures are only passed as the third
argument of snd_rawmidi_set_ops. This argument is const, so the
snd_rawmidi_ops structures can be const too.
Done with the help of Coccinelle.
---
drivers/hid/hid-prodikeys.c |2 +-
drivers/usb/gadget/function/f_midi.c
On Tue, 15 Aug 2017, Julia Lawall wrote:
> This snd_rawmidi_ops structure is only passed as the third
> argument of snd_rawmidi_set_ops. This argument is const, so the
> snd_rawmidi_ops structure can be const too.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall
>
> ---
>
Looks good,
Reviewed-by: Sagi Grimberg
p.s. we'll need also to update the configure timestamp configuration.
IRQ_WORK_FLAGS is defined simply to 3UL. This is confusing as it
says nothing about its purpose. Define IRQ_WORK_FLAGS as a bitwise
OR of IRQ_WORK_PENDING and IRQ_WORK_BUSY.
While we're at it: use the BIT() macro for all flags.
Signed-off-by: Bartosz Golaszewski
---
v1 -> v2:
- IRQ_WORK_LAZY is
Am 15.08.2017 um 05:49 schrieb Sandy Huang:
> This adds support for Rockchip soc lvds found on rk3288
> Based on the patches from Mark yao and Heiko Stuebner
>
> Signed-off-by: Sandy Huang
> Signed-off-by: Mark Yao
> Signed-off-by: Heiko Stuebner
> ---
> drivers/gpu/drm/rockchip/Kconfig
From: Sean Wang
Add MediaTek MT6380 regulator becoming one of PMIC wrapper slave
and also add extra new regmap_config of 32-bit mode for MT6380
since old regmap_config of 16-bit mode can't be fit into the need.
Signed-off-by: Chenglin Xu
Signed-off-by: Chen Zhong
Signed-off-by: Sean Wang
---
From: Sean Wang
Some regulators such as MediaTek MT6380 has to be read in 32-bit mode.
So the patch adds pwrap_read32, rename old pwrap_read into pwrap_read16
and one function pointer is introduced for increasing flexibility allowing
the determination which mode is used by the pwrap slave detecti
After the kernel ASLR, the module virtual address is moved to
[module_alloc_base, module_alloc_base + MODULES_VSIZE).
However, the MODULES_VADDR is still defined as a constant and functions
like is_vmalloc_or_module_addr() and dump function will not able to
use correct module range information.
Us
From: Sean Wang
pwrap initialization is highly associated with the base SoC, so
update here for allowing pwrap_init without slave program which would be
used to those PMICs without extra encryption on bus such as MT6380.
Signed-off-by: Chenglin Xu
Signed-off-by: Chen Zhong
Signed-off-by: Sean
From: Sean Wang
fixup those warnings such as lines over 80 words and parenthesis
alignment which would be complained by checkpatch.pl.
Signed-off-by: Sean Wang
---
drivers/soc/mediatek/mtk-pmic-wrap.c | 20 +---
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/dri
For the series,
Reviewed-by: Sagi Grimberg
From: Chenglin Xu
Add the registers, callbacks and data structures required to make the
PMIC wrapper work on MT7622.
Signed-off-by: Chenglin Xu
Signed-off-by: Chen Zhong
Signed-off-by: Sean Wang
---
drivers/soc/mediatek/mtk-pmic-wrap.c | 180 +++
1 file change
From: Sean Wang
Some regulators such as MediaTek MT6380 also has to be written in
32-bit mode. So the patch adds pwrap_write32, rename old pwrap_write
into pwrap_write16 and one additional function pointer is introduced
for increasing flexibility allowing the determination which mode is
used by t
From: Chenglin Xu
The MT6380 is a regulator found those boards with MediaTek MT7622 SoC
It is connected as a slave to the SoC using MediaTek PMIC wrapper which
is the common interface connecting with Mediatek made various PMICs.
Signed-off-by: Chenglin Xu
Signed-off-by: Sean Wang
---
drivers/
From: Sean Wang
add dt-binding document for MediaTek MT6380 PMIC
Signed-off-by: Chenglin Xu
Signed-off-by: Sean Wang
---
.../bindings/regulator/mt6380-regulator.txt| 89 ++
1 file changed, 89 insertions(+)
create mode 100644
Documentation/devicetree/bindings/regu
From: Sean Wang
Signed-off-by: Chenglin Xu
Signed-off-by: Sean Wang
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/soc/mediatek/pwrap.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/soc/mediatek/pwrap.txt
b/Documentation/devicetree/bindi
From: Sean Wang
Changes since v2:
- for patch 1/2, enhance the document as the suggestions from v2.
- for patch 3, constify the table with struct regulator_ops, also fix that
regulator doesn't have modesetting facilities it just shouldn't have the ops
and finally fix copy+paste mistake in warrant
2017-08-14 13:56 GMT+02:00 Bartosz Golaszewski :
> IRQ_WORK_FLAGS is defined simply to 3UL. This is confusing as it
> says nothing about its purpose. Define IRQ_WORK_FLAGS as a bitwise
> OR of IRQ_WORK_PENDING and IRQ_WORK_BUSY.
>
> While we're at it: use the BIT() macro for all flags.
>
> Signed-o
On Tue, Aug 08, 2017 at 02:25:10PM +0100, Will Deacon wrote:
> On Fri, Jul 28, 2017 at 04:12:33PM -0700, Greg KH wrote:
> > On Thu, Jul 27, 2017 at 03:15:15PM +0200, Borislav Petkov wrote:
> > > On Thu, Jul 27, 2017 at 11:08:56AM +0200, Jan Glauber wrote:
> > > > OK. As fixing the firmware will tak
On Tue, Aug 15, 2017 at 2:38 AM, wrote:
> From: Fenglin Wu
>
> GPIO LV (low voltage)/MV (medium voltage) subtypes have different
> features and register mappings than 4CH/8CH subtypes. Add support
> for LV and MV subtypes.
>
> Signed-off-by: Fenglin Wu
> Acked-by: Rob Herring
> Acked-by: Bjor
On Mon, Aug 14, 2017 at 11:12:22PM -0700, Dan Williams wrote:
> MAP_DIRECT is an mmap(2) flag with the following semantics:
>
> MAP_DIRECT
> In addition to this mapping having MAP_SHARED semantics, successful
> faults in this range may assume that the block map (logical-file-offset
> to ph
On Tue, Aug 15, 2017 at 2:38 AM, wrote:
> From: Fenglin Wu
>
> Add property "qcom,dtest-buffer" to specify which dtest rail to feed
> when the pin is configured as a digital input.
>
> Signed-off-by: Fenglin Wu
> Acked-by: Rob Herring
> Acked-by: Bjorn Andersson
Patch applied.
Yours,
Linus
Hi!
My new Thinkpad T470p regularly triggers this warning.
Seems to happy only after resuming from suspend.
[147242.220708] PM: Finishing wakeup.
[147242.220711] OOM killer enabled.
[147242.220711] Restarting tasks ...
[147242.221908] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 201
Hi Dmitry,
At 08/15/2017 03:18 PM, Dmitry Vyukov wrote:
Hello,
I am getting the following deadlock report while booting linux-next on
91dfed74eabcdae9378131546c446442c29bf769 in qemu. Config is attached.
WARNING: possible recursive locking detected
4.13.0-rc4-next-20170811 #2 Not tainted
Perf BPF prologue generator unconditionally fetches 8 bytes for function
parameters, which causes problem on big endian machine. Thomas gives a
detail analysis for this problem:
http://lkml.kernel.org/r/968ebda5-abe4-8830-8d69-49f62529d...@linux.vnet.ibm.com
This patch parses the type of each a
On Tue, Aug 8, 2017 at 8:16 AM, Andrew Jeffery wrote:
> HPLL was in fact not the clock we need. Remove prescription of which
> clock to avoid further error. Please refer to your datasheet and double
> check like I should have.
>
> Signed-off-by: Andrew Jeffery
Patch applied with the ACKs.
Your
On Thu, 10 Aug 2017, Jason Baron wrote:
>
>
> On 08/10/2017 07:12 AM, Miroslav Benes wrote:
> >
> > > Ok - associating the "atomic replace" with the patch itself makes sense to
> > > me.
> > > It would also basically work, I think with the patch I proposed except for
> > > the
> > > case where
On Tue, Aug 8, 2017 at 8:16 AM, Andrew Jeffery wrote:
> HPLL was in fact not the clock we need. Remove description of which
> clock to avoid any further error.
>
> Signed-off-by: Andrew Jeffery
Patch applied with Joel's ACK.
Yours,
Linus Walleij
Hi Pasha,
At 08/14/2017 11:44 PM, Pasha Tatashin wrote:
Hi Dou,
Thank you for your comments:
{
x86_init.timers.timer_init();
tsc_init();
+tsc_early_fini();
tsc_early_fini() is defined in patch 2, I guess you may miss it
when you split your patches.
Indeed, I will move it to
On Tue, 15 Aug 2017 11:00:17 +0200,
Julia Lawall wrote:
>
>
>
> On Tue, 15 Aug 2017, Takashi Iwai wrote:
>
> > On Tue, 15 Aug 2017 10:09:54 +0200,
> > Julia Lawall wrote:
> > >
> > > These snd_rawmidi_ops structures are only passed as the third
> > > argument of snd_rawmidi_set_ops. This argum
On Tue, Aug 15, 2017 at 11:20 AM, Dou Liyang wrote:
> Hi Dmitry,
>
> At 08/15/2017 03:18 PM, Dmitry Vyukov wrote:
>>
>> Hello,
>>
>> I am getting the following deadlock report while booting linux-next on
>> 91dfed74eabcdae9378131546c446442c29bf769 in qemu. Config is attached.
>>
>>
>> WARNING: pos
On 03/08/17 11:31, Adrian Hunter wrote:
> Hi
>
> Here is a script for exporting to SQLite 3 the same data as the PostgreSQL
> export. The call-graph script is renamed and amended to work with both
> PostgreSQL and SQLite.
>
>
> Adrian Hunter (5):
> perf script: Fix missing call_path_id in
On Tue, Aug 15, 2017 at 8:19 AM, Bernat, Yehezkel
wrote:
> The key size is tested by hex2bin() already (as '\0' isn't an hex digit)
Yes, and it's guaranteed (by kernelfs) that '\0' will be there sooner or later.
> Suggested-by: Andy Shevchenko
I'm using @linux.intel.com, though for this tag it
[CC Mel - the original patch was
http://lkml.kernel.org/r/1502138329-123460-6-git-send-email-pasha.tatas...@oracle.com]
On Mon 07-08-17 16:38:39, Pavel Tatashin wrote:
> In deferred_init_memmap() where all deferred struct pages are initialized
> we have a check like this:
>
> if (page->flags)
On Mon 14-08-17 10:01:52, Pasha Tatashin wrote:
> >>However, now thinking about it, I will change it to CONFIG_MEMBLOCK_DEBUG,
> >>and let users decide what other debugging configs need to be enabled, as
> >>this is also OK.
> >
> >Actually the more I think about it the more I am convinced that a k
On Mon, Aug 14, 2017 at 02:27:27PM -0600, Tycho Andersen wrote:
> Hi Mark,
>
> First, thanks for taking a look!
>
> On Sat, Aug 12, 2017 at 12:57:37PM +0100, Mark Rutland wrote:
> > On Wed, Aug 09, 2017 at 02:07:52PM -0600, Tycho Andersen wrote:
> > > From: Juerg Haefliger
> > >
> > > If the pa
Hello!
On 8/15/2017 9:50 AM, Colin King wrote:
From: Colin Ian King
The returns on some if statements are not indented correctly,
s/in/if/ in the subject?
add in the missing tab.
Signed-off-by: Colin Ian King
[...]
MBR, Sergei
From: Colin Ian King
The function acpi_processor_check_duplicates is local to the source and
does not need to be in global scope, so make it static.
Cleans up sparse warnings:
symbol 'acpi_processor_check_duplicates' was not declared. Should it
be static?
Signed-off-by: Colin Ian King
---
dri
From: Sean Wang
DT bindings shouldn't reference drivers and they should be OS-agnostic.
Signed-off-by: Sean Wang
---
Documentation/devicetree/bindings/regulator/mt6397-regulator.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/regulator/
From: Sean Wang
DT bindings shouldn't reference drivers and they should be OS-agnostic.
Signed-off-by: Sean Wang
---
Documentation/devicetree/bindings/regulator/mt6323-regulator.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/regulator/
From: Sean Wang
DT bindings shouldn't reference drivers and they should be OS-agnostic.
Signed-off-by: Sean Wang
---
Documentation/devicetree/bindings/regulator/mt6311-regulator.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/regulator/
Hi,
Chanwoo Choi writes:
> This patch replaces the deprecated extcon API as following:
> - extcon_get_cable_state_() -> extcon_get_state()
>
> Cc: Felipe Balbi
> Cc: Greg Kroah-Hartman
> Cc: Raviteja Garimella
> Signed-off-by: Chanwoo Choi
Do you want to take these through your tree or mine
On Tue, Aug 15, 2017 at 04:45:35PM +0800, Kemi Wang wrote:
> In this patch, NUMA statistics is separated from zone statistics
> framework, all the call sites of NUMA stats are changed to use
> numa-stats-specific functions, it does not have any functionality change
> except that the value of NUMA
From: Colin Ian King
The returns on some if statements are not indented correctly,
add in the missing tab.
Signed-off-by: Colin Ian King
---
net/bridge/netfilter/ebt_ip.c | 4 ++--
net/bridge/netfilter/ebt_ip6.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/net/bridge
Hi,
On Tue, Jul 25, 2017 at 08:10:37PM +0800, Shaokun Zhang wrote:
> This patch adds documentation for the uncore PMUs on HiSilicon SoC.
>
> Reviewed-by: Jonathan Cameron
> Signed-off-by: Shaokun Zhang
> Signed-off-by: Anurup M
> ---
> Documentation/perf/hisi-pmu.txt | 52
> +
On 15/08/17 10:45, Sergei Shtylyov wrote:
> Hello!
>
> On 8/15/2017 9:50 AM, Colin King wrote:
>
>> From: Colin Ian King
>>
>> The returns on some if statements are not indented correctly,
>
>s/in/if/ in the subject?
Doh, fix resent.
>
>> add in the missing tab.
>>
>> Signed-off-by: Coli
Hi,
Baolin Wang writes:
>> Currently the Linux kernel does not provide any standard integration of this
>> feature that integrates the USB subsystem with the system power regulation
>> provided by PMICs meaning that either vendors must add this in their kernels
>> or USB gadget devices based on
On Tue, Aug 15, 2017 at 04:45:36PM +0800, Kemi Wang wrote:
> Threshold CPU cyclesThroughput(88 threads)
> 32 799 241760478
> 64 640 301628829
> 125 537 358906028 <==> system by default (base)
> 256 468 4123
On Mon, Aug 14, 2017 at 11:41:55AM +0300, Stanimir Varbanov wrote:
> Hi,
>
> This RFC patch is intended to give to the drivers a choice to change
> the default behavior of the v4l2-core DMA mapping direction from
> DMA_TO/FROM_DEVICE (depending on the buffer type CAPTURE or OUTPUT)
> to DMA_BIDIRE
Hi,
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Subject: Re: [PATCH 1/3] ACPICA: Dispatch active GPEs at init time
>
> On Friday, August 11, 2017 7:40:56 AM CEST Zheng, Lv wrote:
> > Hi, Rafael
> >
> > > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> > > Subject: Re: [PATCH 1/3
When a need raise up to use JTAG interface for system's devices
programming or CPU debugging, it could be done from the external
JTAG master controller.
For such purpose, usually the user layer
application implements jtag protocol or using a proprietary
connection to vendor hardware.
This method i
It has been tested on Mellanox system with BMC equipped with
Aspeed 2520 SoC for programming CPLD devices.
Signed-off-by: Oleksandr Shamray
Signed-off-by: Jiri Pirko
---
v2->v3
Comments pointed by Rob Herring
- split Aspeed jtag driver and binding to sepatrate patches
- delete unnecessary "stat
Initial patch for JTAG friver
JTAG class driver provide infrastructure to support hardware/software
JTAG platform drivers. It provide user layer API interface for flashing
and debugging external devices which equipped with JTAG interface
using standard transactions.
Driver exposes set of IOCTL to
Driver adds support of Aspeed 2500/2400 series SOC JTAG master controller.
Driver implements the following jtag ops:
- freq_get;
- freq_set;
- status_get;
- idle;
- xfer;
It has been tested on Mellanox system with BMC equipped with
Aspeed 2520 SoC for programming CPLD devices.
Signed-off-by: Ole
Hi,
Danilo Krummrich writes:
> udc_stop needs to be called before gadget driver unbind. Otherwise it
> might happen that udc drivers still call into the gadget driver (e.g.
> to reset gadget after OTG event). If this happens it is likely to get
> panics from gadget driver dereferencing NULL ptr,
On Fri, Aug 04, 2017 at 05:06:19PM +0200, Michal Hocko wrote:
> On Thu 03-08-17 11:37:37, YASUAKI ISHIMATSU wrote:
> >
> >
> > On 08/02/2017 01:49 AM, joeyli wrote:
> > > Hi YASUAKI,
> > >
> > > On Tue, Aug 01, 2017 at 03:21:38PM -0400, YASUAKI ISHIMATSU wrote:
> > >> Hi Joey,
> > >>
> > >> On 0
On 08/14/17 10:41, Stanimir Varbanov wrote:
> Hi,
>
> This RFC patch is intended to give to the drivers a choice to change
> the default behavior of the v4l2-core DMA mapping direction from
> DMA_TO/FROM_DEVICE (depending on the buffer type CAPTURE or OUTPUT)
> to DMA_BIDIRECTIONAL during queue_in
Hi Boris,
Borislav Petkov writes:
> On Tue, Aug 01, 2017 at 02:36:07PM +0100, Punit Agrawal wrote:
>> During the driver init, the ghes driver initialises some data structures
>
> Let's stick to "GHES" in capital letters everywhere.
>
>> which are only used if a GHES platform device is probed. Si
Hi,
On Tue, Jul 25, 2017 at 08:10:38PM +0800, Shaokun Zhang wrote:
> +/* Read Super CPU cluster and CPU cluster ID from MPIDR_EL1 */
> +void hisi_read_sccl_and_ccl_id(u32 *sccl_id, u32 *ccl_id)
> +{
> + u64 mpidr;
> +
> + mpidr = read_cpuid_mpidr();
> + if (mpidr & MPIDR_MT_BITMASK) {
On 14/08/17 21:08, Rob Herring wrote:
> +linuxppc-dev
>
> On Fri, Aug 11, 2017 at 11:29 AM, Robin Murphy wrote:
>> Moving DMA configuration to happen later at driver probe time had the
>> unnoticed side-effect that we now perform DMA configuration for *every*
>> device represented in DT, rather t
On Tue, Aug 15, 2017 at 11:10:05AM +0100, Punit Agrawal wrote:
> In the absence of any GHES entries these are wasted.
I know. This whole APEI init code would need a proper cleanup, like
acpi_pci_root_init() calls acpi_hest_init() and it shouldn't have to
communicate through a variable with GHES wh
Hi Tony,
"Luck, Tony" writes:
> From: Tony Luck
>
> The ACPI Boot Error Record Table provides a method for platform
> firmware to give information to the operating system about error
> that occurred prior to boot (of particular interest are problems
> that caused the previous OS instance to cra
Hi Richard,
> My new Thinkpad T470p regularly triggers this warning.
> Seems to happy only after resuming from suspend.
>
> [147242.220708] PM: Finishing wakeup.
> [147242.220711] OOM killer enabled.
> [147242.220711] Restarting tasks ...
> [147242.221908] Bluetooth: hci0: Bootloader revision 0.
[ thanks for dropping the bad email! ]
Borislav Petkov writes:
> On Tue, Aug 15, 2017 at 11:10:05AM +0100, Punit Agrawal wrote:
>> In the absence of any GHES entries these are wasted.
>
> I know. This whole APEI init code would need a proper cleanup, like
> acpi_pci_root_init() calls acpi_hest_i
ccw_device_id are not supposed to change at runtime. AlL functions
working with ccw_device_id provided by work with
const ccw_device_id. So mark ccw_device_id as const.
Signed-off-by: Arvind Yadav
---
arch/s390/include/asm/ccwdev.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
ccw_device_id are not supposed to change at runtime. All functions
working with ccw_device_id provided by work with
const ccw_device_id. So mark ccw_device_id member of struct ccw driver
as const. And change all driver relatively.
Arvind Yadav (13):
[RFT 01/13] s390: ccwdev: constify ccw_device
ccw_device_id are not supposed to change at runtime. All functions
working with ccw_device_id provided by work with
const ccw_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/s390/char/con3215.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
ccw_device_id are not supposed to change at runtime. All functions
working with ccw_device_id provided by work with
const ccw_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/s390/char/raw3270.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
ccw_device_id are not supposed to change at runtime. All functions
working with ccw_device_id provided by work with
const ccw_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/s390/net/qeth_core_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-
ccw_device_id are not supposed to change at runtime. All functions
working with ccw_device_id provided by work with
const ccw_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/s390/char/tape_3590.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
d
ccw_device_id are not supposed to change at runtime. All functions
working with ccw_device_id provided by work with
const ccw_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/s390/char/vmur.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -
201 - 300 of 848 matches
Mail list logo
