On Fri, 2017-04-28 at 16:09 -0500, Rob Herring wrote:
> On Fri, Apr 28, 2017 at 05:10:34PM +0800, Ryder Lee wrote:
> > Add binding document for Mediatek PCIe Gen2 v1 host controller driver.
> >
> > Signed-off-by: Ryder Lee
> > ---
> > .../bindings/pci/mediatek,gen2v1-pcie.txt | 174
> >
On Fri, 2017-04-28 at 12:52 -0500, Rob Herring wrote:
> On Sun, Apr 23, 2017 at 04:17:33PM +0800, Ryder Lee wrote:
> > Add documentation for PCIe PHY available in MT7623 series SoCs.
> >
> > Signed-off-by: Ryder Lee
> > ---
> > .../devicetree/bindings/phy/phy-mt7623-pcie.txt| 67
> > +++
Hi Arnd,
> 2017-04-28 19:41 GMT+08:00 Arnd Bergmann :
>
> On Fri, Apr 28, 2017 at 4:46 AM, Ryder Lee
> wrote:
> > On Thu, 2017-04-27 at 21:06 +0200, Arnd Bergmann wrote:
> >> On Wed, Apr 26, 2017 at 10:10 AM, Ryder Lee
> wrote:
> >> > On Tue, 201
Hi Linus,
please pull from the 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
to receive the following updates:
The majority of the s390 patches for the 4.12 merge window:
* Included are three merges for KVM/s390 with changes for vfio-ccw a
From: MaJun
Don't minus reserved interrupts (64) when get the clear
register offset, because the clear register space includes
the space of these 64 interrupts.
This bug wasn't discovered until we running the driver on
a new platform with an updated firmware. It turns out that
there is a timeout
On 04/29/2017 09:42 AM, Geliang Tang wrote:
Drop useless kfree when memdup_user() failed, since we have already
called kfree in memdup_user().
Signed-off-by: Geliang Tang
---
drivers/firmware/efi/test/efi_test.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers
From: Hanjun Guo
Some mbigens share memory regions, and devm_ioremap_resource
does not allow to share resources which will break the probe
of mbigen, in opposition to devm_ioremap.
This patch restores back usage of devm_ioremap function, but
with proper error handling and logging.
Fixes: 216646
From: Hanjun Guo
platform_get_resource() may return NULL, add proper
check to avoid potential NULL dereferencing.
Signed-off-by: Hanjun Guo
---
drivers/irqchip/irq-mbigen.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/irqchip/irq-mbigen.c b/drivers/irqchip/irq-mbigen.c
index
On 05/01/17 at 03:37pm, Yinghai Lu wrote:
> On Mon, May 1, 2017 at 4:41 AM, Baoquan He wrote:
> > arch/x86/mm/init_64.c | 6 --
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
> > index 15173d3..dbf4f00 100644
> > --- a/ar
On 28 April 2017 at 22:33, Tejun Heo wrote:
> Hello, Vincent.
>
> On Thu, Apr 27, 2017 at 10:29:10AM +0200, Vincent Guittot wrote:
>> On 27 April 2017 at 00:52, Tejun Heo wrote:
>> > Hello,
>> >
>> > On Wed, Apr 26, 2017 at 08:12:09PM +0200, Vincent Guittot wrote:
>> >> On 24 April 2017 at 22:14,
On Fri, Apr 28, 2017 at 1:03 AM, Richard Weinberger wrote:
> Am 24.04.2017 um 17:47 schrieb Richard Weinberger:
>>> So, if some flag should be implemented, who should do it? :)
>>
>> I'll not do it for you. ;)
>
> Please also see http://marc.info/?l=linux-fsdevel&m=149327990608749&w=2
>
Richard,
On 28 April 2017 at 19:46, Tejun Heo wrote:
> Hello, Vincent.
>
> On Thu, Apr 27, 2017 at 10:59:12AM +0200, Vincent Guittot wrote:
>> > But the only difference there is that we lose accuracy in calculation;
>> > otherwise, the end results are the same, no?
>>
>> Yes the end result is the same, it
On Tue, 2017-04-11 at 22:43 +0200, Richard Weinberger wrote:
> Makes sense.
>
> Artem, do you remember why UBIFS didn't set s_uuid in first place?
Just did not notice it I think.
Hi Linus,
The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:
Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git
tags/m68k-for-v4.12-tag1
for you to fetch ch
* Baoquan He wrote:
> On 05/01/17 at 03:37pm, Yinghai Lu wrote:
> > On Mon, May 1, 2017 at 4:41 AM, Baoquan He wrote:
> > > arch/x86/mm/init_64.c | 6 --
> > > 1 file changed, 4 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
> > > index
Below is the list of build error/warning regressions/improvements in
v4.11[1] compared to v4.10[2].
Summarized:
- build errors: +3/-1
- build warnings: +1102/-838
JFYI, when comparing v4.11[1] to v4.11-rc8[3], the summaries are:
- build errors: +3/-1
- build warnings: +608/-638
Note that
change in V3:
reword the commit message,explain why the specific clocks are need to be
critical.
change in v2:
fix up some clks which have their own driver, not need to set as critical clocks
Elaine Zhang (4):
clk: rockchip: rk3036: make pclk_ddrupctl as critical_clock
clk: rockchip: rk3228:
The jtag clk no driver to handle them.
But this clk need enable,so make it as critical.
The ddrphy\ddrupctl clks no driver to handle them,
Chip design requirements for these clock to always on,
The new document will update the description of these clock.
The pmu_hclk_otg0 is Chip design defect, m
No driver to handle this clk, Chip design requirements for this clock to always
on,
The new document will update the description of this clock.
Signed-off-by: Elaine Zhang
---
drivers/clk/rockchip/clk-rk3036.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/rockchip/clk-rk3036.c
On Sun 30-04-17 15:33:50, Arthur Marsh wrote:
>
>
> Michal Hocko wrote on 27/04/17 18:56:
> >On Thu 27-04-17 18:36:38, Arthur Marsh wrote:
> >[...]
> >>[55363.482931] QXcbEventReader: page allocation stalls for 10048ms, order:0,
> >>mode:0x14200ca(GFP_HIGHUSER_MOVABLE), nodemask=(null)
> >
> >Are
The atclk\dbg\jtag\xin12m\pclk_core clks no driver to handle them.
But this clks need enable,so make it as critical.
The ddrupctl0\ddrupctl1\publ0\publ1 clks no driver to handle them,
Chip design requirements for these clock to always on,
The new document will update the description of these clock
Hi Dmitry,
can you resend this series? I really think we should get this into
4.12 at least.
The jtag\bus\peri\initmem\rom\stimer\phy clks no driver to handle them.
But this clks need enable,so make it as critical.
The ddrupctl\ddrmon\ddrphy clks no driver to handle them,
Chip design requirements for these clock to always on,
The new document will update the description of these clock.
T
Amir,
Am 02.05.2017 um 09:19 schrieb Amir Goldstein:
> On Fri, Apr 28, 2017 at 1:03 AM, Richard Weinberger wrote:
>> Am 24.04.2017 um 17:47 schrieb Richard Weinberger:
So, if some flag should be implemented, who should do it? :)
>>>
>>> I'll not do it for you. ;)
>>
>> Please also see http:/
>-Original Message-
>From: Chris Wilson [mailto:ch...@chris-wilson.co.uk]
>Sent: Friday, April 28, 2017 6:09 PM
>To: Chen, Xiaoguang
>Cc: kra...@redhat.com; alex.william...@redhat.com; intel-
>g...@lists.freedesktop.org; intel-gvt-...@lists.freedesktop.org; Wang, Zhi A
>; zhen...@linux.i
On 05/02/17 at 09:24am, Ingo Molnar wrote:
>
> * Baoquan He wrote:
>
> > On 05/01/17 at 03:37pm, Yinghai Lu wrote:
> > > On Mon, May 1, 2017 at 4:41 AM, Baoquan He wrote:
> > > > arch/x86/mm/init_64.c | 6 --
> > > > 1 file changed, 4 insertions(+), 2 deletions(-)
> > > >
> > > > diff --gi
On Thu, Feb 16, 2017 at 11:34:16AM +0900, Byungchul Park wrote:
> pick_next_pushable_dl_task(rq) has BUG_ON(rq->cpu != task_cpu(task))
> when it returns a task other than NULL, which means that task_cpu(task)
> must be rq->cpu. So if task == next_task, then task_cpu(next_task) must
> be rq->cpu as
On Mon 01-05-17 21:12:35, Marc MERLIN wrote:
> Howdy,
>
> Well, sadly, the problem is more or less back is 4.11.0. The system doesn't
> really
> crash but it goes into an infinite loop with
> [34776.826800] BUG: workqueue lockup - pool cpus=6 node=0 flags=0x0 nice=0
> stuck for 33s!
> More logs
This is v4 of a driver for the Aspeed VUART. This version addresses feedback
from Andy and Greg, and includes Rob's ack for the bindings change.
The VUART is a serial device on the BMC side of the LPC bus that connects a BMC
to it's host processor.
We add a flag to the serial core to allow the dr
The probing of THRE irq behaviour assumes the other end will be reading
bytes out of the buffer in order to probe the port at driver init. In
some cases the other end cannot be relied upon to read these bytes, so
provide a flag for them to skip this step.
Bit 19 was chosen as the flags are a int a
On Tue, Apr 11, 2017 at 9:45 PM, Andy Shevchenko
wrote:
> On Mon, Apr 10, 2017 at 7:04 AM, Joel Stanley wrote:
>> From: Jeremy Kerr
>>
>> This change adds a driver for the 16550-based Aspeed virtual UART
>> device. We use a similar process to the of_serial driver for device
>> probe, but expose
From: Jeremy Kerr
This change adds a driver for the 16550-based Aspeed virtual UART
device. We use a similar process to the of_serial driver for device
probe, but expose some VUART-specific functions through sysfs too.
The VUART is two UART 'front ends' connected by their FIFO (no actual
serial
On Tue, May 2, 2017 at 8:52 AM, Hans-Christian Noren Egtvedt
wrote:
> Around Mon 27 Mar 2017 15:35:56 +0200 or thereabout, Hans-Christian Noren
> Egtvedt wrote:
>> Around Mon 27 Mar 2017 15:26:04 +0200 or thereabout, Boris Brezillon wrote:
>>> On Wed, 1 Mar 2017 21:44:26 +0100 Hans-Christian Nore
Hello Rob,
On 04/28/2017 10:53 PM, Rob Herring wrote:
> On Mon, Apr 10, 2017 at 05:19:55PM +0200, olivier moysan wrote:
>> This patch adds documentation of device tree bindings for the
>> STM32 SAI ASoC driver.
>>
>> Signed-off-by: olivier moysan
>> ---
>> .../devicetree/bindings/sound/st,stm32-
On Tue, May 2, 2017 at 9:28 AM, Geert Uytterhoeven wrote:
> JFYI, when comparing v4.11[1] to v4.11-rc8[3], the summaries are:
> - build errors: +3/-1
Nothing new to report.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li
On Tue, May 2, 2017 at 10:45 AM, Joel Stanley wrote:
> From: Jeremy Kerr
>
> This change adds a driver for the 16550-based Aspeed virtual UART
> device. We use a similar process to the of_serial driver for device
> probe, but expose some VUART-specific functions through sysfs too.
>
> The VUART i
From: Xiubo Li
For the "struct tcmu_cmd_entry" in cmd area, the minimum size
will be sizeof(struct tcmu_cmd_entry) == 112 Bytes. And it could
fill about (sizeof(struct rsp) - sizeof(struct req)) /
sizeof(struct iovec) == 68 / 16 ~= 4 data regions(iov[4]) by
default.
For most tcmu_cmds, the data
On Tue 02-05-17 14:14:52, Minchan Kim wrote:
> Oops, forgot to add lkml and linux-mm.
> Sorry for that.
> Send it again.
>
> >From 8ddf1c8aa15baf085bc6e8c62ce705459d57ea4c Mon Sep 17 00:00:00 2001
> From: Minchan Kim
> Date: Tue, 2 May 2017 12:34:05 +0900
> Subject: [PATCH] vmscan: scan pages unt
The open-osd domain doesn't exist anymore, and mails to the list lead
to really annoying bounced that repeat every day.
Also the primarydata address for Benny bounces, and while I have a new
one for him he doesn't seem to be maintaining the OSD code any more.
Which beggs the question: should we
The IOT2000 is industrial controller platform, derived from the Intel
Galileo Gen2 board. The variant IOT2020 comes with one LAN port, the
IOT2040 has two of them. They can be told apart based on the board asset
tag in the DMI table.
Based on patch by Sascha Weisenberger.
Signed-off-by: Jan Kiszk
* Paul E. McKenney wrote:
> On Mon, May 01, 2017 at 06:19:44PM -0700, Linus Torvalds wrote:
> > On Mon, May 1, 2017 at 2:59 AM, Ingo Molnar wrote:
> > > Linus,
> > >
> > > Please pull the latest core-rcu-for-linus git tree from:
> > >
> > >git://git.kernel.org/pub/scm/linux/kernel/git/tip/t
On Tue, 2017-05-02 at 17:15 +0930, Joel Stanley wrote:
> From: Jeremy Kerr
>
> This change adds a driver for the 16550-based Aspeed virtual UART
> device. We use a similar process to the of_serial driver for device
> probe, but expose some VUART-specific functions through sysfs too.
>
> The VUAR
Hi, I use "memtester -p 0x6c800 10G" to test physical address
0x6c800
Because this physical address is invalid, and valid_mmap_phys_addr_range()
always return 1, so it causes crash.
My question is that should the user assure the physical address is valid?
...
[ 169.147578] ? pani
On Tue, May 2, 2017 at 10:58 AM, Jan Kiszka wrote:
> The IOT2000 is industrial controller platform, derived from the Intel
> Galileo Gen2 board. The variant IOT2020 comes with one LAN port, the
> IOT2040 has two of them. They can be told apart based on the board asset
> tag in the DMI table.
>
> B
The Droid 4 has a isl29030 to measure ambient light (e.g. for
automatically adapting display brightness) and proximity.
Signed-off-by: Sebastian Reichel
---
Hi,
The (trivial) driver changes have already been queued to iio-testing:
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/co
On Mon 01-05-17 14:34:21, David Rientjes wrote:
[...]
> @@ -2204,8 +2204,17 @@ static void get_scan_count(struct lruvec *lruvec,
> struct mem_cgroup *memcg,
> }
>
> if (unlikely(pgdatfile + pgdatfree <= total_high_wmark)) {
> - scan_balance = SCAN_
On Tue, Feb 14, 2017 at 04:26:21PM +0900, Byungchul Park wrote:
Hello,
I did what you suggested. Is there anything I shoud do more?
If so, please let know.
Thank you,
Byungchul
> Change from v2
> - replace for_each(wake_list) with the safe version in scheduler.
> - fix a trivial comment in llis
On 04/27/2017 05:06 PM, Michal Hocko wrote:
> On Tue 25-04-17 12:42:57, Joonsoo Kim wrote:
>> On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote:
>>> On Mon 17-04-17 11:02:12, Joonsoo Kim wrote:
On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote:
> On Wed 12-04-17 10:35
> diff --git a/include/linux/bio.h b/include/linux/bio.h
> index d1b04b0e99cf..0975da6bebd9 100644
> --- a/include/linux/bio.h
> +++ b/include/linux/bio.h
> @@ -373,8 +373,10 @@ static inline struct bio *bio_next_split(struct bio
> *bio, int sectors,
> return bio_split(bio, sectors, gfp, bs)
mutex_destroy does nothing most of time, but it's better to call
it to make the code future proof and it also has some meaning
for like mutex debug.
Signed-off-by: Liang Chen
---
drivers/md/bcache/super.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/md/bcache/super.c b/drivers/m
On Sun, 30 Apr 2017, Mark Brown wrote:
> On Fri, Apr 28, 2017 at 12:56:21AM -0400, Javier Martinez Canillas wrote:
> > The Samsung email address will stop working soon, so use my personal
> > email address instead.
>
> Acked-by: Mark Brown
I think this is now yours to take.
--
Lee Jones
Linar
Around Tue 02 May 2017 10:46:58 +0300 or thereabout, Andy Shevchenko wrote:
> On Tue, May 2, 2017 at 8:52 AM, Hans-Christian Noren Egtvedt
> wrote:
>> Around Mon 27 Mar 2017 15:35:56 +0200 or thereabout, Hans-Christian Noren
>> Egtvedt wrote:
>>> Around Mon 27 Mar 2017 15:26:04 +0200 or thereabou
Looks fine,
Reviewed-by: Christoph Hellwig
although I think we really should kill off the block level bouncing
rather sooner than later.
On Tue, May 02, 2017 at 01:42:24PM +1000, NeilBrown wrote:
> This patch converts bioset_create() and
> bioset_create_nobvec() to not create a workqueue so
> alloctions will never trigger punt_bios_to_rescuer(). It
> also introduces bioset_create_rescued() and
> bioset_create_nobvec_rescued() which
Looks fine,
Reviewed-by: Christoph Hellwig
Looks fine,
Reviewed-by: Christoph Hellwig
Looks fine,
Reviewed-by: Christoph Hellwig
Almost low level functions from open firmware have used const to
qualify device_node structures, so add const for device_node
parameters in of_coresight related functions.
Reviewed-by: Stephen Boyd
Signed-off-by: Leo Yan
---
drivers/hwtracing/coresight/of_coresight.c | 4 ++--
include/linux/cor
On Mon, Apr 24, 2017 at 10:26:45AM -0400, Alex Deucher wrote:
> On Fri, Apr 21, 2017 at 6:53 PM, Eric Anholt wrote:
> > Daniel Vetter writes:
> >
> >> On Wed, Apr 19, 2017 at 7:55 PM, Eric Anholt wrote:
> >>> Daniel Vetter writes:
> On Tue, Apr 18, 2017 at 9:11 PM, Eric Anholt wrote:
> >>
On Mon, May 01, 2017 at 05:56:04PM -0400, Tejun Heo wrote:
> I still wonder what gcfs_rq se->load_avg.avg is good for tho? It's
> nice to keep the value in line but is it actually used anywhere?
Its used to manage its parent's cfs_rq sums boundary conditions. When we
enqueue the group se to the
On Mon, Apr 24, 2017 at 11:25:12AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Fri, 21 Apr 2017 12:10:14 +1000 Stephen Rothwell
> wrote:
> >
> > After merging the drm-misc tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/tee/tee_shm.c:87:2: error: u
On 01/05/17 22:26, Matthias Kaehlcke wrote:
> clang raises 'asm-operand-widths' warnings in inline assembly code when
> the size of an operand is < 64 bits and the operand width is unspecified.
> Most warnings are raised in macros, i.e. the datatype of the operand may
> vary. Forcing the use of an
On Fri, Apr 28, 2017 at 10:50 PM, Will Deacon wrote:
> On Fri, Apr 28, 2017 at 10:23:47AM +0530, Ganapatrao Kulkarni wrote:
>> This is not a full event list, but a short list of useful events.
>>
>> Signed-off-by: Ganapatrao Kulkarni
>> ---
>> tools/perf/pmu-events/arch/arm64/mapfile.csv |
On Tue, May 02, 2017 at 10:19:05AM +0200, Peter Zijlstra wrote:
> Can you have a play with something like the below? I suspect
> 'shares_runnable' might work for you here.
> ---
> kernel/sched/fair.c | 62
> +
> 1 file changed, 44 insertions(+)
ARMv8 architecture reference manual (ARM DDI 0487A.k) Chapter H7 "The
Sample-based Profiling Extension" has description for sampling
registers, we can utilize these registers to check program counter
value with combined CPU exception level, secure state, etc. So this is
helpful for CPU lockup bugs,
According to ARMv8 architecture reference manual (ARM DDI 0487A.k)
Chapter 'Part H: External debug', the CPU can integrate debug module
and it can support self-hosted debug and external debug. Especially
for supporting self-hosted debug, this means the program can access
the debug module from mmio
* Ingo Molnar wrote:
> > I will get rid of the unused rcu_segcblist_extract_all() function and
> > create a
> > kernel/rcu/segcblist.c for the functions that are either non-trivial or
> > performance-insensitive.
> >
> > Does that cover it, or am I missing something?
>
> I'd also suggest mo
Update kernel-parameters.txt to add new parameter:
coresight_cpu_debug.enable is a knob to enable debugging at boot time.
Add detailed documentation, which contains the implementation, Mike
Leach excellent summary for "clock and power domain". At the end some
examples on how to enable the debuggin
From: Suzuki K Poulose
The of_get_coresight_platform_data iterates over the possible CPU nodes
to find a given cpu phandle. However it does not drop the reference
to the node pointer returned by the of_get_coresight_platform_data.
This patch also introduces another minor fix is to use
of_cpu_dev
The firmware API should not be used after we go to suspend
and after we reboot/halt. The suspend/resume case is a bit
complex, so this documents that so things are clearer.
We want to know about users of the API in incorrect places so
that their callers are corrected, so this also adds a warn
for
Coresight includes debug module and usually the module connects with CPU
debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has
description for related info in "Part H: External Debug".
Chapter H7 "The Sample-based Profiling Extension" introduces several
sampling registers, e.g. we
Bind debug module driver for Hi6220.
Signed-off-by: Leo Yan
---
arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 64 +++
1 file changed, 64 insertions(+)
diff --git a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
b/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
index 470461d..467
This will make subsequent changes easier to read.
Signed-off-by: Luis R. Rodriguez
---
drivers/base/firmware_class.c | 77 +--
1 file changed, 38 insertions(+), 39 deletions(-)
diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
ind
Add debug unit on Qualcomm msm8916 based platforms, including the
DragonBoard 410c board.
Signed-off-by: Leo Yan
---
arch/arm64/boot/dts/qcom/msm8916.dtsi | 32
1 file changed, 32 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8916.dtsi
b/arch/arm64/boo
Gentle ping!
On 24/04/17 11:16, Vladimir Murzin wrote:
> It seem that addition of cache support for M-class CPUs uncovered
> latent bug in DMA usage. NOMMU memory model has been treated as being
> always consistent; however, for R/M CPU classes memory can be covered
> by MPU which in turn might co
We kill pending fallback requests on suspend and reboot,
the only difference is that on suspend we only kill custom
fallback requests. Provide a wrapper that lets us customize
the request with a flag.
This also lets us simplify the #ifdef'ery over the calls.
Signed-off-by: Luis R. Rodriguez
---
This moves the usermode helper locks into only code paths that use the
usermode helper API from the kernel. The usermode helper locks were
originally added to prevent stalling suspend, later the firmware cache
was added to help with this, and further later direct filesystem lookup
was added by Linu
On Tue, May 2, 2017 at 11:12 AM, Hans-Christian Noren Egtvedt
wrote:
> Around Tue 02 May 2017 10:46:58 +0300 or thereabout, Andy Shevchenko wrote:
>> On Tue, May 2, 2017 at 8:52 AM, Hans-Christian Noren Egtvedt
>> wrote:
>>> Around Mon 27 Mar 2017 15:35:56 +0200 or thereabout, Hans-Christian Nore
This is refactor to add function of_coresight_get_cpu(), so it's used to
retrieve CPU id for coresight component. Finally can use it as a common
function for multiple places.
Suggested-by: Mathieu Poirier
Reviewed-by: Suzuki K Poulose
Signed-off-by: Leo Yan
---
drivers/hwtracing/coresight/of_c
Now that we've have proper wrappers for the fallback mechanism
we can easily share the reboot notifier for the firmware_class
at all times.
This change will make subsequent modifications to the reboot
notifier easier to review.
Signed-off-by: Luis R. Rodriguez
---
drivers/base/firmware_class.c
This routine will used in functions declared earlier next. This
code shift has no functional changes, it will make subsequent
changes easier to read.
Signed-off-by: Luis R. Rodriguez
---
drivers/base/firmware_class.c | 32
1 file changed, 16 insertions(+), 16 del
Greg,
This v2 follows the last iteration submitted [0] and addresses one
build failure case which for some reason was not caught by 0-day, and
it also adjusts some documentation to make 'make htmldocs' happy. This
and the next series are available in git form on my linux-next
20170501-driver-data-
Hi Daniel,
On Tue, 2 May 2017 10:25:18 +0200 Daniel Vetter wrote:
>
> Since this is an all-new driver it might be best to stagger the pull
> requests and merge the new tee subsystem (or whatever it is) after drm?
>
> Not sure what to best do here ...
This will merge via Dave, so Dave just needs
On Tue 02-05-17 15:59:23, Xishi Qiu wrote:
> Hi, I use "memtester -p 0x6c800 10G" to test physical address
> 0x6c800
> Because this physical address is invalid, and valid_mmap_phys_addr_range()
> always return 1, so it causes crash.
>
> My question is that should the user assure t
On 29/04/2017 03:39, Geliang Tang wrote:
> Use offset_in_page() macro instead of open-coding.
>
> Signed-off-by: Geliang Tang
Acked-by: Richard Genoud
> ---
> Changes in v2:
> - include mm.h
> ---
> drivers/tty/serial/atmel_serial.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
On Wed, Apr 26, 2017 at 11:48:34AM +0100, Jose Abreu wrote:
> Some crtc's may have restrictions in the mode they can display. In
> this patch a new callback (crtc->mode_valid()) is introduced that
> is called at the same stage of connector->mode_valid() callback.
>
> This shall be implemented if t
Greg,
On the v6 series [0] I got good amount of feedback from Luca and from
AKASHI Takahiro, who is picking up on the firmware signing work. In this
respin I've addressed their feedback, mostly to do away with redundant
checks while we can just proactively prevent certain situations, added
a int t
The firmware API does not scale well: when new features are added we
either add a new exported symbol or extend the arguments of existing
routines. For the later case this means we need to traverse the kernel
with a slew of collateral evolutions to adjust old driver users. The
firmware API is also
This adds a load tester driver test_driver_data a for the new extensible
driver_data loader API, part of firmware_class. This test driver enables
you to build your tests in userspace by exposing knobs of the exported
API to userspace and enables a trigger action to mimic a one time use
of the kerne
As the firmware API evolves we keep extending functions with more arguments.
Stop this nonsense by proving an extensible data structure which can be used
to represent both user parameters and private internal parameters.
We introduce 3 data structures:
o struct driver_data_req_params - used fo
The driver data API provides support for looking for firmware
from a specific set of API ranges, so just use that. Since we
free the firmware on the callback immediately after consuming it,
this also takes avantage of that feature.
Signed-off-by: Luis R. Rodriguez
---
drivers/net/wireless/intel/
This documents the driver data API.
Signed-off-by: Luis R. Rodriguez
---
Documentation/driver-api/firmware/driver_data.rst | 167 +
Documentation/driver-api/firmware/index.rst| 1 +
Documentation/driver-api/firmware/introduction.rst | 16 ++
.../driver-api/firmwar
You are a recipient to Mrs Julie Leach Donation of $3 million USD.
Contact(julieleac...@gmail.com) for claims.
The commit 7efe665903d0 ("rtc: Disable EFI rtc for x86") turns off rtc-efi
option completely for x86 in rtc/Kconfig, to avoid possible crash caused by
buggy implementations of the time-related EFI runtime services.
In fact, there are more and more UEFI firmware has time-related EFI runtime
service
Hei Sakari,
On 04/30/2017 01:21 AM, Sakari Ailus wrote:
> Hi, Stan!!
>
> On Fri, Apr 28, 2017 at 12:13:52PM +0300, Stanimir Varbanov wrote:
> ...
>> +int helper_get_bufreq(struct venus_inst *inst, u32 type,
>> + struct hfi_buffer_requirements *req)
>> +{
>> +u32 ptype = HFI_P
On 2017/5/2 16:43, Michal Hocko wrote:
> On Tue 02-05-17 15:59:23, Xishi Qiu wrote:
>> Hi, I use "memtester -p 0x6c800 10G" to test physical address
>> 0x6c800
>> Because this physical address is invalid, and valid_mmap_phys_addr_range()
>> always return 1, so it causes crash.
>>
On Tue, May 2, 2017 at 10:41 AM, Stephen Rothwell wrote:
> Hi Daniel,
>
> On Tue, 2 May 2017 10:25:18 +0200 Daniel Vetter wrote:
>>
>> Since this is an all-new driver it might be best to stagger the pull
>> requests and merge the new tee subsystem (or whatever it is) after drm?
>>
>> Not sure wha
On Tue, 2 May 2017 07:47:40 +0200
Christophe LEROY wrote:
> Le 01/05/2017 à 23:46, Brian Norris a écrit :
> > On Fri, Feb 10, 2017 at 03:01:10PM +0100, Christophe Leroy wrote:
> >> On some hardware, the nCE signal is wired to the ChipSelect associated
> >> to bus address of the NAND, so it is a
On Fri, Apr 28, 2017 at 01:47:21PM +0200, Stefan Wahren wrote:
> Starting with commit 6fe729c4bdae ("serdev: Add serdev_device_write
> subroutine") the function serdev_device_write_buf cannot be used in
> atomic context anymore (mutex_lock is sleeping). So restore the old
> behavior.
Yeah, prevent
On Mon, 1 May 2017 14:02:46 -0700
Brian Norris wrote:
> Hi,
>
> On Tue, Jan 03, 2017 at 02:01:25PM +0100, Boris Brezillon wrote:
> > A lot of NANDs are implementing generic features in a non-generic way,
> > or are providing advanced auto-detection logic where the NAND ID bytes
> > meaning chang
1 - 100 of 620 matches
Mail list logo
