Hello, Linus.
Nothing interesting. A couple device specific minor updates and a
kernel doc change.
Thanks.
The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
are available in the git repository at:
On Tue, Sep 1, 2015 at 9:08 AM, Felipe Balbi wrote:
> On Tue, Sep 01, 2015 at 11:12:18AM +0200, Sebastian Ott wrote:
>> On Mon, 31 Aug 2015, Felipe Balbi wrote:
>> > while booting AM437x device, the following splat
>> > triggered:
>> >
>> > [ 12.005238] ===
>> > [
Hello, Linus.
Only three trivial changes for workqueue this time - doc, MAINTAINERS
and EXPORT_SYMBOL updates.
Thanks.
The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
are available in the git repository at:
On Wednesday 02 September 2015 02:01 AM, Joe Perches wrote:
On Wed, 2015-09-02 at 00:54 +0530, Vaibhav Hiremath wrote:
There were some coding style issues where spaces have been used instead
of tabs, for example, in macro definitions, alignment of function
declarations/definitions, etc...
Intel Architecture Instruction Set Extensions Programing
Reference (Oct 2014) describes 3 new memory instructions,
namely clflushopt, clwb and pcommit. Add them to the op
code map and the perf tools new instructions test. e.g.
$ tools/perf/perf test "x86 ins"
39: Test x86 instruction
Add rdpkru and wrpkru to the op code map and the perf tools
new instructions test. In the case of the test, only the
bytes can be tested at the moment since binutils doesn't
support the instructions yet. To run the test:
$ tools/perf/perf test "x86 ins"
39: Test x86 instruction decoder
Intel SHA Extensions are explained in the Intel Architecture
Instruction Set Extensions Programing Reference (Oct 2014).
There are 7 new instructions. Add them to the op code map
and the perf tools new instructions test. e.g.
$ tools/perf/perf test "x86 ins"
39: Test x86 instruction
The patch
regulator: core: fix possible NULL dereference
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The MPX instructions are presently not described in the SDM
opcode maps, and there are not encoding characters for bnd
registers, address method or operand type. So the kernel
opcode map is using 'Gv' for bnd registers and 'Ev' for
everything else. That is fine because the instruction
decoder
Add a new test titled:
Test x86 instruction decoder - new instructions
The purpose of this test is to check the instruction decoder
after new instructions have been added. Initially, MPX
instructions are tested which are already supported, but the
definitions in x86-opcode-map.txt will
Add xsavec, xsaves and xrstors to the op code map and the
perf tools new instructions test. To run the test:
$ tools/perf/perf test "x86 ins"
39: Test x86 instruction decoder - new instructions : Ok
Or to see the details:
$ tools/perf/perf test -v "x86 ins" 2>&1 | grep
Hi
Here is version 2.
perf tools has a copy of the x86 instruction decoder for decoding
Intel PT. This patch set adds a perf tools test to use it to
test new instructions. Subsequent patches add a few new x86
instructions, or very slightly modify them in the case of MPX.
Those changes affect
perf tools has a copy of the x86 instruction decoder used by the kernel.
The expectation is that the copy will be kept more-or-less in-synch
with the kernel version. Consequently it is helpful to know if there are
differences. This patch adds a check into the perf tools build so that
a diff is
Hi Lars,
On 31.08.2015 17:57, Lars-Peter Clausen wrote:
On 08/17/2015 02:45 PM, Vladimir Barinov wrote:
Hello Daniel,
I've verified that your hrtimer trigger works.
I have minor suggestions.
Will not it be useful to have ability to stop/start hrtimer polling
not only during attach/detach
On 09/02/2015 02:09 PM, Arend van Spriel wrote:
On 09/02/2015 03:19 AM, Luis R. Rodriguez wrote:
On Mon, Aug 31, 2015 at 10:21:34PM +0800, Ming Lei wrote:
On Sun, Aug 30, 2015 at 4:25 PM, Arend van Spriel
wrote:
Does this mean a built-in driver can not get firmware from initramfs or
built in
On Wed, Sep 02, 2015 at 10:55:20AM +0100, Marc Zyngier wrote:
> On 02/09/15 10:33, Qais Yousef wrote:
> > On 08/28/2015 03:22 PM, Thomas Gleixner wrote:
> >> On Fri, 28 Aug 2015, Qais Yousef wrote:
> >>> Thanks a lot for the detailed explanation. I wasn't looking for a quick
> >>> and
> >>> dirty
On 09/02/2015 03:19 AM, Luis R. Rodriguez wrote:
On Mon, Aug 31, 2015 at 10:21:34PM +0800, Ming Lei wrote:
On Sun, Aug 30, 2015 at 4:25 PM, Arend van Spriel wrote:
Does this mean a built-in driver can not get firmware from initramfs or
built in the kernel early. Seems a bit too aggressive.
发自我的 iPhone
> 在 2015年9月2日，下午7:54，Jiri Olsa 写道：
>
>> On Wed, Sep 02, 2015 at 02:53:58PM +0800, Wangnan (F) wrote:
>> Sorry, forget to CC kernel mailing list...
>>
>>> On 2015/9/2 14:49, Wang Nan wrote:
>>> If parse_events__scanner() collects no entry, perf_evlist__last(evlist)
>>> is invalid.
On Wednesday 02 September 2015, Tomi Valkeinen wrote:
> On 24/08/15 22:37, Ondrej Zary wrote:
> > i2c-algo-bit allows I2C adapters without SCL read capability to work but
> > fb_ddc_read fails to work on them.
> >
> > Fix fb_ddc_read to work with I2C adapters not capable of reading SCL.
> >
> >
On Wednesday 02 September 2015, Tomi Valkeinen wrote:
> Hi,
>
> On 24/08/15 22:37, Ondrej Zary wrote:
> > Add DDC support for Trident cards.
> >
> > Tested on TGUI9440, TGUI9680, 3DImage 9750, Blade3D 9880 and Blade XP.
> >
> > Signed-off-by: Ondrej Zary
> > ---
> > drivers/video/fbdev/Kconfig
On some platforms, there is occasional panic triggered when trying to
resume from hibernation, a typical panic looks like:
BUG: unable to handle kernel paging request at 880085894000
IP: [] load_image_lzo+0x8c2/0xe70
This is because e820 map has been changed by BIOS before/after
hibernation,
On 01/09/15 16:55, Sudip Mukherjee wrote:
> On Tue, Sep 01, 2015 at 04:27:24PM +0300, Tomi Valkeinen wrote:
>>
>>
>> On 18/07/15 07:08, Sudip Mukherjee wrote:
>>> Now since all cleanups are done and the code is ready to be merged lets
>>> move it out of staging into fbdev location.
>>
>> Have
On Tue, 1 Sep 2015 15:39:45 -0400
Austin S Hemmelgarn wrote:
> On 2015-09-01 06:29, Albino B Neto wrote:
> > 2015-08-31 19:31 GMT-03:00 Raymond Jennings :
> >> I think also that we should remove the ext2 driver before we remove the
> >> ext3
> >> driver.
> >
> > Yes. It is logical to remove the
On 08/31/2015 06:12 PM, Boris Ostrovsky wrote:
On 08/20/2015 02:16 PM, Juergen Groß wrote:
On 08/18/2015 05:55 PM, Dario Faggioli wrote:
Hey everyone,
So, as a followup of what we were discussing in this thread:
[Xen-devel] PV-vNUMA issue: topology is misinterpreted by the guest
On Wed, Sep 02, 2015 at 02:53:58PM +0800, Wangnan (F) wrote:
> Sorry, forget to CC kernel mailing list...
>
> On 2015/9/2 14:49, Wang Nan wrote:
> >If parse_events__scanner() collects no entry, perf_evlist__last(evlist)
> >is invalid.
> >
> >Although it shouldn't happen at this point, before
On 02/09/15 11:48, Qais Yousef wrote:
> On 09/02/2015 10:55 AM, Marc Zyngier wrote:
>> On 02/09/15 10:33, Qais Yousef wrote:
>>> On 08/28/2015 03:22 PM, Thomas Gleixner wrote:
On Fri, 28 Aug 2015, Qais Yousef wrote:
> Thanks a lot for the detailed explanation. I wasn't looking for a quick
On Wednesday 02 September 2015 01:56 PM, Jisheng Zhang wrote:
On Wed, 2 Sep 2015 13:49:53 +0530
Vaibhav Hiremath wrote:
On Wednesday 02 September 2015 12:34 PM, Jisheng Zhang wrote:
On Wed, 2 Sep 2015 01:02:17 +0530
Vaibhav Hiremath wrote:
Currently, the
On Wed, 2015-09-02 at 13:35 +0200, Martin van Es wrote:
> On Wed, Sep 2, 2015 at 12:50 PM, Mike Galbraith
> wrote:
> > On Wed, 2015-09-02 at 11:38 +0200, Martin van Es wrote:
> >> Hi,
> >>
> >> I recently compiled 4.2.0 based on my previous 4.1.6 config (make
> >> oldconfig).
> >> On 4.1.6 all
On 31 August 2015 at 20:24, Heiko Stuebner wrote:
> From: Douglas Anderson
>
> This adds logic to the MMC core to set VQMMC. This is expected to be
> called by MMC drivers like dw_mmc as part of (or instead of) their
> start_signal_voltage_switch() callback.
>
> A few notes:
>
> * When setting
On Wed, Sep 2, 2015 at 12:50 PM, Mike Galbraith
wrote:
> On Wed, 2015-09-02 at 11:38 +0200, Martin van Es wrote:
>> Hi,
>>
>> I recently compiled 4.2.0 based on my previous 4.1.6 config (make oldconfig).
>> On 4.1.6 all cores are equally scheduled.
>
> Do you have CONFIG_NO_HZ_FULL_ALL enabled?
On 24/08/15 22:37, Ondrej Zary wrote:
> i2c-algo-bit allows I2C adapters without SCL read capability to work but
> fb_ddc_read fails to work on them.
>
> Fix fb_ddc_read to work with I2C adapters not capable of reading SCL.
>
> Signed-off-by: Ondrej Zary
> Acked-by: Krzysztof Helt
> ---
>
Am 14.08.2015 um 12:08 schrieb Radim Krčmář:
> v3:
> * acked by Christian [1/5]
> * use ioctl argument directly (unsigned long as flags) [4/5]
> * precisely #ifdef arch-specific ioctls [5/5]
> v2:
> * move request_exits debug counter patch right after introduction of
>KVM_REQ_EXIT [3/5]
>
Hi,
On 24/08/15 22:37, Ondrej Zary wrote:
> Add DDC support for Trident cards.
>
> Tested on TGUI9440, TGUI9680, 3DImage 9750, Blade3D 9880 and Blade XP.
>
> Signed-off-by: Ondrej Zary
> ---
> drivers/video/fbdev/Kconfig |9 ++
> drivers/video/fbdev/tridentfb.c | 192
>
The functions gru_get_cb_exception_detail_str() and gru_abort() were
only called locally from that file. We can make them static.
Signed-off-by: Sudip Mukherjee
---
drivers/misc/sgi-gru/grukservices.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
On 10/08/15 17:31, Alexandre Belloni wrote:
> Definitions from linux/platform_data/atmel.h are not used, remove the
> include.
>
> Signed-off-by: Alexandre Belloni
> ---
> drivers/video/fbdev/atmel_lcdfb.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git
The member gid in struct gru_dump_chiplet_state_req is unsigned int. So
it can never be less than 0.
Signed-off-by: Sudip Mukherjee
---
drivers/misc/sgi-gru/grukdump.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/sgi-gru/grukdump.c
gru_alloc_gts() can fail and it can return ERR_PTR(errvalue). We should
not dereference it if it has returned error. And incase it has returned
error then just downgrade the write lock and exit.
Signed-off-by: Sudip Mukherjee
---
drivers/misc/sgi-gru/grukservices.c | 3 +++
1 file changed, 3
These variables were only assigned some value and were never used.
Signed-off-by: Sudip Mukherjee
---
I have removed the variables in the functions gru_dump_tfm() and
gru_dump_tgh() but it appeared that the intended logic might have been
something like:
bytes = GRU_NUM_TFM *
Hi,
as a reminder, the Kernel Recipes 2015 conference is scheduled at the
end of this month in Paris. Registrations opened yesterday but there
are still some places left. More about it here :
https://kernel-recipes.org/
Cheers,
Willy
--
To unsubscribe from this list: send the line
On Tue, Sep 01, 2015 at 11:56:06AM -0700, Tony Lindgren wrote:
> * Mark Brown [150901 11:40]:
> > That'd work. The other thing I was thinking we could do is to get
> > syscon to treat any excessively large address that gets passed in that
> > looks like an absolute address appropriately.
> Hmm
Hi!
While running KASAN on 4.2 with Trinity I got the following report:
==
BUG: KASan: use after free in page_cache_async_readahead+0x2cb/0x3f0
at addr 880034bf6690
Read of size 8 by task sshd/2571
Explicitly initialize ret to -EINVAL in regmap_raw_read to fix the
following compilation warning:
CC drivers/base/regmap/regmap.o
linux/drivers/base/regmap/regmap.c: In function ‘regmap_raw_read’:
linux/drivers/base/regmap/regmap.c:2174:6: warning: ‘ret’ may be used
uninitialized in this
On 09/02/2015 12:51 PM, Zhenzhong Duan wrote:
On some numa system, after dom0 up, we see below warning even if there are
enough pfn ranges could be used for remapping.
"Unable to find available pfn range, not remapping identity pages"
Fix it to avoid getting a memory region of zero size in
On 09/02/2015 06:54 PM, Markus Trippelsdorf wrote:
On 2015.09.02 at 18:27 +0800, Xiao Guangrong wrote:
On 09/02/2015 05:38 PM, Markus Trippelsdorf wrote:
On 2015.09.02 at 17:17 +0800, Xiao Guangrong wrote:
No. PAT is of course enabled and booting is successful sometimes even
with the
Any feedback is greatly appreciated.
Hi Matias,
After a reading of your code, that's a great idea.
I tried it with null_nvm and qemu-nvm. I have two questions
here.
Hi Yang, thanks for taking a look. I appreciate it.
(1), Why we name it lightnvm? IIUC, this framework
can work for
On 2015/9/2 18:34, Will Deacon wrote:
On Mon, Aug 31, 2015 at 09:16:28PM +0100, Arnaldo Carvalho de Melo wrote:
Em Sat, Aug 29, 2015 at 03:16:52AM +, He Kuang escreveu:
This patch implements arch_get_reg_info() for arm64 to enable
HAVE_BPF_PROLOGUE feature. For arm64, structure pt_regs
On 2015.09.02 at 18:27 +0800, Xiao Guangrong wrote:
>
>
> On 09/02/2015 05:38 PM, Markus Trippelsdorf wrote:
> > On 2015.09.02 at 17:17 +0800, Xiao Guangrong wrote:
> >>>
> >>> No. PAT is of course enabled and booting is successful sometimes even
> >>> with the BUG() in allback_mtrr_type(). I
Use "ti,pbias-omap2" compatible string which is specifically added
for OMAP2.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap2430.dtsi |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap2430.dtsi b/arch/arm/boot/dts/omap2430.dtsi
index
vsel_reg and enable_reg of the pbias regulator descriptor should actually
have the offset from syscon.
However after
"ARM: dts: : add minimal l4 bus layout with control module
support"
vsel_reg and enable_reg started to have the absolute address because
of address translation that happens due to
On some numa system, after dom0 up, we see below warning even if there are
enough pfn ranges could be used for remapping.
"Unable to find available pfn range, not remapping identity pages"
Fix it to avoid getting a memory region of zero size in xen_find_pfn_range.
Signed-off-by: Zhenzhong Duan
Use "ti,pbias-dra7" compatible string which is specifically added
for DRA7 SoCs.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/dra7.dtsi |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
index
On Wed, Sep 02, 2015 at 10:59:06AM +0100, Will Deacon wrote:
> Hi Paul,
>
> On Tue, Sep 01, 2015 at 10:45:40PM +0100, Paul E. McKenney wrote:
> > On Tue, Sep 01, 2015 at 08:00:27PM +0100, Will Deacon wrote:
> > > On Fri, Aug 28, 2015 at 04:39:21PM +0100, Peter Zijlstra wrote:
> > > > Yes, the
Use "ti,pbias-omap4" compatible string which is specifically added
for OMAP4.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap4.dtsi |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index
Use "ti,pbias-omap3" compatible string which is specifically added
for OMAP3.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap3.dtsi |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
index
On Wed, 2015-09-02 at 11:38 +0200, Martin van Es wrote:
> Hi,
>
> I recently compiled 4.2.0 based on my previous 4.1.6 config (make oldconfig).
> On 4.1.6 all cores are equally scheduled.
Do you have CONFIG_NO_HZ_FULL_ALL enabled?
-Mike
--
To unsubscribe from this list: send the line
On 09/02/2015 10:55 AM, Marc Zyngier wrote:
On 02/09/15 10:33, Qais Yousef wrote:
On 08/28/2015 03:22 PM, Thomas Gleixner wrote:
On Fri, 28 Aug 2015, Qais Yousef wrote:
Thanks a lot for the detailed explanation. I wasn't looking for a quick and
dirty solution but my view of the problem is
+
+/* register with device with a supported BM */
+list_for_each_entry(bt, _bms, list) {
+ret = bt->register_bm(dev);
+if (ret < 0)
+goto err; /* initialization failed */
+if (ret > 0) {
+dev->bm = bt;
+break; /* successfully
Use "ti,pbias-omap5" compatible string which is specifically added
for OMAP5.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap5.dtsi |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index
Add separate compatible strings for every platform and populate the
pbias register offset in the driver data.
This helps avoid depending on the dt for pbias register offset.
Also update the dt binding documentation with the new compatible
strings.
Suggested-by: Tony Lindgren
Signed-off-by:
We were checking rdev->supply for NULL after dereferencing it. Lets
check for rdev->supply along with _regulator_is_enabled() and call
regulator_enable() only if rdev->supply is not NULL.
Signed-off-by: Sudip Mukherjee
---
drivers/regulator/core.c | 5 ++---
1 file changed, 2 insertions(+), 3
On Wed, Sep 02, 2015 at 08:23:29AM +0200, Robert Jarzmik wrote:
> On old ARM chips, unaligned accesses to memory are not trapped and
> fixed. On module load, symbols are relocated, and the relocation of
> __bug_table symbols is done on a u32 basis. Yet the section is not
> aligned to a multiple
On Fri, Aug 28, 2015 at 12:49:47PM +0100, Horia Geantă wrote:
> This will allow device drivers to consistently use io{read,write}XXbe
> macros also for 64-bit accesses.
>
> Signed-off-by: Alex Porosanu
> Signed-off-by: Horia Geantă
> ---
> arch/arm64/include/asm/io.h | 4 +++-
> 1 file
On Mon, Aug 31, 2015 at 09:16:28PM +0100, Arnaldo Carvalho de Melo wrote:
> Em Sat, Aug 29, 2015 at 03:16:52AM +, He Kuang escreveu:
> > This patch implements arch_get_reg_info() for arm64 to enable
> > HAVE_BPF_PROLOGUE feature. For arm64, structure pt_regs is not composed
> > by fields of
On 09/02/2015 05:38 PM, Markus Trippelsdorf wrote:
On 2015.09.02 at 17:17 +0800, Xiao Guangrong wrote:
No. PAT is of course enabled and booting is successful sometimes even
with the BUG() in allback_mtrr_type(). I suspect a setup (timing) issue.
Thanks for your confirmation.
markus@x4
> From: Wangnan (F) [mailto:wangn...@huawei.com]
>
> Sorry, forget to CC kernel mailing list...
>
> On 2015/9/2 14:49, Wang Nan wrote:
> > If parse_events__scanner() collects no entry, perf_evlist__last(evlist)
> > is invalid.
> >
> > Although it shouldn't happen at this point, before calling
>
On 09/02/2015 12:47 PM, Kirill A. Shutemov wrote:
<>
>
> I don't insist on applying the patch. And I worry about false-positives.
>
Thanks, yes
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
On 09/02/2015 08:17 AM, Dave Chinner wrote:
> On Tue, Sep 01, 2015 at 09:19:45PM -0600, Ross Zwisler wrote:
>> On Wed, Sep 02, 2015 at 08:21:20AM +1000, Dave Chinner wrote:
>>> Which means applications that should "just work" without
>>> modification on DAX are now subtly broken and don't actually
> From: Ingo Molnar [mailto:mingo.kernel@gmail.com] On Behalf Of Ingo Molnar
>
> > > sure, np you can use my ack
> >
> > I'm also OK for this patch. I just concern that is OK for Adrian too?
> > Since this ensures all the copied code should be dead copy (not modified
> > anymore),
> > if we
On Sun, Aug 30, 2015 at 07:19:59AM +0100, yalin wang wrote:
> This patch add kc_offset_to_vaddr() and kc_vaddr_to_offset(),
> the default version doesn't work on arm64, because arm64 kernel address
> is below the PAGE_OFFSET, like module address and vmemmap address are
> all below PAGE_OFFSET
On 2 September 2015 at 11:48, Ard Biesheuvel wrote:
> On 13 August 2015 at 19:29, Catalin Marinas wrote:
>> On Thu, Aug 13, 2015 at 03:45:07PM +0100, Suzuki K. Poulose wrote:
>>> On 13/08/15 13:28, Steve Capper wrote:
>>> >On 13 August 2015 at 12:34, Suzuki K. Poulose
>>> >wrote:
>>> >>
Some of the data structures (like response UPIU) and/or its elements
(unused fields) should be cleared before sending out the respective
command to UFS device.
This change clears the UPIU response data structure for query commands
and NOP command before sending out the command. We also initialize
According to UFS device specification REQUEST_SENSE command can
only report back up to 18 bytes of data.
Signed-off-by: Gilad Broner
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/ufshcd.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git
A race condition appear to exist between request completion when
scsi_done() is called to end the request and set the tag back to
-1 (at blk_queue_end_tag() scsi_end_request), and scsi layer error
handling which aborts the command and reuses it to request sense
data. Sending the request sense is
On Wed, Aug 26, 2015 at 04:10:34PM +0100, Chris Metcalf wrote:
> On 08/26/2015 06:36 AM, Will Deacon wrote:
> > On Tue, Aug 25, 2015 at 08:55:52PM +0100, Chris Metcalf wrote:
> >> diff --git a/arch/arm64/kernel/ptrace.c b/arch/arm64/kernel/ptrace.c
> >> index d882b833dbdb..e3d83a12f3cf 100644
> >>
UFS flag query requests may fail sometimes due to timeouts etc.
Add a wrapper function to retry up to 10 times in case of such
failure, similar to retries being made for attribute queries.
Signed-off-by: Gilad Broner
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/ufshcd.c | 63
The dme_peer get/set attribute commands are prone to errors, therefore
we add three retries for the UIC command sending.
Error code returned from ufshcd_send_uic_cmd() is checked, and unless
it was successful or the retries have finished, another command will be
sent.
Signed-off-by: Lee Susman
DME commands such as Hibern8 enter/exit and gear switch generate 2
completion interrupts, one for confirmation that command is received
by local UniPro and 2nd one is the final confirmation after communication
with remote UniPro. Currently both of these completions are registered
as interrupt
fDeviceInit query response time for some devices is too long that default
query request timeout of 100ms may not be enough. Experiments show that
fDeviceInit response sometimes takes 500ms so to be on safer side this
change sets the timeout to 600ms. Without this change, we might
unnecessarily
Hibern8 exit can be called from 3 different context:
- ufshcd_hibern8_exit_work
- ufshcd_ungate_work
- runtime/system resume
If hibern8 exit fails for some reason then we try to bring the link to
active state by link startup but this recovery mechanism results into
deadlock or errors
Add a write memory barrier to make sure descriptors prepared are actually
written to memory before ringing the doorbell. We have also added the
write memory barrier after ringing the doorbell register so that
controller sees the new request immediately.
Signed-off-by: Gilad Broner
Signed-off-by:
Sometimes queries from the device might return a failure so it is
recommended to retry sending the query, before giving up.
This change adds a wrapper to retry sending a query attribute,
in cases where we need to wait longer, before we continue,
or before reporting a failure.
Signed-off-by: Yaniv
If hibern8 enter command fails then UFS link state may be unknown which
may result into timeout of all the commands issued after failure.
This change does 2 things (for pre-defined number of retry counts) after
hibern8 enter failure:
1. Recovers the UFS link to active state
2. If link is
If device raises the exception event in the response to the commands
sent during the runtime/system PM callbacks, exception event handler
might run in parallel with PM callbacks and may see unclocked register
accesses. This change fixes this issue by not scheduling the exception
event handler
Performing several writes to UFS host controller registers has
no gurrantee of ordering, so we must make sure register writes
to setup request list base address etc. are performed before the
run/stop register is enabled.
In addition, when setting up a task request, we must make sure
the updating
When sending a query to the device returns with a timeout error,
we clear the corresponding bit in the DOORBELL register but
we don't clear the outstanding_request field as we should.
This patch fixes this bug.
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/ufshcd.c | 22
Important:
This serie of 15 small patches should be pushed after the series of 8 patches
"Fix error message and present UFS variant probe"
V3:
removed specific calls to wmb() since they are redundant.
V2:
a few minor changes
V1:
This serie of 15 small patches should be pushed after the series
Clear the UFS data structures before sending new request.
The SCSI command is sent to the device within the UFS UPIU request.
As part of the transfer UPIU preparation, the SCSI command is copied
to the UPIU structure according to the SCSI command size.
As different SCSI commands differ in size
On 02/09/15 10:55, Ard Biesheuvel wrote:
On 13 August 2015 at 13:33, Suzuki K. Poulose wrote:
From: "Suzuki K. Poulose"
Patches 1-7 cleans up the kernel page size handling code.
Patches 8-11 Fixes some issues with the KVM bits, mainly the fake PGD
handling code.
Patch 12
On Thu, Aug 27, 2015 at 06:56:49PM +0100, Mathieu Desnoyers wrote:
> arm64 sys_membarrier number is already wired for arm64 through
> asm-generic/unistd.h, but needs to be allocated separately for
> the 32-bit compability layer of arm64.
>
> [ Untested on this architecture. To try it out: fetch
On 09/02/2015 06:19 AM, Ross Zwisler wrote:
> On Wed, Sep 02, 2015 at 08:21:20AM +1000, Dave Chinner wrote:
>> Which means applications that should "just work" without
>> modification on DAX are now subtly broken and don't actually
>> guarantee data is safe after a crash. That's a pretty nasty
>>
On Wed 2015-06-17 21:01:55, Andreas Mohr wrote:
> Hi,
>
> [unable to set In-Reply-To: since lkml.org "headers" view remains broken...]
>
> > Hibernation works well here, including X. (Which has small glitch with
> > mouse cursor being corrupted until it is changed by application).
>
> I
On Wed, Aug 19, 2015 at 08:58:24AM +0530, Pratyush Anand wrote:
> /sys/class/watchdog/watchdogn/device/modalias can help to identify the
> driver/module for a given watchdog node. However, many wdt devices does not
> set
> its parent and so, we do not see an entry for device in sysfs for such
>
Thierry,
在 2015/9/2 16:34, Thierry Reding 写道:
On Wed, Sep 02, 2015 at 10:06:36AM +0800, Yakir Yang wrote:
在 09/02/2015 05:00 AM, Heiko Stuebner 写道:
Am Dienstag, 1. September 2015, 14:01:48 schrieb Yakir Yang:
[...]
diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
Move dl_time_before static definition in include/linux/sched/deadline.h
so that it can be used by different parties without being re-defined.
Cc: Ingo Molnar
Cc: Peter Zijlstra
Reported-by: Luca Abeni
Signed-off-by: Juri Lelli
---
include/linux/sched/deadline.h | 5 +
Hi all,
while trying to come up with 01/04, I collected the following set of fixes.
Patches 02-04/04 are simple refactoring of code and clean-ups.
Patch 01/04 is instead my attempt to fix a problem highlighted some time
back by Wanpeng Li regarding hotplug and the way SCHED_DEADLINE keeps
track
On 2 September 2015 at 11:42, Suzuki K. Poulose wrote:
> On 02/09/15 10:38, Ard Biesheuvel wrote:
>>
>> On 13 August 2015 at 13:33, Suzuki K. Poulose
>> wrote:
>>>
>>> From: "Suzuki K. Poulose"
>>>
>>> We use section maps with 4K page size to create the
>>> swapper/idmaps. So far we have used
Hotplug operations are destructive w.r.t data associated with cpuset;
in this case we care about root_domains. SCHED_DEADLINE puts bandwidth
information regarding admitted tasks on root_domains, information that
is gone when an hotplug operation happens. Also, it is not currently
possible to tell
The return value of (do_)balance_runtime() is not consumed by anybody.
Make them return void.
Cc: Ingo Molnar
Cc: Peter Zijlstra
Signed-off-by: Juri Lelli
---
kernel/sched/rt.c | 22 ++
1 file changed, 6 insertions(+), 16 deletions(-)
diff --git a/kernel/sched/rt.c
rt_mutex_waiter_less() check of tasks deadlines is open coded. Since this
is subject to wraparound issues, make it use the correct helper.
Cc: Ingo Molnar
Cc: Peter Zijlstra
Reported-by: Luca Abeni
Signed-off-by: Juri Lelli
---
kernel/locking/rtmutex.c | 3 ++-
1 file changed, 2
Hi Paul,
On Tue, Sep 01, 2015 at 10:45:40PM +0100, Paul E. McKenney wrote:
> On Tue, Sep 01, 2015 at 08:00:27PM +0100, Will Deacon wrote:
> > On Fri, Aug 28, 2015 at 04:39:21PM +0100, Peter Zijlstra wrote:
> > > Yes, the difference between RCpc and RCsc is in the meaning of RELEASE +
> > >
501 - 600 of 1480 matches
Mail list logo
