From: Pankaj Dubey
Let's handle i2c interrupt re-configuration in i2c driver. This will
help us in removing some soc specific checks from machine files.
Since only Exynos5250, and Exynos5420 need to do this, added syscon
based phandle to i2c device nodes of respective SoC DT files.
Also handle sa
From: Pankaj Dubey
Exynos SoCs have Chipid, for identification of product IDs
and SoC revistions. Till now we are using static macros
such as soc_is_exynos and #ifdefs for run time identification
of SoCs and their revisions. This is leading to add new Kconfig,
soc_is_exynos definitions ea
From: Pankaj Dubey
This patch removed "plat/cpu.h" inclusion from hotplug.c as it
is not required.
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/hotplug.c |2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm/mach-exynos/hotplug.c b/arch/arm/mach-exynos/hotplug.c
index 0243ef
From: Pankaj Dubey
This patch enables chipid driver for ARCH_EXYNOS and refactors
machine code as well as exynos cpufreq driver code for using
chipid driver for identification of SoC ID and SoC rev.
This patch also updates DT binding information in exynos4 and
exynos5 dtsi file. As to differenti
From: Pankaj Dubey
This patch removes usage of soc_is_exynos4/5 from exynos.c.
For this we need to separate machine descriptors for exynos4
and exynos5. While doing this patch does some consolidation also.
CC: Russell King
CC: Thomas Abraham
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exyn
From: Pankaj Dubey
This patch series attempts to get rid of soc_is_exynos macros
and eventually with the help of this series we can probably get
rid of CONFIG_SOC_EXYNOS in near future.
Each Exynos SoC has ChipID block which can give information about
SoC's product Id and revision number.
From: Pankaj Dubey
Since all these code has been moved into i2c driver, now we can
safely remove them from machine files.
CC: Russell King
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/exynos.c | 38 +--
arch/arm/mach-exynos/include/mach/map.h |
This patch removed "plat/cpu.h" inclusion from hotplug.c as it
is not required.
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/hotplug.c |2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm/mach-exynos/hotplug.c b/arch/arm/mach-exynos/hotplug.c
index 0243ef3..5e19601 100644
---
Since all these code has been moved into i2c driver, now we can
safely remove them from machine files.
CC: Russell King
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/exynos.c | 38 +--
arch/arm/mach-exynos/include/mach/map.h |3 ---
arch/arm/ma
This patch removes usage of soc_is_exynos4/5 from exynos.c.
For this we need to separate machine descriptors for exynos4
and exynos5. While doing this patch does some consolidation also.
CC: Russell King
CC: Thomas Abraham
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/exynos.c
This patch enables chipid driver for ARCH_EXYNOS and refactors
machine code as well as exynos cpufreq driver code for using
chipid driver for identification of SoC ID and SoC rev.
This patch also updates DT binding information in exynos4 and
exynos5 dtsi file. As to differentiate product id bit-ma
Let's handle i2c interrupt re-configuration in i2c driver. This will
help us in removing some soc specific checks from machine files.
Since only Exynos5250, and Exynos5420 need to do this, added syscon
based phandle to i2c device nodes of respective SoC DT files.
Also handle saving and restoring of
Exynos SoCs have Chipid, for identification of product IDs
and SoC revistions. Till now we are using static macros
such as soc_is_exynos and #ifdefs for run time identification
of SoCs and their revisions. This is leading to add new Kconfig,
soc_is_exynos definitions each time new SoC suppo
This patch series attempts to get rid of soc_is_exynos macros
and eventually with the help of this series we can probably get
rid of CONFIG_SOC_EXYNOS in near future.
Each Exynos SoC has ChipID block which can give information about
SoC's product Id and revision number. Currently we have si
On 2014-04-18 02:35, Nadav Amit wrote:
> According to Intel specifications, PAE and non-PAE does not have any reserved
> bits. In long-mode, regardless to PCIDE, only the high bits (above the
> physical address) are reserved.
>
> Signed-off-by: Nadav Amit
> ---
> :100644 100644 7de069af.. e21aee
__mod_zone_page_stat() is not irq-safe, so it should be used carefully.
And it is not appropirately documented now. This patch adds comment for
it, and also documents for some of its call sites.
Suggested-by: Andrew Morton
Signed-off-by: Jianyu Zhan
---
mm/page_alloc.c | 2 ++
mm/rmap.c
On Fri, May 09, 2014 at 12:19:16PM -0700, Josh Triplett wrote:
> + if (port > 65535)
> + return 0;
> + switch (count) {
[...]
> + case 4:
> + if (__put_user(inl(port), buf) < 0)
> + return -EFAULT;
What if I attempt a four-byte read at 65535?
mlocked_vma_newpage() is only called in fault path by
page_add_new_anon_rmap(), which is called on a *new* page.
And such page is initially only visible via the pagetables, and the
pte is locked while calling page_add_new_anon_rmap(), so we need not
use an irq-safe mod_zone_page_state() here, using
mlocked_vma_newpage is used to determine if a new page is mapped into
a *mlocked* vma. It is poorly named, so rename it to newpage_in_mlocked_vma.
Signed-off-by: Jianyu Zhan
---
mm/internal.h | 4 ++--
mm/rmap.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/mm/inte
From: Jan Kiszka
Regression of 346874c9: PAE is set in long mode, but that does not mean
we have valid PDPTRs.
Signed-off-by: Jan Kiszka
---
arch/x86/kvm/x86.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index c5582c3..19
Hi Courtney,
On Fri, 2014-05-09 at 13:30 -0700, Courtney Cavin wrote:
> > > Requiring a specific PMIC listed before a generic one allows us an
> > > escape hatch in the future if for some reason we need to add a quirk for
> > > a specific PMIC.
> >
> > Is there a conclusion on this issue? I am
2014-05-09 19:03 GMT+02:00 Ville Syrjälä :
> On Fri, May 09, 2014 at 05:14:38PM +0100, Damien Lespiau wrote:
>> On Fri, May 09, 2014 at 06:11:37PM +0200, Jörg Otte wrote:
>> > > Jörg, can you please boot with drm.debug=0xe, reproduce the issue and
>> > > then attach the complete dmesg? Please make
On 9 May 2014, at 18:31, j...@joshtriplett.org wrote:
> On Fri, May 09, 2014 at 11:23:19AM -0400, Theodore Ts'o wrote:
>> Also, if you have time to double check the e-mail addresses that we
>> have, the Google Spreadsheet is here:
>>
>> http://goo.gl/FsVUFX
>
>> Peter P Waskiewicz Jr
>
> P
On 10/05/2014 03:16, Maxime Ripard wrote:
> On Fri, May 09, 2014 at 06:56:10PM +0200, Boris BREZILLON wrote:
>> The P2WI looks like an SMBus controller which only supports byte data
>> transfers. But, it differs from standard SMBus protocol on several
>> aspects:
>> - it supports only one slave de
Hi Nicolas,
On 09/05/2014 at 15:44:27 +0200, Nicolas Ferre wrote :
> Signed-off-by: Nicolas Ferre
> ---
> arch/arm/boot/dts/sama5d3.dtsi | 82
> ++
> 1 file changed, 82 insertions(+)
>
> diff --git a/arch/arm/boot/dts/sama5d3.dtsi b/arch/arm/boot/dts/sam
On Tue, May 6, 2014 at 1:47 AM, Dan Carpenter wrote:
>> diff --git a/drivers/staging/rtl8192u/ieee80211/rtl819x_TSProc.c
>> b/drivers/staging/rtl8192u/ieee80211/rtl819x_TSProc.c
>> index 426f223..c96dbab 100644
>> --- a/drivers/staging/rtl8192u/ieee80211/rtl819x_TSProc.c
>> +++ b/drivers/staging/
At Sat, 10 May 2014 11:17:45 +0200,
Knut Petersen wrote:
>
> S3 suspend / resume cycle works on kernels up to 3.14.x as expected.
> With kernels 3.15.0-rc2 it's necessary to reload the alsa modules as sound
> stays silent otherwise.
>
> Hardware: AOpen i915GMm-hfs mobo, hda intel sound with real
The P2WI looks like an SMBus controller which only supports byte data
transfers. But, it differs from standard SMBus protocol on several
aspects:
- it supports only one slave device, and thus drop the address field
- it adds a parity bit every 8bits of data
- only one read access is required to rea
Hello,
This series adds support for the P2WI block used by some Allwinner
boards to interface with the AXP221 PMIC.
Best Regards,
Boris
Changes since v3:
- update the DT bindings doc
- fix a comment that was no longer true
Changes since v2:
- drop the initialization (switch from I2C to P2WI mo
P2WI (Push/Pull 2 Wire Interface) is an SMBus like bus used to communicate
with some PMICs (like the AXP221).
Document P2WI DT bindings which are pretty much the same as the one defined
for the marvell's mv64xxx controller.
Signed-off-by: Boris BREZILLON
---
.../devicetree/bindings/i2c/i2c-sunx
Using devm_ioremap_resource() API should actually be preferred over
devm_ioremap(), since the former request the mem region first and then
gives back the ioremap'ed memory pointer.
devm_ioremap_resource() calls request_mem_region(), therby preventing
other drivers to make any overlapping call to th
Using devm_ioremap_resource() API should actually be preferred over
devm_ioremap(), since the former request the mem region first and then
gives back the ioremap'ed memory pointer.
devm_ioremap_resource() calls request_mem_region(), therby preventing
other drivers to make any overlapping call to th
Using devm_ioremap_resource() API should actually be preferred over
devm_ioremap(), since the former request the mem region first and then
gives back the ioremap'ed memory pointer.
devm_ioremap_resource() calls request_mem_region(), therby preventing
other drivers to make any overlapping call to th
Based on 'usb-next' branch of Greg's usb tree.
devm_ioremap_resource() API is advantageous over devm_ioremap()
and should therefore be preferred to request any ioremap'ed address
for hcd.
Vivek Gautam (6):
usb: host: ehci-exynos: Use devm_ioremap_resource instead of
devm_ioremap
usb: host
Using devm_ioremap_resource() API should actually be preferred over
devm_ioremap(), since the former request the mem region first and then
gives back the ioremap'ed memory pointer.
devm_ioremap_resource() calls request_mem_region(), therby preventing
other drivers to make any overlapping call to th
Using devm_ioremap_resource() API should actually be preferred over
devm_ioremap(), since the former request the mem region first and then
gives back the ioremap'ed memory pointer.
devm_ioremap_resource() calls request_mem_region(), therby preventing
other drivers to make any overlapping call to th
Using devm_ioremap_resource() API should actually be preferred over
devm_ioremap(), since the former request the mem region first and then
gives back the ioremap'ed memory pointer.
devm_ioremap_resource() calls request_mem_region(), therby preventing
other drivers to make any overlapping call to th
Somehow $ was overlooked in the last round of whitespace
cleanups.
Do that now, before making further changes.
Signed-off-by: Manfred Spraul
---
ipc/sem.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/ipc/sem.c b/ipc/sem.c
index bee5554..5749b9c 100644
--- a/ipc/sem.c
Per definition, a task waits on exactly one semaphore:
The semaphore from the first operation in the sop array that cannot proceed.
The Linux implementation never followed the standard, it tried to count all
semaphores that might be the reason why a task sleeps.
This patch fixes that.
Note:
The
Right now, perform_atomic_semop gets the content of sem_queue as individual
fields.
Changes that, instead pass a pointer to sem_queue.
This is a preparation for the next patch: it uses
sem_queue to store the reason why a task must sleep.
Signed-off-by: Manfred Spraul
---
ipc/sem.c | 38
Preparation for the next patch:
In the slow-path of perform_atomic_semop(), store a pointer to the operation
that caused the operation to block.
Signed-off-by: Manfred Spraul
---
ipc/sem.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/ipc/sem.c b/ipc/sem.c
index 3962cca..22a4c12 100644
Hi all,
According to the man page of semop(), semzcnt or semncnt are increased
exactly for the operation that couldn't proceed.
The Linux implementation always tried to be clever and to increase the counters
for all operations that might be the reason why a task sleeps.
The following patches fix
count_semzcnt and count_semncnt are more of less identical.
The patch creates a single function that either counts the number of tasks
waiting for zero or waiting due to a decrease operation.
Signed-off-by: Manfred Spraul
---
ipc/sem.c | 103 ++
GETZCNT is supposed to return the number of threads that wait until
a semaphore value becomes 0.
The current implementation overlooks complex operations that contain
both wait-for-zero operation and operations that alter at least one semaphore.
The patch fixes that.
It's intentionally copy&paste,
Sat, 10 May 2014 15:26:58 +0530 от Vivek Gautam :
> Using devm_ioremap_resource() API should actually be preferred over
> devm_ioremap(), since the former request the mem region first and then
> gives back the ioremap'ed memory pointer.
> devm_ioremap_resource() calls request_mem_region(), therby p
On Wed, 7 May 2014 15:25:57 -0700
Andrew Morton wrote:
> On Wed, 7 May 2014 22:33:39 +0200 Fabian Frederick wrote:
>
> > This patch fixes a sparse warning about noreturn attribute only
> > featuring in module.h
> >
> > kernel/module.c:212:6: error: symbol '__module_put_and_exit' redeclared wit
On 10/05/14 01:43, Hartmut Knaack wrote:
Philippe Reynes schrieb:
This driver add partial support of the
maxim 1027/1029/1031. Differential mode is not
supported.
It was tested on armadeus apf27 board.
Signed-off-by: Philippe Reynes
I've added a few additional comments to Hartmut's thorough
-no level printk converted to pr_warn/pr_info
-fixed a small identation problem
This is untested
Cc: Geert Uytterhoeven
Cc: Andrew Morton
Signed-off-by: Fabian Frederick
---
v2: use pr_cont after pr_ without newline (suggested by Geert Uytterhoeven)
arch/m68k/amiga/amisound.c | 2 +-
arch/m
On 08/05/14 15:56, Arnd Bergmann wrote:
Without ANON_INODES, we get this build error:
drivers/built-in.o: In function `iio_event_getfd':
:(.text+0x14bf18): undefined reference to `anon_inode_getfd'
All other users explicitly select this symbol, so we should
do the same thing here.
Signed-off-b
small suggestions regarding interrupt registration ( request_irq()) call:
1. instead of request_irq() call in probe function , i think interrupt
can be registered in dwceqos_open() call . since packet only come when
we make interface up( ifconfig up) .
2. in request_irq() thier is flag parameter ca
no level printk converted to pr_info
This is untested
Cc: Geert Uytterhoeven
Cc: Andrew Morton
Signed-off-by: Fabian Frederick
---
arch/m68k/apollo/config.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/arch/m68k/apollo/config.c b/arch/m68k/apollo/
On 09/05/14 13:57, Nicolas Ferre wrote:
On 09/05/2014 13:43, Arnd Bergmann :
On Friday 09 May 2014 12:01:48 Nicolas Ferre wrote:
On 08/05/2014 16:56, Arnd Bergmann :
Building the at91 adc driver with CONFIG_INPUT disabled results in this
build error:
ERROR: "input_event" [drivers/iio/adc/at91
This patch also fixes some checkpatch warnings
This is untested
Cc: Geert Uytterhoeven
Cc: Andrew Morton
Signed-off-by: Fabian Frederick
---
arch/m68k/hp300/config.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/arch/m68k/hp300/config.c b/arch/m68k/hp300/conf
irq and dma are both resource_size_t (derived from phys_addr_t <-> unsigned)
Cc: "Rafael J. Wysocki"
Cc: Andrew Morton
Signed-off-by: Fabian Frederick
---
drivers/pnp/resource.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/pnp/resource.c b/drivers/pnp/resourc
val is unsigned.
Cc: "James E.J. Bottomley"
Cc: Andrew Morton
Signed-off-by: Fabian Frederick
---
drivers/scsi/sd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
index efcbcd1..b54d4f8 100644
--- a/drivers/scsi/sd.c
+++ b/drivers/scsi
On Fri, 9 May 2014, Thomas Gleixner wrote:
> On Fri, 9 May 2014, Viresh Kumar wrote:
> So the right thing to do this is:
>
> 1A) Change the prototype of the set_mode callback to return int and
> fixup all users. Either add the missing default clause or remove
> the existing BUG()/ pr_err()
From: Borislav Petkov
... in 3a497f48637 ("perf: Simplify perf_event_exit_task_context()")
Cc: Peter Zijlstra
Signed-off-by: Borislav Petkov
---
kernel/events/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 7ab734fba
Hi,
i am currently working on an implemenation of my Board Management Controller
(BMC).
This Controller is a MCR assembled on almost all of our Compact PCI or Compact
PCI Serial
Cards as well as on some other CPU Boards.
The BMC includes LED´s, Watchdog, Voltage Monitoring and some other featur
Hi,
On Sat, May 10, 2014 at 3:36 PM, Alexander Shiyan wrote:
> Sat, 10 May 2014 15:26:58 +0530 от Vivek Gautam :
>> Using devm_ioremap_resource() API should actually be preferred over
>> devm_ioremap(), since the former request the mem region first and then
>> gives back the ioremap'ed memory po
Found by checkpatch.
Signed-off-by: Levente Kurusa
---
drivers/staging/rtl8821ae/pci.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8821ae/pci.c b/drivers/staging/rtl8821ae/pci.c
index a562aa6..7bbaef7 100644
--- a/drivers/staging/rtl8821ae/pci.c
+++
Using devm_ioremap_resource() API should actually be preferred over
devm_ioremap(), since the former request the mem region first and then
gives back the ioremap'ed memory pointer.
devm_ioremap_resource() calls request_mem_region(), therby preventing
other drivers to make any overlapping call to th
Using devm_ioremap_resource() API should actually be preferred over
devm_ioremap(), since the former request the mem region first and then
gives back the ioremap'ed memory pointer.
devm_ioremap_resource() calls request_mem_region(), therby preventing
other drivers to make any overlapping call to th
Using devm_ioremap_resource() API should actually be preferred over
devm_ioremap(), since the former request the mem region first and then
gives back the ioremap'ed memory pointer.
devm_ioremap_resource() calls request_mem_region(), therby preventing
other drivers to make any overlapping call to th
Using devm_ioremap_resource() API should actually be preferred over
devm_ioremap(), since the former request the mem region first and then
gives back the ioremap'ed memory pointer.
devm_ioremap_resource() calls request_mem_region(), therby preventing
other drivers to make any overlapping call to th
Based on 'usb-next' branch of Greg's usb tree.
devm_ioremap_resource() API is advantageous over devm_ioremap()
and should therefore be preferred to request any ioremap'ed address
for hcd.
Changes from v1:
- Changed the way returned pointer is checked for error value
as pointed out in the revi
Using devm_ioremap_resource() API should actually be preferred over
devm_ioremap(), since the former request the mem region first and then
gives back the ioremap'ed memory pointer.
devm_ioremap_resource() calls request_mem_region(), therby preventing
other drivers to make any overlapping call to th
Using devm_ioremap_resource() API should actually be preferred over
devm_ioremap(), since the former request the mem region first and then
gives back the ioremap'ed memory pointer.
devm_ioremap_resource() calls request_mem_region(), therby preventing
other drivers to make any overlapping call to th
From 95f6ac368dbe352af0dfa2097b7d58b416447be5 Mon Sep 17 00:00:00 2001
From: Aurabindo J
Date: Sat, 10 May 2014 15:16:58 +0530
Subject: [PATCH] mfd: abx500-core: Fix compiler warning larger stack frame
On systems with CONFIG_FRAME_WARN=1024, compiler warns the allocation of
an object of struct de
On Saturday, May 10, 2014 12:47:15 PM Fabian Frederick wrote:
> irq and dma are both resource_size_t (derived from phys_addr_t <-> unsigned)
>
> Cc: "Rafael J. Wysocki"
> Cc: Andrew Morton
> Signed-off-by: Fabian Frederick
Queued up for 3.16, thanks!
> ---
> drivers/pnp/resource.c | 4 ++--
>
On Fri, 9 May 2014, Paul E. McKenney wrote:
> On Sat, May 10, 2014 at 12:57:15AM +0200, Thomas Gleixner wrote:
> > On Fri, 9 May 2014, Christoph Lameter wrote:
> > > On Fri, 9 May 2014, Thomas Gleixner wrote:
> > > > I understand why you want to get this done by a housekeeper, I just
> > > > did n
Hello,
On Fri, May 09, 2014 at 11:13:56PM -0400, George Spelvin wrote:
> +config GLOB
> + tristate
> +#(Prompt disabled to reduce kbuild clutter until someone needs it.)
> +#prompt "glob_match() function"
> + help
> + This option provides a glob_match function for performing
On Sat, 10 May 2014, Frederic Weisbecker wrote:
> Anyway I agree that was overengineering at this stage.
>
> Fortunately nothing has been applied. I was too busy with cleanups and
> workqueues
> affinity.
Good.
> So the "only" damage is on bad directions given to Christoph. But you know
> how
Ooh, one more nitpick.
On Fri, May 09, 2014 at 11:13:56PM -0400, George Spelvin wrote:
> +/**
> + * glob_match - Shell-style pattern matching, like !fnmatch(pat, str, 0)
> + * @pat: Pattern to match. Metacharacters are ?, *, [ and \.
> + * (And, inside character classes, !, - and ].)
@ARG
On Sat, 10 May 2014, Frederic Weisbecker wrote:
> But I still have the plan to make the timekeeper use the full sysidle
> facility in order to adaptively get to dynticks idle.
>
> Reminder for others: in NO_HZ_FULL, the timekeeper (always CPU 0) stays
> completely periodic. It can't enter in dynti
On 05/10/2014 06:22 AM, Andreas Werner wrote:
Hi,
i am currently working on an implemenation of my Board Management Controller
(BMC).
This Controller is a MCR assembled on almost all of our Compact PCI or Compact
PCI Serial
Cards as well as on some other CPU Boards.
The BMC includes LED´s, Wa
On Sat, May 10, 2014 at 11:46:01AM +0200, Boris BREZILLON wrote:
> Hello,
>
> This series adds support for the P2WI block used by some Allwinner
> boards to interface with the AXP221 PMIC.
>
> Best Regards,
It looks fine now. Thanks for your work.
You have, for the two patches, my
Acked-by: Max
The USB clocks of the A31 seems to be parented to the 24MHz oscillator, and
handle the clocks for the USB phys and OHCI devices.
Signed-off-by: Maxime Ripard
Reviewed-by: Hans de Goede
---
arch/arm/boot/dts/sun6i-a31.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm
The A31 USB clock slightly differ from its older counterparts, mostly because
it has a different gate for each PHY, while the older one had a single gate for
all the phy.
Signed-off-by: Maxime Ripard
Reviewed-by: Hans de Goede
---
drivers/clk/sunxi/clk-sunxi.c | 6 ++
1 file changed, 6 inse
From: Boris BREZILLON
On the Allwinner's A31 SoC the reset line connected to the EHCI IP has to
be deasserted for the EHCI block to be usable.
Add support for an optional reset controller that will be deasserted on
power off and asserted on power on.
Signed-off-by: Boris BREZILLON
Signed-off-b
From: Boris BREZILLON
The APP4 EVB1 development boards embeds an A31, together with some NAND, one SD
card slot, and one SDIO + UART WiFi and Bluetooth chip, a few I2C buses, USB,
and a LCD display.
Signed-off-by: Boris BREZILLON
Signed-off-by: Maxime Ripard
Reviewed-by: Hans de Goede
---
ar
Hi everyone,
This patchset adds support for the USB controllers found in the
Allwinner A31.
While the design is similar to the earlier Allwinner SoCs that are
already supported, a few details here and there change, like the fact
that the PHYs now have one clock per phy, while it used to be only o
The OHCI controllers used in the Allwinner A31 are asserted in reset using a
global reset controller.
Add optional support for such a controller in the OHCI platform driver.
Signed-off-by: Maxime Ripard
Reviewed-by: Hans de Goede
---
Documentation/devicetree/bindings/usb/usb-ohci.txt | 1 +
d
The A31 has two ECHI/OHCI controllers, and one OHCI-only phy-less controller.
Signed-off-by: Maxime Ripard
Reviewed-by: Hans de Goede
---
arch/arm/boot/dts/sun6i-a31.dtsi | 77
1 file changed, 77 insertions(+)
diff --git a/arch/arm/boot/dts/sun6i-a31.dt
The USB phy controller in the A31 differs mostly from the older controllers
because it has a clock dedicated for each phy, while the older ones were having
a single clock for all the phys.
Signed-off-by: Maxime Ripard
Reviewed-by: Hans de Goede
---
drivers/phy/phy-sun4i-usb.c | 35 +
On Sat, May 10, 2014 at 02:31:28PM +0200, Thomas Gleixner wrote:
> On Sat, 10 May 2014, Frederic Weisbecker wrote:
> > But I still have the plan to make the timekeeper use the full sysidle
> > facility in order to adaptively get to dynticks idle.
> >
> > Reminder for others: in NO_HZ_FULL, the tim
On Fri, May 09, 2014 at 08:58:47PM -0400, Waiman Long wrote:
> On 05/08/2014 02:58 PM, Peter Zijlstra wrote:
> >On Wed, May 07, 2014 at 11:01:34AM -0400, Waiman Long wrote:
> >>@@ -221,11 +222,37 @@ static inline int trylock_pending(struct qspinlock
> >>*lock, u32 *pval)
> >> */
> >>for (;
On Sat, May 10, 2014 at 05:32:13AM -0700, Guenter Roeck wrote:
> On 05/10/2014 06:22 AM, Andreas Werner wrote:
> >Hi,
> >i am currently working on an implemenation of my Board Management Controller
> >(BMC).
> >
> >This Controller is a MCR assembled on almost all of our Compact PCI or
> >Compact
Thanks a lot for the feedback!
> On Fri, May 09, 2014 at 11:13:56PM -0400, George Spelvin wrote:
>> +/**
>> + * glob_match - Shell-style pattern matching, like !fnmatch(pat, str, 0)
>> + * @pat: Pattern to match. Metacharacters are ?, *, [ and \.
>> + * (And, inside character classes, !, -
On Fri, May 09, 2014 at 09:19:32PM -0400, Waiman Long wrote:
> On 05/08/2014 03:06 PM, Peter Zijlstra wrote:
> >On Wed, May 07, 2014 at 11:01:37AM -0400, Waiman Long wrote:
> >>If unfair lock is supported, the lock acquisition loop at the end of
> >>the queue_spin_lock_slowpath() function may need
On Fri, May 09, 2014 at 09:08:56PM -0400, Waiman Long wrote:
> On 05/08/2014 03:04 PM, Peter Zijlstra wrote:
> >On Wed, May 07, 2014 at 11:01:36AM -0400, Waiman Long wrote:
> >> /*
> >>+ * To have additional features for better virtualization support, it is
> >>+ * necessary to store additional da
On Sat, 2014-05-10 at 10:08 -0400, George Spelvin wrote:
> > What's the device ID of these devices?
>
> Oops! It's
>
> 05:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9172 SATA
> 6Gb/s Controller [1b4b:9172] (rev 11)
> 06:00.0 SATA controller [0106]: Marvell Technology Group L
Sat, 10 May 2014 17:30:04 +0530 от Vivek Gautam :
> Based on 'usb-next' branch of Greg's usb tree.
>
> devm_ioremap_resource() API is advantageous over devm_ioremap()
> and should therefore be preferred to request any ioremap'ed address
> for hcd.
>
> Changes from v1:
> - Changed the way returne
On Sat, 10 May 2014, Maxime Ripard wrote:
> From: Boris BREZILLON
>
> On the Allwinner's A31 SoC the reset line connected to the EHCI IP has to
> be deasserted for the EHCI block to be usable.
>
> Add support for an optional reset controller that will be deasserted on
> power off and asserted o
Hi,
Please find attached patch which fixes most of
"Missing blank line after declaration" in drivers/staging/usbip
directory.
There are still two WARNINGS reported which refers to the struct
declaration, and it seems to be a problem with the checkpatck.pl script.
Regards
Pawel Lebioda
>From 6fb
On Fri, 2014-05-09 at 20:27 -0400, Richard Guy Briggs wrote:
> Generate and assign a serial number per namespace instance since boot.
>
> Use a serial number per namespace (unique across one boot of one kernel)
> instead of the inode number (which is claimed to have had the right to change
> reser
The existing quirk for these devices doesn't really solve the problem,
re-implement it using the DMA alias iterator. We'll come back later
and remove the existing quirk and dma_source interface. Note that
device ID 0xe822 is typically function 0 and 0xe230 has been tested
to not need the quirk an
This version can be found in my git tree:
git://github.com/awilliam/linux-vfio.git dma-alias-v3
Please report any issues.
v3:
- Found several instances where I had PCI_SLOT when I meant
PCI_FUNC. Thanks to Andrew for spotting this. This should
fix the problem he was having with Ricoh qu
Several Marvell devices and a JMicron device have a similar DMA
requester ID problem to Ricoh, except they use function 1 as the
PCIe requester ID. Add a quirk for these to populate the DMA
function alias bitmap.
Signed-off-by: Alex Williamson
---
drivers/pci/quirks.c | 34 +++
Several PCIe-to-PCI bridges fail to provide a PCIe capability, causing
us to handle them as conventional PCI devices. In some cases, this
may be correct, in others it's not. Add a dev_flag bit to identify
devices to be handled as standard PCIe-to-PCI bridges.
Signed-off-by: Alex Williamson
---
There are a few broken devices that use the requester ID of a different
function in the slot for their DMA. To handle these, add a bitmap to
struct pci_dev (using an alignment gap) that quirks can populate. As
we iterate over the device and bus DMA aliases, also iterate over any
bits in the map.
1 - 100 of 210 matches
Mail list logo
