On Fri, Mar 11, 2016 at 06:42:36PM +0300, Alexey Brodkin wrote:
> ARC PGU could be found on some development boards from Synopsys.
> This is a simple byte streamer that reads data from a framebuffer
> and sends data to the single encoder.
>
> Signed-off-by: Alexey Brodkin
> Cc: David Airlie
> Cc
Hi Krzysztof,
On 2016년 03월 14일 15:42, Krzysztof Kozlowski wrote:
> On 14.03.2016 11:04, Chanwoo Choi wrote:
>> This patch adds the support for Device Tree source for Samsung ARTIK5
>> module[1]
>> based on Exynos3250 SoC. The ARTIK5 module includes the follwoing devices:
>> - Application Processo
On 14.03.2016 11:04, Chanwoo Choi wrote:
> From: Jaehoon Chung
>
> This patch adds MSHC (Mobile Storage Host Controller) dt node for Exynos3250
> SoC. MSHC is an interface between the system and the eMMC device.
>
> Signed-off-by: Jaehoon Chung
> Signed-off-by: Andi Shyti
> Signed-off-by: Chan
Hi,
Rajesh Bhagat writes:
> [ text/plain ]
> Some freescale QorIQ platforms require to disable receiver detection
> in P3 for correct detection of USB devices. If GUSB3PIPECTL(DISRXDETINP3)
> is set, Core will change PHY power state to P2 and then perform receiver
> detection. After receiver de
On 13 March 2016 at 20:50, Andrew Pinski wrote:
> On many cores, udiv with a large value is slow, expand instead
> the division out to be what GCC would have generated for the
> divide by 1000.
>
> On ThunderX, the speeds up gettimeofday by 5%.
>
> Signed-off-by: Andrew Pinski
> ---
> arch/arm64
On Mon, Mar 14, 2016 at 09:12:28AM +0800, Yankejian (Hackim Yim) wrote:
>
>
> On 2016/3/12 18:43, Leon Romanovsky wrote:
> > On Fri, Mar 11, 2016 at 06:37:10PM +0800, Lijun Ou wrote:
> >> It added hns_dsaf_roce_reset routine for roce driver.
> >> RoCE is a feature of hns.
> >> In hip06 SOC, in ro
On Thu, Mar 03, 2016 at 11:46:01PM +0900, Sergey Senozhatsky wrote:
> zsmalloc knows the watermark after which classes are considered
> to be ->huge -- every object stored consumes the entire zspage (which
> consist of a single order-0 page). On x86_64, PAGE_SHIFT 12 box, the
> first non-huge class
Hi Parav Pandit, thanks your reviewing.
On 2016/3/4 17:37, Parav Pandit wrote:
> On Fri, Mar 4, 2016 at 2:11 PM, Wei Hu(Xavier)
> wrote:
>> +
>> +int hns_roce_register_device(struct hns_roce_dev *hr_dev)
>> +{
>> + int ret;
>> + struct hns_roce_ib_iboe *iboe = NULL;
>> + struct
On Fri, Mar 11, 2016 at 06:07:40PM +0100, Vlastimil Babka wrote:
> On 03/11/2016 04:00 PM, Joonsoo Kim wrote:
> > 2016-03-09 10:23 GMT+09:00 Leizhen (ThunderTown)
> > :
> >>
> >> Hi, Joonsoo:
> >> This new patch worked well. Do you plan to upstream it in the near
> >> furture?
> >
> > Of
Hi all,
To make sure I wasn't crazy, I installed a mainline kernel on my x86 laptop.
It also doesn't work there, but I do get a far more detailed set of
backtraces, which I've added below. It also means it's not powerpc
specific, which should help in debugging it.
Regards,
Daniel
[ 118.453138]
On 03/11/2016 05:44 PM, David Miller wrote:
> From: Andrzej Hajda
> Date: Fri, 11 Mar 2016 07:51:15 +0100
>
>> Function skb_splice_bits can return negative values, its result should
>> be assigned to signed variable to allow correct error checking.
>>
>> The problem has been detected using patch
>
From: Ma Jun
For mbigen module, there is a special case that more than one mbigen
device nodes use the same reg definition in DTS when these devices
exist in the same mbigen hardware module.
To fix the mbigen IO remap problem, the mbigen node definition and
structure are changed based on Mark Ru
From: Ma Jun
To fix the IO remap problem, change the mbigen driver based on the
new mbigen node definition.
Signed-off-by: Ma Jun
---
drivers/irqchip/irq-mbigen.c | 30 +-
1 files changed, 21 insertions(+), 9 deletions(-)
diff --git a/drivers/irqchip/irq-mbigen.c
From: Ma Jun
This patch set is used to fix the problem of remap a set of registers
repeatedly.
Changes in v2:
--- Change the mbigen device node definition
--- Change the mbigen driver based on the new mbigen dts structure.
Ma Jun (2):
Irq/mbigen:Change the mbigen node definition in dt binding
On 14.03.2016 11:04, Chanwoo Choi wrote:
> This patch adds the support for Device Tree source for Samsung ARTIK5
> module[1]
> based on Exynos3250 SoC. The ARTIK5 module includes the follwoing devices:
> - Application Processor (Samsung Exynos3250)
> - WiFi/BT Combo chip (Broadcom4354)
> - PMIC (S
Hi all,
Changes since 20160311:
The vfs tree gained a conflict against Linus' tree. I also applied a
patch for a known runtime bug.
The tip tree gained a conflict against the mips tree.
The aio tree still had a build failure so I removed several commits
from it. It also gained a conflict again
Hi Marcel,
Do you have any comments for this patch?
Please let us know if you have any more suggestions for the improvements.
> From: Amitkumar Karwar [mailto:akar...@marvell.com]
> Sent: Thursday, March 03, 2016 5:27 PM
> To: linux-blueto...@vger.kernel.org
> Cc: Cathy Luo; linux-kernel@vger.ker
On Thu, Mar 03, 2016 at 11:46:00PM +0900, Sergey Senozhatsky wrote:
> Do not register shrinker compaction callbacks anymore, since
> now we shedule class compaction work each time its fragmentation
> value goes above the watermark.
I suggested to remove shrinker compaction but while I review your
Hi Andy,
2016-03-14 13:44 GMT+09:00 Andy Lutomirski :
> On Sun, Mar 13, 2016 at 9:36 PM, Masahiro Yamada
> wrote:
>> 2016-03-14 13:28 GMT+09:00 Andy Lutomirski :
>>> On Sun, Mar 13, 2016 at 9:08 PM, Masahiro Yamada
>>> wrote:
Hi Andy
2016-03-14 9:39 GMT+09:00 Andy Lutomirski
On 14.03.2016 11:04, Chanwoo Choi wrote:
> This patch adds the MSHC2 (Mobile Storage Host Controller) Device Tree node
> for
> Exynos3250 SoC.
>
> Cc: Kukjin Kim
> Cc: Krzysztof Kozlowski
> Signed-off-by: Chanwoo Choi
> Reviewed-by: Krzysztof Kozlowski
> ---
> arch/arm/boot/dts/exynos3250-pi
Hi
On 03/07/2016 10:42 PM, Paolo Bonzini wrote:
On 04/03/2016 21:46, Suravee Suthikulpanit wrote:
>
>+static void svm_vcpu_blocking(struct kvm_vcpu *vcpu)
>+{
>+ avic_set_running(vcpu, false);
>+}
>+
>+static void svm_vcpu_unblocking(struct kvm_vcpu *vcpu)
>+{
>+ avic_set_running(vcpu, tru
Sudip Mukherjee writes:
> From: Jia-Ju Bai
>
> The memory allocated by kzalloc in b43_bus_dev_ssb_init and
> b43_bus_dev_bcma_init is not freed.
> This patch fixes the bug by adding kfree in b43_ssb_remove,
> b43_bcma_remove and error handling code of b43_bcma_probe.
>
> Thanks Michael for his s
Hey Sergey,
Sorry for late review.
On Thu, Mar 03, 2016 at 11:45:59PM +0900, Sergey Senozhatsky wrote:
> zsmalloc classes are known to be affected by internal fragmentation.
>
> For example, /sys/kernel/debug/zsmalloc/zramX/classes
> class size almost_full almost_empty obj_allocated obj_used
Hi
On 03/07/2016 10:39 PM, Paolo Bonzini wrote:
+ svm_x86_ops.update_cr8_intercept = NULL;
>} else {
>svm_x86_ops.deliver_posted_interrupt = NULL;
>}
>@@ -1116,7 +1119,8 @@ static void init_vmcb(struct vcpu_svm *svm)
>set_cr_intercept(svm, INTERCEPT_CR0_WRIT
On 14.03.2016 10:12, Chanwoo Choi wrote:
> This patch adds initial pin configuration using pinctrl subsystem
> to reduce leakage power-consumption of gpio pins in normal state.
> All pins included in this patch are NC (not connected) pin.
>
> Cc: Kukjin Kim
> Cc: Krzysztof Kozlowski
> Signed-off
In MT8173, Normally the first 1GB PA is for the HW SRAM and Regs,
so the PA will be 33bits if the dram size is 4GB. We have a
"DRAM 4GB mode" toggle bit for this. If it's enabled, from CPU's
point of view, the dram PA will be from 0x1_~0x1_.
In short descriptor, the pagetable descr
This patch add 4GB mode support for m4u.
Signed-off-by: Yong Wu
---
drivers/iommu/mtk_iommu.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/drivers/iommu/mtk_iommu.c b/drivers/iommu/mtk_iommu.c
index 721ffdb..b97de21 100644
--- a/drivers/iommu/mtk_iommu.c
++
This patch-set add MTK 4GB mode support on the Short-Descriptor.
Normally, the memory map in mt8173 looks like below:
Physical addr
| 1st GB |-> HW SRAM and Regs
|
| 2nd GB |-> Dram 1st GB
|
| 3rd GB |-> Dram 2nd GB
|
| 4th GB |-> Dram 3rd GB
|
This patch adds the get_direction to support the gpio
interface.
The gpio direction is not used on rockchip platform when use the gpio
debugfs.
Tested on kylin board. (RK3036 SoCs)
The repro steps:
$/sys/class/gpio/
echo 53 > export
$/sys/class/gpio/gpio53# cat direction
in
In general, the gpio53
在 2016年03月14日 13:44, Caesar Wang 写道:
This patch adds the get_direction to support the gpio
interface.
the gpio direction is not used on rockchip platform when use the gpio
debugfs.
Tested on kylin board. (RK3036 SoCs)
The repro steps:
$/sys/class/gpio/
echo 53 > export
$/sys/class/gpio/gpio53
The header file asm/sizes.h is unnecessary.
And it can also be compiled under X86 arch after the removal.
Signed-off-by: Wang Hongcheng
---
drivers/mmc/host/mmci.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/mmc/host/mmci.c b/drivers/mmc/host/mmci.c
index fb26674..e5e5441 100644
-
This patch adds the get_direction to support the gpio
interface.
the gpio direction is not used on rockchip platform when use the gpio
debugfs.
Tested on kylin board. (RK3036 SoCs)
The repro steps:
$/sys/class/gpio/
echo 53 > export
$/sys/class/gpio/gpio53# cat direction
in
In general, the gpio53
Al Viro writes:
> On Mon, Mar 14, 2016 at 08:48:26AM +0800, kernel test robot wrote:
>> FYI, we noticed the below changes on
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.lookups
>> commit fda89e65743179d09e55bc6c265d06fa5efa8803 ("namei: untanlge
>> lookup_fast()")
>
Utilization contributions to cfs_rq->avg.util_avg are scaled for both
microarchitecture-invariance as well as frequency-invariance. This means
that any given utilization contribution will be scaled against the
current cpu capacity (cpu frequency). Contributions from long running
tasks, whose utiliz
I'm happy that scheduler-driven cpu frequency selection is getting some
attention. Rafael's recent schedutil governor is a step in the right direction.
This series builds on top of Rafael's schedutil governor, bringing it to parity
with some of the features in the schedfreq series posted by Steve[0
With the addition of the global cfs capacity margin helpers in patch,
"sched/cpufreq: new cfs capacity margin helpers", we can now export
sysfs tunables from the schedutil governor. This allows privileged users
to tune the value more easily.
The margin value is global to cfs, not per-policy. As su
On 03/07/2016 10:36 PM, Paolo Bonzini wrote:
On 04/03/2016 21:46, Suravee Suthikulpanit wrote:
+static void svm_deliver_avic_intr(struct kvm_vcpu *vcpu, int vec)
+{
+ struct vcpu_svm *svm = to_svm(vcpu);
+
+ kvm_lapic_set_vector(vec, avic_get_bk_page_entry(svm, APIC_IRR));
+
+
From: Dietmar Eggemann
Implements cpufreq_scale_freq_capacity() to provide the scheduler with a
frequency scaling correction factor for more accurate load-tracking.
The factor is:
current_freq(cpu) << SCHED_CAPACITY_SHIFT / max_freq(cpu)
In fact, freq_scale should be a struct cpufreq_p
Introduce helper functions that allow cpufreq governors to change the
value of the capacity margin applied to the cfs_rq->avg.util_avg signal.
This allows for run-time tuning of the margin.
A follow-up patch will update the schedutil governor to use these
helpers.
Signed-off-by: Michael Turquette
cpufreq_update_util() accepts a single utilization value which does not
account for multiple utilization contributions from the cfs, rt & dl
scheduler classes. Begin fixing this by adding a sched_class argument to
cpufreq_update_util(), all of its call sites and the governor-specific
hooks in inte
Hi,
On 03/12/2016 08:22 PM, Peter Zijlstra wrote:
On Tue, Feb 23, 2016 at 08:12:36AM -0600, Suravee Suthikulpanit wrote:
From: Suravee Suthikulpanit
First, this patch move arch/x86/events/amd/iommu.h to
arch/x86/include/asm/perf/amd/iommu.h so that we easily include
it in both perf-amd-iommu
arch_scale_freq_capacity is weird. It specifies an arch hook for an
implementation that could easily vary within an architecture or even a
chip family.
This patch helps to mitigate this weirdness by defaulting to the
cpufreq-provided implementation, which should work for all cases where
CONFIG_CPU
cpufreq_trigger_update() was introduced in "cpufreq: Rework the
scheduler hooks for triggering updates"[0]. Consensus is that this
helper is not needed and removing it will aid in experimenting with
deadline and rt capacity requests.
Instead of reverting the above patch, which includes useful rena
Patch, "sched/cpufreq: pass sched class into cpufreq_update_util" made
it possible for calls of cpufreq_update_util() to specify scheduler
class, particularly cfs, rt & dl.
Update the schedutil governor to store these individual utilizations per
cpu and sum them to create a total utilization contr
On Sun, Mar 13, 2016 at 9:31 PM, Brown, Len wrote:
>> By BIOS (1.2.3 on a Dell XPS 13 9350) seems to want to enable C1E
>> auto-promotion (ugh!), which results in this difference across
>> suspend/resume according to turbostat:
>>
>> -cpu3: MSR_IA32_POWER_CTL: 0x0024005d (C1E auto-promotion: DISab
On Sun, 13 Mar 2016, Joe Perches wrote:
> Loggng messages that emit function names have many different forms.
> Perhaps it'd be better for logging consistency and grep ease to
> exclusively use "%s:"
>
> As well, function tracing logging uses are generally unnecessary given
> the kernel's functio
From: Alexander Duyck
Date: Fri, 11 Mar 2016 14:05:28 -0800
> This patch series is meant to address the differences that exist between
> IPv4 and IPv6 in terms of checksum calculation. Specifically the IPv6
> function csum_ipv6_magic treated length as a value that could be greater
> than 64K, wh
We used to have ptmx be owned by the inner uid and gid 0. Change
this: if the owner and group are both mapped but are not both 0,
then use the owner instead.
For container-style namespaces (LXC, etc), this should have no
effect -- UID 0 is will either be the owner or will be unmapped.
The import
On Sat, Mar 12, 2016 at 11:09:36AM +0800, xuyiping wrote:
>
>
> On 2016/3/11 15:30, Minchan Kim wrote:
> >For migration, we need to create sub-page chain of zspage
> >dynamically so this patch factors it out from alloc_zspage.
> >
> >As a minor refactoring, it makes OBJ_ALLOCATED_TAG assign
> >mo
Hello Rui,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal linus
to receive Thermal-SoC Management updates for v4.6-rc1 with top-most
61f846f37354fd294f3172845d9fec2c03f60a45:
thermal: doc: Add details of
devm_thermal_zone_of_sensor_{register,unre
Hello,
this series adds two core variant header sets for test_mmuhifi_c3 and
test_kc705_hifi used in sample configurations for SMP and audio respectively.
Max Filippov (1):
xtensa: add test_kc705_hifi variant
Piet Delaney (1):
xtensa: add Three Core HiFi-2 MX Variant.
.../test_kc705_hifi/i
From: Piet Delaney
This variant has coherent cache, is equipped with interrupt distributor
and is capable of running SMP linux.
Signed-off-by: Piet Delaney
Signed-off-by: Max Filippov
---
.../test_mmuhifi_c3/include/variant/core.h | 384 +
.../test_mmuhifi_c3/inclu
This variant has HiFi3 coprocessor and is used in sample audio-enabled
configuration.
Signed-off-by: Max Filippov
---
.../test_kc705_hifi/include/variant/core.h | 532 +
.../test_kc705_hifi/include/variant/tie-asm.h | 329 +
.../variants/test_kc705_hi
On Sat, Mar 12, 2016 at 09:44:48AM +0800, xuyiping wrote:
>
>
> On 2016/3/11 15:30, Minchan Kim wrote:
> >Every zspage in a size_class has same number of max objects so
> >we could move it to a size_class.
> >
> >Signed-off-by: Minchan Kim
> >---
> > mm/zsmalloc.c | 29 ++---
So this is later on a Sunday than my usual schedule, because I just
couldn't make up my mind whether I should do another rc8 or not, and
kept just waffling about it. In the end, I obviously decided not to,
but it could have gone either way.
We did have one nasty regression that got fixed yesterday
For the NCR5380.c core driver, these macros are never used.
If REAL_DMA were to be defined, compilation would fail.
For the atari_NCR5380.c core driver, REAL_DMA is always defined.
Hence these macros are pointless.
Signed-off-by: Finn Thain
---
drivers/scsi/NCR5380.c | 218 +---
intel_idle already fixes MSRs on each CPU when it registers for that
CPU, so it doesn't need to separately broadcast to all CPUs on
startup.
Signed-off-by: Andy Lutomirski
---
drivers/idle/intel_idle.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/idle/intel_idle.c b/drivers/idle/
Only the atari_scsi and sun3_scsi drivers define DMA_MIN_SIZE.
Both drivers also define NCR5380_dma_xfer_len, which means
DMA_MIN_SIZE is redundant.
This removes another discrepancy between the two core drivers.
Signed-off-by: Finn Thain
---
drivers/scsi/atari_NCR5380.c | 16
I can't usefully test the fourth patch. I'm reasonably confident
that the other three work, though, and I tested them on a laptop
that doesn't preserve the C1E auto-promotion flag across
suspend/resume.
Andy Lutomirski (4):
intel_idle: Consolidate auto-promotion/auto-demotion fixups
intel_idl
Firmware that enables auto-promotion / auto-demotion flags we don't
like will probably re-enable them after suspend/resume. Disable
them again after resume so they stay fixed.
I've seen this on my Dell XPS 13 9350.
Signed-off-by: Andy Lutomirski
---
drivers/idle/intel_idle.c | 12
This change brings a number of improvements: fewer macros, better test
coverage, simpler code and sane Kconfig options. The downside is a small
chance of incompatibility (which seems unavoidable).
CONFIG_SCSI_GENERIC_NCR53C400 exists to enable or inhibit pseudo DMA
transfers when the driver is use
Hi Ben,
On Sat, 16 Jan 2016 09:55:15 +1100 Stephen Rothwell
wrote:
>
> On Fri, 15 Jan 2016 10:18:21 -0500 Benjamin LaHaise wrote:
> >
> > On Fri, Jan 15, 2016 at 01:25:31AM -0800, Christoph Hellwig wrote:
> > > On Fri, Jan 15, 2016 at 08:23:16PM +1100, Stephen Rothwell wrote:
> > > > Via
This eliminates some duplicate code and will make it easier
add fixup calls in places where they're currently missing.
Signed-off-by: Andy Lutomirski
---
drivers/idle/intel_idle.c | 34 +-
1 file changed, 13 insertions(+), 21 deletions(-)
diff --git a/drivers/idl
The demotion policy config registers are per-package and these CPUs
only exist in single-package variants AFAIK, so it's not stricly
necessary to fix these MSRs on each core, but fixing them on resume
is still likely to be helpful, so move them into fix_this_cpu.
Signed-off-by: Andy Lutomirski
--
Those wrapper drivers which use DMA define the REAL_DMA macro and
those which use pseudo DMA define PSEUDO_DMA. These macros need to be
removed for a number of reasons, not least of which is to have drivers
share more code.
Redefine the PDMA send and receive hooks as DMA setup hooks, so that the
D
For those wrapper drivers which only implement Programmed IO, have
NCR5380_dma_xfer_len() evaluate to zero. That allows PDMA to be easily
disabled at run-time and so the PSEUDO_DMA macro is no longer needed.
Also remove the spin counters used for debugging pseudo DMA drivers.
Signed-off-by: Finn
Add support for the Atari ST DMA chip to the NCR5380.c core driver.
This code is copied from atari_NCR5380.c.
Signed-off-by: Finn Thain
---
drivers/scsi/NCR5380.c| 32
drivers/scsi/atari_scsi.c |6 +++---
2 files changed, 35 insertions(+), 3 deletions(
The only chip that needs the workarounds enabled is an early NMOS
device. That means that the common case is to disable them.
Unfortunately the sense of the flag is such that it has to be set
for the common case.
Rename the flag so that zero can be used to mean "no errata workarounds
needed". Thi
The io_recovery_delay macro is intended to insert a microsecond delay
between the chip register accesses that begin a DMA operation. This
is reportedly needed for some ISA boards.
Reverse the sense of the macro test so that in the common case,
where no delay is required, drivers need not define th
Drivers that define PSEUDO_DMA also define NCR5380_dma_xfer_len.
The core driver must call NCR5380_dma_xfer_len which means
FLAG_NO_PSEUDO_DMA can be eradicated from the core driver.
dmx3191d doesn't define PSEUDO_DMA and has no use for FLAG_NO_PSEUDO_DMA,
so remove it there also.
Signed-off-by:
The driver has a limit of eight LUs because of the byte-sized bitfield
that is used for busy flags. Reject commands with LUN > 7.
Signed-off-by: Finn Thain
---
drivers/scsi/NCR5380.c |6 ++
drivers/scsi/NCR5380.h |2 ++
2 files changed, 8 insertions(+)
Index: linux/drivers/scsi/NCR
Adopt the DMA implementation from atari_NCR5380.c. This means that
atari_scsi and sun3_scsi can make use of the NCR5380.c core driver
and the atari_NCR5380.c driver fork can be made redundant.
Signed-off-by: Finn Thain
---
drivers/scsi/NCR5380.c | 170 +++--
Standardize the DMA setup hooks so that the DMA implementation in
atari_NCR5380.c can be reconciled with pseudo DMA implementation in
NCR5380.c.
Calls to NCR5380_dma_recv_setup() and NCR5380_dma_send_setup() return
a negative value on failure, zero on PDMA transfer success and a positive
byte coun
Add support for the custom Sun 3 DMA logic to the NCR5380.c core driver.
This code is copied from atari_NCR5380.c.
Signed-off-by: Finn Thain
---
The Sun 3 DMA code is still configured by macros. I have simplified things
slightly but I have avoided more ambitious refactoring. It's not clear to
m
On Mon, Mar 14, 2016 at 10:21:57AM +0900, Sergey Senozhatsky wrote:
> Hello Byungchul,
>
> Sorry, I'll make sure I Cc you next time. Jan Kara's updated patch set
>
> http://marc.info/?l=linux-kernel&m=145787625506342
Hello Sergey,
It would be appreciated if you or Jan Cc me from now.
>
> it's
Update kernel parameter documentation for atari_scsi, mac_scsi and
g_NCR5380 drivers. Remove duplication.
Signed-off-by: Finn Thain
---
Documentation/scsi/g_NCR5380.txt | 17 ++-
Documentation/scsi/scsi-parameters.txt | 11 +++---
drivers/scsi/g_NCR5380.c
The dmx3191d driver is not capable of DMA or PDMA so all transfers
use PIO. Now that large slow PIO transfers periodically stop and call
cond_resched(), the max_sectors limit can go away.
Signed-off-by: Finn Thain
---
drivers/scsi/dmx3191d.c |1 -
1 file changed, 1 deletion(-)
Index: linux
Some freescale QorIQ platforms require to disable receiver detection
in P3 for correct detection of USB devices. If GUSB3PIPECTL(DISRXDETINP3)
is set, Core will change PHY power state to P2 and then perform receiver
detection. After receiver detection, Core will change PHY power state to
P3. Same
Now that atari_scsi and sun3_scsi have been converted to use the NCR5380.c
core driver, remove atari_NCR5380.c. Also remove the last vestiges of its
Tagged Command Queueing implementation from the wrapper drivers.
The TCQ support in atari_NCR5380.c is abandoned by this patch. It is not
merged into
Decode all bits in the chip registers. They are all useful at times.
Fix printk severity so that this output can be suppressed along with
the other debugging output.
Signed-off-by: Finn Thain
---
drivers/scsi/NCR5380.c | 42 +-
1 file changed, 25 insert
On Sun, Mar 13, 2016 at 9:36 PM, Masahiro Yamada
wrote:
> 2016-03-14 13:28 GMT+09:00 Andy Lutomirski :
>> On Sun, Mar 13, 2016 at 9:08 PM, Masahiro Yamada
>> wrote:
>>>
>>> Hi Andy
>>>
>>> 2016-03-14 9:39 GMT+09:00 Andy Lutomirski :
>>> > On Mar 12, 2016 4:14 PM, "Masahiro Yamada"
>>> > wrote:
>
Signed-off-by: Finn Thain
---
drivers/scsi/NCR5380.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Index: linux/drivers/scsi/NCR5380.c
===
--- linux.orig/drivers/scsi/NCR5380.c 2016-03-14 15:26:50.0 +1100
When initializing sdio card, we get struct mmc_card
from mmc_alloc_card which allocates it by kzalloc. So we
don't need another memset while reading cccr.
Signed-off-by: Shawn Lin
---
drivers/mmc/core/sdio.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/mmc/core/sdio.c b/drivers/
The benefit of limiting can_queue to 1 is that atari_scsi shares the
ST DMA chip more fairly with other drivers (e.g. falcon-ide).
Unfortunately, this can limit SCSI bus utilization. On systems without
IDE, atari_scsi should issue SCSI commands whenever it can arbitrate for
the bus. Make that poss
Fix various issues: Comments about bus errors are incorrect. The
PDMA asm must return the size of the memory access that faulted so the
transfer count can be adjusted accordingly. A phase change may cause a
bus error but should not be treated as failure. A bus error does not
always imply a phase ch
Signed-off-by: Finn Thain
---
drivers/scsi/NCR5380.c | 12 +---
drivers/scsi/NCR5380.h |4
drivers/scsi/arm/oak.c |2 --
drivers/scsi/dmx3191d.c |2 --
drivers/scsi/dtc.c | 12 +++-
drivers/scsi/g_NCR5380.c |2 --
drivers/scsi/pas16.c |
This setting does not need to be conditional on Atari ST or TT.
Without TCQ support, cmd_per_lun == 2 is probably reasonable...
Signed-off-by: Finn Thain
---
drivers/scsi/atari_scsi.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Index: linux/drivers/scsi/atari_scsi.c
===
Hi all,
On Mon, 14 Mar 2016 15:36:47 +1100 Stephen Rothwell
wrote:
>
> And I forgot this bit :-(
And just to show I should be on holidays, this as well :-(
From: Stephen Rothwell
Date: Mon, 14 Mar 2016 15:38:22 +1100
Subject: [PATCH] vfs: do_loop_readv_writev API merge fix part 3
Signed-off-
This patch series has more macro elimination and some tweaks to the
DMA hooks so that all the wrapper drivers can share the same core
DMA algorithm. This resolves the major discrepancies between the two
core drivers, which relate to code conditional on the REAL_DMA and
PSEUDO_DMA macros.
After al
Hi all,
On Mon, 14 Mar 2016 15:32:14 +1100 Stephen Rothwell
wrote:
>
> I also added the following merge fix patch:
>
> From: Stephen Rothwell
> Date: Mon, 14 Mar 2016 15:28:05 +1100
> Subject: [PATCH] vfs: do_loop_readv_writev() API change merge fix
>
> Signed-off-by: Stephen Rothwell
> ---
2016-03-14 13:28 GMT+09:00 Andy Lutomirski :
> On Sun, Mar 13, 2016 at 9:08 PM, Masahiro Yamada
> wrote:
>>
>> Hi Andy
>>
>> 2016-03-14 9:39 GMT+09:00 Andy Lutomirski :
>> > On Mar 12, 2016 4:14 PM, "Masahiro Yamada"
>> > wrote:
>> >>
>> >> These targets are marked as PHONY. No need to add FORCE
From: Baoquan He
Subject: Re: [PATCH V2] proc-vmcore: wrong data type casting fix
Date: Mon, 14 Mar 2016 11:50:53 +0800
> On 03/14/16 at 11:47am, Baoquan He wrote:
>> On 03/14/16 at 12:25pm, HATAYAMA Daisuke wrote:
>> > From: Dave Young
>> > Subject: [PATCH V2] proc-vmcore: wrong data type casti
Hi Benjamin,
Today's linux-next merge of the aio tree got a conflict in:
fs/read_write.c
between commit:
793b80ef14af ("vfs: pass a flags argument to vfs_readv/vfs_writev")
from the vfs tree and commit:
4047629ed53e ("fs: make do_loop_readv_writev() non-static")
from the aio tree.
I f
> By BIOS (1.2.3 on a Dell XPS 13 9350) seems to want to enable C1E
> auto-promotion (ugh!), which results in this difference across
> suspend/resume according to turbostat:
>
> -cpu3: MSR_IA32_POWER_CTL: 0x0024005d (C1E auto-promotion: DISabled)
> +cpu3: MSR_IA32_POWER_CTL: 0x0024005f (C1E auto-p
On Sun, Mar 13, 2016 at 9:08 PM, Masahiro Yamada
wrote:
>
> Hi Andy
>
> 2016-03-14 9:39 GMT+09:00 Andy Lutomirski :
> > On Mar 12, 2016 4:14 PM, "Masahiro Yamada"
> > wrote:
> >>
> >> These targets are marked as PHONY. No need to add FORCE to their
> >> dependency.
> >
> > If this is, in fact, c
On 2016/3/11 17:01, Andy Shevchenko wrote:
> On Fri, 2016-03-11 at 11:25 +0800, Kejian Yan wrote:
>> When we use ethtool to retrieves or configure the receive flow hash
>> indirection table, ethtool needs to call .get_rxnfc to get the ring
>> number
>> so this patchset implements the .get_rxnfc
the tty_alloc_driver() can allocate memory for ttys and termios.
And also it can release allocated memory easly with using
put_tty_driver().
Signed-off-by: Daeseok Youn
---
drivers/staging/dgnc/dgnc_tty.c | 86 +++--
1 file changed, 31 insertions(+), 55 deleti
Signed-off-by: Daeseok Youn
---
drivers/staging/dgnc/dgnc_driver.h | 4 +-
drivers/staging/dgnc/dgnc_tty.c| 118 ++---
2 files changed, 61 insertions(+), 61 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_driver.h
b/drivers/staging/dgnc/dgnc_driver.h
in
For using tty_alloc_driver, SerialDriver has to be pointer type.
It also has checkpatch.pl warning about Camelcase, so
SerialDriver is changed to serial_driver.
Signed-off-by: Daeseok Youn
---
drivers/staging/dgnc/dgnc_driver.h | 4 +-
drivers/staging/dgnc/dgnc_tty.c| 118 +
Get some build coverage of S5P/Exynos AES H/W acceleration driver.
Driver uses DMA and devm_ioremap_resource() so add DMA and IOMEM
dependencies for the compile testing.
Signed-off-by: Krzysztof Kozlowski
---
Compile-tested on x86, x86_64, ppc64, arm, arm64 and mips.
---
drivers/crypto/Kconfig
1 - 100 of 363 matches
Mail list logo
