On Fri, 7 Nov 2014 14:41:12 +0100
Alexandre Belloni wrote:
> On 05/11/2014 at 17:01:16 +0100, Boris Brezillon wrote :
> > Arnd, you've commented the first version of this driver (IIRC, you
> > focused on the DT binding part), could you give your feedback on this
> > version (I based the new DT
Allocating with __GFP_DMA avoids the need for bounce buffers
Signed-off-by: Andrew Jackson
---
drivers/tty/serial/amba-pl011.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/tty/serial/amba-pl011.c b/drivers/tty/serial/amba-pl011.c
index 8572f2a..a285196
If the DMA engine doesn't support residue processing then the RX DMA
handling won't work terribly well if polling is enabled. So, disable
RX DMA if residue handling isn't available.
Signed-off-by: Andrew Jackson
---
drivers/tty/serial/amba-pl011.c | 17 -
1 files changed, 16
The DMA engines on some systems require that the dma_length is set
when using scatter gather lists.
Signed-off-by: Andrew Jackson
---
drivers/tty/serial/amba-pl011.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/tty/serial/amba-pl011.c
The existing code assumed that PL011_DMA_BUFFER_SIZE == UART_XMIT_SIZE,
which may not always be the case. This allows for these two being
different sizes and not copying too much data.
Signed-off-by: Andrew Jackson
---
drivers/tty/serial/amba-pl011.c |6 +-
1 files changed, 5
This patch set fixes a number of issues found when using
DMA driven UART transfers on the PL011 UART through a
DMA330 DMA controller on a 64bit system.
Andrew Jackson (5):
serial: pl011: Allocate TX DMA buffer from DMA capable memory
serial: pl011: Avoid assumptions about buffer size when
On Fri, 7 Nov 2014, Catalin Marinas wrote:
> On Fri, Nov 07, 2014 at 11:05:25AM +, Catalin Marinas wrote:
> > BTW, drivers/xen/swiotlb-xen.c needs something like:
> >
> > dma_addr_t dev_addr = xen_phys_to_bus(phys_to_dma(phys));
> >
> > phys != bus address.
>
> Wrong place, what I
On Fri, 7 Nov 2014, Catalin Marinas wrote:
> On Thu, Nov 06, 2014 at 12:22:13PM +, Stefano Stabellini wrote:
> > On Thu, 6 Nov 2014, Catalin Marinas wrote:
> > > On Wed, Nov 05, 2014 at 06:15:38PM +, Stefano Stabellini wrote:
> > > > On Wed, 5 Nov 2014, Catalin Marinas wrote:
> > > > >
Hi Alexandre,
On Fri, 7 Nov 2014 14:45:10 +0100
Alexandre Belloni wrote:
> On 05/11/2014 at 17:01:17 +0100, Boris Brezillon wrote :
> > AT91 SoCs have a memory range reserved for internal bus configuration.
> > Expose those registers so that drivers can make use of the matrix syscon
> >
Add equivalent attributes to those provided in the platform data
for use when RX DMA is enabled.
Signed-off-by: Andrew Jackson
---
Documentation/devicetree/bindings/serial/pl011.txt | 19 ++--
drivers/tty/serial/amba-pl011.c| 22 +--
2 files
On Friday 07 November 2014 14:27:55 Tomasz Nowicki wrote:
> These calls allow to map/unmap PCI config space ranges (which are specified in
> MMCFG ACPI table).
>
> Signed-off-by: Tomasz Nowicki
>
Nothing in this patch looks arm64 specific, and most of it looks like a
copy of the x86 code.
In order to have subsytem agnostic media bus format definitions we've
moved media bus definitions to include/uapi/linux/media-bus-format.h and
prefixed values with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Replace all references to the old definitions in i2c drivers.
Signed-off-by: Boris Brezillon
In order to have subsytem agnostic media bus format definitions we've
moved media bus definition to include/uapi/linux/media-bus-format.h and
prefixed them with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Update the v4l documentation accordingly.
Signed-off-by: Boris Brezillon
---
Replace references to the v4l2_mbus_pixelcode enum with the new
media_bus_format enum in all common headers.
Signed-off-by: Boris Brezillon
Acked-by: Sakari Ailus
---
include/media/v4l2-mediabus.h| 2 +-
include/media/v4l2-subdev.h | 2 +-
include/uapi/linux/v4l2-subdev.h | 6 +++---
On 11/07/2014 02:54 PM, David Vrabel wrote:
On 06/11/14 05:47, Juergen Gross wrote:
At start of the day the Xen hypervisor presents a contiguous mfn list
to a pv-domain. In order to support sparse memory this mfn list is
accessed via a three level p2m tree built early in the boot process.
Place v4l2_mbus_pixelcode in a #ifndef __KERNEL__ section so that kernel
users don't have access to these definitions.
We have to keep this definition for user-space users even though they're
encouraged to move to the new media_bus_format enum.
Signed-off-by: Boris Brezillon
---
Hello,
This patch series prepares the use of media bus formats outside of
the V4L2 subsytem (my final goal is to use it in the Atmel HLCDC DRM
driver where I have to configure my DPI/RGB bus according to the
connected display).
The series first defines MEDIA_BUS_FMT_ macros, and then replace all
In order to have subsytem agnostic media bus format definitions we've
moved media bus definition to include/uapi/linux/media-bus-format.h and
prefixed values with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Replace all references to the old definitions in pci drivers.
Signed-off-by: Boris Brezillon
On 07/11/14 13:19, Juergen Gross wrote:
> On 11/07/2014 02:04 PM, David Vrabel wrote:
>>
>> I suppose this is the "make some functions static" but it's an
>> unreviewable mess. If you can't do this with some one line changes
>> adding "static" and perhaps some forward declarations then please
On Friday 07 November 2014 14:27:54 Tomasz Nowicki wrote:
> Add special pci_mmcfg_insert_lock mutex since pci_mmcfg_lock was moved
> to common file. No functional changes.
>
> Signed-off-by: Tomasz Nowicki
>
What is the new lock protecting against? You no longer have a mutual
exclusion with
In order to have subsytem agnostic media bus format definitions we've
moved media bus definition to include/uapi/linux/media-bus-format.h and
prefixed enum values with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Reference new definitions in the ipu-v3 driver.
Signed-off-by: Boris Brezillon
---
In order to have subsytem agnostic media bus format definitions we've
moved media bus definition to include/uapi/linux/media-bus-format.h and
prefixed values with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Reference new definitions in all media drivers residing in staging.
Signed-off-by: Boris
In order to have subsytem agnostic media bus format definitions we've
moved media bus definition to include/uapi/linux/media-bus-format.h and
prefixed enum values with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Reference new definitions in all usb drivers.
Signed-off-by: Boris Brezillon
---
In order to have subsytem agnostic media bus format definitions we've
moved media bus definition to include/uapi/linux/media-bus-format.h and
prefixed values with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Reference new definitions in all platform drivers.
Signed-off-by: Boris Brezillon
---
Define MEDIA_BUS_FMT macros (re-using the values defined in the
v4l2_mbus_pixelcode enum) into a separate header file so that they can be
used from the DRM/KMS subsystem without any reference to the V4L2
subsystem.
Then set V4L2_MBUS_FMT definitions to the MEDIA_BUS_FMT values using the
On Fri, Nov 07, 2014 at 07:11:53AM -0600, Josh Poimboeuf wrote:
> 2. Add consistency model(s) (e.g. kpatch stop_machine, kGraft per-task
>consistency, Masami's per task ref counting)
I have given some thought to the consistency models and how they differ
and how they potentially could be
On 11/07, AKASHI Takahiro wrote:
>
> --- a/arch/arm/kernel/ptrace.c
> +++ b/arch/arm/kernel/ptrace.c
> @@ -853,11 +853,6 @@ long arch_ptrace(struct task_struct *child, long request,
> datap);
> break;
>
> - case
Hello Minchan,
On (11/07/14 13:55), Minchan Kim wrote:
> On Thu, Nov 06, 2014 at 10:43:42PM +0900, Sergey Senozhatsky wrote:
> > Hello,
> >
> > On (11/05/14 09:10), Minchan Kim wrote:
> > > zram_rw_page returns error code to upper layer with PG_error flag
> > > of the page but it should be wrong
Also move static variable no_buildid_cache and check it in the
perf_session_cache_build_ids().
Signed-off-by: Namhyung Kim
---
tools/perf/util/build-id.c | 11 +++
tools/perf/util/build-id.h | 1 +
tools/perf/util/header.c | 10 +-
tools/perf/util/util.h | 1 -
4 files
On 06/11/14 05:47, Juergen Gross wrote:
> When the physical memory configuration is initialized the p2m entries
> for not pouplated memory pages are set to "invalid". As those pages
> are beyond the hypervisor built p2m list the p2m tree has to be
> extended.
>
> This patch delays processing the
Add a new config option for auto-disable buildid-cache.
$ cat ~/.perfconfig
[record]
use-buildid-cache = false
$ rm -rf ~/.debug
$ perf record -av sleep 1
mmap size 528384B
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.439 MB perf.data
Hi Vlastimil,
On Fri, 07 Nov 2014, Vlastimil Babka wrote:
> Great, that's good news if I understand correctly, but ...
no "but ..."
> I suggested the commit to you for revert 1 day ago, and you say you
> can't reproduce it for 2 days already? That's a bit suspicious. Did
No, you suggested it
We probabyl should start making sure we have a commit log for every
patches ;)
On 05/11/2014 at 17:01:22 +0100, Boris Brezillon wrote :
> +Child chip-select (cs) nodes contain the memory devices nodes connected to
> +such as NOR (e.g. cfi-flash) and NAND.
> +There might be board specific devices
Add runtime Power Management to the Exynos DSI driver so the LCD power
domain could be turned off.
This slightly reduces the energy consumption when screen is completely
turned off. On Trats2 board when the system was idle the energy
consumption dropped by 1% (from 92.2 mA to 91.1 mA).
Before
On 06/11/14 05:47, Juergen Gross wrote:
> At start of the day the Xen hypervisor presents a contiguous mfn list
> to a pv-domain. In order to support sparse memory this mfn list is
> accessed via a three level p2m tree built early in the boot process.
> Whenever the system needs the mfn associated
During system resume from suspend to RAM the Exynos DRM driver forced
CRTC mode thus turning display on (DPMS_ON). This lead to runtime resuming
of DSI which failed because whole LCD power domain was off and it was
not allowed to turn on because of system resume in progress.
Forcing mode should
Hi,
Changes since v1
1. Replace patch 1 changing PM core with fix only for DRM exynos driver.
Description
===
The goal of the patch 2 is to add runtime PM to the Exynos DSI driver.
This allows LCD power domain to be turned off.
However after adding this patch an
The pmu-sram is used to store resume code, suspend/resume need get the
address of it. Therefore add a binding and documentation for it.
Signed-off-by: Tony Xie
Signed-off-by: Chris Zhong
Reviewed-by: Doug Anderson
---
Changes in v7: None
Changes in v6:
- change pmu_intmem@ff72 to
It's a basic version of suspend and resume for rockchip,
it only support RK3288 now.
Signed-off-by: Tony Xie
Signed-off-by: Chris Zhong
Tested-by: Doug Anderson
Reviewed-by: Doug Anderson
---
Changes in v7:
- get rid all of unused code
Changes in v6:
- get rid of the save/restore of SRAM
-
add pmu sram node for suspend, add global_pwroff pinctrl.
The pmu sram is used to store the resume code.
global_pwroff is held low level at work, it would be pull to high
when entering suspend. reference this in the board DTS file since
some boards need it.
Signed-off-by: Tony Xie
Signed-off-by:
global_pwroff would be pull to high when RK3288 entering suspend,
this pin is a sleep signal for RK808, so RK808 could goto sleep
mode, and some regulators would be disable.
Signed-off-by: Chris Zhong
---
Changes in v7:
- add regulator-state-mem sub node for suspend
Changes in v6: None
save and restore some clks, which might be changed in suspend.
Signed-off-by: Tony Xie
Signed-off-by: Chris Zhong
Reviewed-by: Doug Anderson
Tested-by: Doug Anderson
---
Changes in v7: None
Changes in v6:
- modify comments
Changes in v5:
- modify comments
Changes in v4: None
Changes in
RK3288 can shut down the cpu, gpu and other device controllers in suspend,
and it will pull the GLOBAL_PWROFF pin to high in the final stage of the
process of suspend, pull the pin to low again when resume.
Changes in v7:
- get rid all of unused code
- add regulator-state-mem sub node for suspend
On 05/11/2014 at 17:01:17 +0100, Boris Brezillon wrote :
> AT91 SoCs have a memory range reserved for internal bus configuration.
> Expose those registers so that drivers can make use of the matrix syscon
> declared in at91 DTs.
>
> Signed-off-by: Boris Brezillon
> ---
>
On 05/11/2014 at 17:01:16 +0100, Boris Brezillon wrote :
> Arnd, you've commented the first version of this driver (IIRC, you
> focused on the DT binding part), could you give your feedback on this
> version (I based the new DT binding on TI's aemif driver).
>
Shouldn't you Cc Arnd then? ;)
--
On 11/06/2014 05:31 PM, Greg Kroah-Hartman wrote:
> On Thu, Nov 06, 2014 at 10:12:54PM +, Måns Rullgård wrote:
>> Greg Kroah-Hartman writes:
>>
>>> On Thu, Nov 06, 2014 at 09:38:59PM +, Måns Rullgård wrote:
Greg Kroah-Hartman writes:
> On Thu, Nov 06, 2014 at 09:01:36PM
Existing code updates cupfreq policy only while executing
cpufreq_apply_cooling() function (i.e. when notify_device != NOTIFY_INVALID).
It doesn't apply constraints when cpufreq policy update happens from any other
place but it should update the cpufreq policy with thermal constraints every
time
On 11/07/2014 02:07 PM, Norbert Preining wrote:
Hi Vlastimil,
On Thu, 06 Nov 2014, Vlastimil Babka wrote:
OK, one possibility is to do (it should apply cleanly)
git revert e14c720efdd73c6d69cd8d07fa894bcd11fe1973
I am running with this reverted now, and I cannot reproduce the
khugepage going
MMCFG table seems to be architecture independent and it makes sense
to share common code across all architectures. The ones that may need
architectural specific actions have default prototype (__weak).
Please note, there is not functional changes in this patch.
Signed-off-by: Tomasz Nowicki
---
>
> Antoine Tenart (7):
> usb: move the OTG state from the USB PHY to the OTG structure
> usb: rename phy to usb_phy in OTG
> usb: add support to the generic PHY framework in OTG
> usb: allow to supply the PHY in the drivers when using HCD
> usb: chipidea: rename transceiver and phy
These calls allow to map/unmap PCI config space ranges (which are specified in
MMCFG ACPI table).
Signed-off-by: Tomasz Nowicki
---
arch/arm64/Kconfig | 3 ++
arch/arm64/kernel/Makefile | 1 +
arch/arm64/kernel/mmconfig.c | 69
3 files
Code inspired by arch/x86/pci/acpi.c and arch/ia64/pci/pci.c files.
The main reasons why we need this:
- parse and manage resources (BUS, IO and MEM)
- create pci root bus and enumerate its children
- provide PCI config space accessors (via MMCONFIG)
Signed-off-by: Tomasz Nowicki
---
Add special pci_mmcfg_insert_lock mutex since pci_mmcfg_lock was moved
to common file. No functional changes.
Signed-off-by: Tomasz Nowicki
---
arch/x86/pci/mmconfig-shared.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/x86/pci/mmconfig-shared.c
Ever since raw_probe_proto_opt was added it had the problem of
causing the user iov to be read twice, once during the probe for
the protocol header and once again in ip_append_data.
This is a potential security problem since it means that whatever
we're probing may be invalid. This patch plugs
The patch set can be break down into two logic parts:
1. patch 1,2 - MMCONFIG code refacoring. MMCFG ACPI table has no arch
dependencies so it can be used across other architectures.
2. patch 3,4 aim for PCI ACPI probing on ARM64
Patches tested on Cavium ThunderX simulator with the latest ACPI
The function raw_probe_proto_opt tries to extract the first two
bytes from the user input in order to seed the IPsec lookup for
ICMP packets. In doing so it's processing iovec by hand and
overcomplicating things.
This patch replaces the manual iovec processing with a call to
memcpy_fromiovecend.
Hi Dave:
This series rewrites the function raw_probe_proto_opt in a more
readable fasion, and then fixes the long-standing bug where we
read the probed bytes twice which means that what we're using to
probe may in fact be invalid.
Cheers,
--
Email: Herbert Xu
Home Page:
This patch removes the use of skb_copy_datagram_const_iovec in
favour of the iovec iterator-based skb_copy_datagram_iter.
Signed-off-by: Herbert Xu
---
drivers/net/tun.c | 65 --
1 file changed, 30 insertions(+), 35 deletions(-)
diff --git
we were dereferencing dev to initialize pdata. but just after that we
have a BUG_ON(!dev). so we were basically dereferencing the pointer
first and then tesing it for NULL.
Signed-off-by: Sudip Mukherjee
---
drivers/net/usb/smsc95xx.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Remove the mach/ header dependency by including the necessary macros and taking
the appropriate resources from the system timer.
Also change the name to avoid conflicting with the at91sam9 watchdog driver and
allow to compile both the at91rm920 and at91sam9 watchdog drivers at the same
time.
This patch removes the use of skb_copy_datagram_const_iovec in
favour of the iovec iterator-based skb_copy_datagram_iter.
Signed-off-by: Herbert Xu
---
drivers/net/macvtap.c | 46 +-
1 file changed, 21 insertions(+), 25 deletions(-)
diff --git
This patch adds skb_copy_datagram_iter, which is identical to
skb_copy_datagram_iovec except that it operates on iov_iter
instead of iovec.
Eventually all users of skb_copy_datagram_iovec should switch
over to iov_iter and then we can remove skb_copy_datagram_iovec.
Signed-off-by: Herbert Xu
Now that both macvtap and tun are using skb_copy_datagram_iter, we
can kill the abomination that is skb_copy_datagram_const_iovec.
Signed-off-by: Herbert Xu
---
include/linux/skbuff.h |3 -
net/core/datagram.c| 89 -
2 files changed, 92
On Fri, Nov 07, 2014 at 02:13:37PM +0100, Jiri Kosina wrote:
> On Fri, 7 Nov 2014, Josh Poimboeuf wrote:
>
> > > Also, lpc_create_object(), lpc_create_func(), lpc_create_patch(),
> > > lpc_create_objects(), lpc_create_funcs(), ... they all are pretty much
> > > alike, and are asking for some
At Fri, 07 Nov 2014 12:10:46 +0100,
Stefan Seyfried wrote:
>
> Hi all,
>
> since 3.18-rc1, setting up a PPP interface kills my kernel with
>
> [ 163.433251] PPP generic driver version 2.4.2
> [ 164.452474] [ cut here ]
> [ 164.453327] kernel BUG at
On pią, 2014-11-07 at 13:28 +0100, Pavel Machek wrote:
> On Fri 2014-11-07 13:18:03, Krzysztof Kozlowski wrote:
> > On pią, 2014-11-07 at 13:13 +0100, Pavel Machek wrote:
> > > On Wed 2014-11-05 09:42:58, Krzysztof Kozlowski wrote:
> > > > On wto, 2014-11-04 at 21:18 +0100, Pavel Machek wrote:
> >
Hi Dave:
This patch series adds the helper skb_copy_datagram_iter, which
is meant to replace both skb_copy_datagram_iovec and its evil
twin skb_copy_datagram_const_iovec.
It then converts tun and macvtap over to the new helper and finally
removes skb_copy_datagram_const_iovec which is only used
On Thu, Nov 6, 2014 at 4:55 PM, Andy Lutomirski wrote:
> On Thu, Nov 6, 2014 at 8:07 AM, David Drysdale wrote:
>> Here's another pass at this. Some things to discuss in particular:
>>
>> 1) The current approach for interpreted execs (i.e. mostly "#!" scripts)
>>gives them an argv[1] filename
On Thu, Nov 6, 2014 at 6:06 PM, Kees Cook wrote:
> On Thu, Nov 6, 2014 at 8:07 AM, David Drysdale wrote:
>> diff --git a/fs/exec.c b/fs/exec.c
>> index a2b42a98c743..800d232c17bb 100644
>> --- a/fs/exec.c
>> +++ b/fs/exec.c
>> @@ -1422,10 +1431,12 @@ static int exec_binprm(struct linux_binprm
On Fri, 2014-11-07 at 13:54 +0100, Stefan Seyfried wrote:
> JFTR, this did not help:
> tux@linux:~/linux> zgrep CONFIG_RCU_NOCB_CPU /proc/config.gz
> # CONFIG_RCU_NOCB_CPU is not set
>
> neither did:
>
> --- a/init/main.c
> +++ b/init/main.c
> @@ -583,7 +583,7 @@ asmlinkage __visible void __init
On 11/07/2014 02:04 PM, David Vrabel wrote:
On 06/11/14 05:47, Juergen Gross wrote:
The m2p overrides are used to be able to find the local pfn for a
foreign mfn mapped into the domain. They are used by driver backends
having to access frontend data.
As this functionality isn't used in early
On Mon, 2014-10-27 at 00:46 +0100, Richard Weinberger wrote:
> The logic of vfree()'ing vol->upd_buf is tied to vol->updating.
> In ubi_start_update() vol->updating is set long before vmalloc()'ing
> vol->upd_buf. If we encounter a write failure in ubi_start_update()
> before vmalloc() the UBI
On Fri, 7 Nov 2014, Josh Poimboeuf wrote:
> > Also, lpc_create_object(), lpc_create_func(), lpc_create_patch(),
> > lpc_create_objects(), lpc_create_funcs(), ... they all are pretty much
> > alike, and are asking for some kind of unification ... perhaps iterator
> > for generic structure
On Thu, Nov 06, 2014 at 11:47:45PM -0800, Christoph Hellwig wrote:
> On Thu, Nov 06, 2014 at 09:24:23PM +0100, Vojtech Pavlik wrote:
> > One reason is that there are currently at least two generators using
> > very different methods of generation (in addition to the option of doing
> > the patch
On Fri, Nov 07, 2014 at 12:44:07PM +, Arnd Bergmann wrote:
> On Friday 07 November 2014 12:11:19 Russell King - ARM Linux wrote:
> > On Fri, Nov 07, 2014 at 01:03:00PM +0100, Arnd Bergmann wrote:
> > > On Friday 07 November 2014 11:55:51 Will Deacon wrote:
> > > > We need this for arm64 and,
On 11/07/14 12:43, Sakari Ailus wrote:
> Hi Boris,
>
> Thank you for the update.
>
> On Thu, Nov 06, 2014 at 10:56:59AM +0100, Boris Brezillon wrote:
>> Rename mediabus formats and move the enum into a separate header file so
>> that it can be used by DRM/KMS subsystem without any reference to
On 11/06/2014 04:12 PM, Rob Herring wrote:
> On Thu, Nov 6, 2014 at 12:37 AM, Alexandre Courbot
> wrote:
>> On 10/30/2014 01:22 AM, Tomeu Vizoso wrote:
>>> #clock-cells = <1>;
>>> #reset-cells = <1>;
>>> };
>>> @@ -60,4 +83,23 @@ Example board file:
>>>
Hi Akashil,
On Tue, Oct 28, 2014 at 5:48 AM, AKASHI Takahiro
wrote:
> Vijay,
>
> On 10/27/2014 09:45 PM, Vijay Kilari wrote:
>>
>> Hi Akashi,
>>
>> I could not reproduce this with my simulator.
>> It would be good if you could post result of KGDB test suite.
>>
>> From sysfs you can
Hi Vlastimil,
On Thu, 06 Nov 2014, Vlastimil Babka wrote:
> OK, one possibility is to do (it should apply cleanly)
> git revert e14c720efdd73c6d69cd8d07fa894bcd11fe1973
I am running with this reverted now, and I cannot reproduce the
khugepage going overboard anymore.
I tried hard since 2 days
On Fri, Nov 07, 2014 at 01:48:45PM +0100, Vojtech Pavlik wrote:
> On Fri, Nov 07, 2014 at 06:31:54AM -0600, Josh Poimboeuf wrote:
> > On Thu, Nov 06, 2014 at 09:24:23PM +0100, Vojtech Pavlik wrote:
> > > On Thu, Nov 06, 2014 at 10:58:57AM -0800, Christoph Hellwig wrote:
> > >
> > > > On Thu, Nov
On Thu, 06 Nov 2014, Maxime Coquelin wrote:
> On 11/06/2014 04:36 PM, Lee Jones wrote:
> >On Thu, 06 Nov 2014, Maxime Coquelin wrote:
> >>On 11/06/2014 12:28 PM, Lee Jones wrote:
> >>>On Thu, 06 Nov 2014, Maxime Coquelin wrote:
> >>>
> Hi Kishon,
> On 11/06/2014 07:59 AM, Kishon Vijay
This patch adds a devicetree node for the Secure
Non-Volatile Storage (SNVS) on the VF610 platform.
The SNVS block also has a Real Time Counter (RTC).
Signed-off-by: Sanchayan Maity
---
arch/arm/boot/dts/vfxxx.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git
This patch adds clock enable and disable support for
the SNVS peripheral, which is required for using the
RTC within the SNVS block.
Signed-off-by: Sanchayan Maity
---
drivers/rtc/rtc-snvs.c | 34 --
1 file changed, 32 insertions(+), 2 deletions(-)
diff --git
This patch adds support for clock gating of
the SNVS peripheral.
Signed-off-by: Sanchayan Maity
---
arch/arm/mach-imx/clk-vf610.c |1 +
include/dt-bindings/clock/vf610-clock.h |3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-imx/clk-vf610.c
The first version of the patches were send quiet a
while back.
https://lkml.org/lkml/2014/9/26/492
The reason for sending this v2 of the patches late was to
prevent any changes midway to the VF dts patches being tried
with the below commit.
https://lkml.org/lkml/2014/10/22/605
Changes since
On 06/11/14 05:47, Juergen Gross wrote:
> The m2p overrides are used to be able to find the local pfn for a
> foreign mfn mapped into the domain. They are used by driver backends
> having to access frontend data.
>
> As this functionality isn't used in early boot it makes no sense to
> initialize
On 11/07/2014 06:31 AM, Alexandre Courbot wrote:
> On 11/07/2014 12:12 AM, Rob Herring wrote:
>> On Thu, Nov 6, 2014 at 12:37 AM, Alexandre Courbot
>> wrote:
>>> On 10/30/2014 01:22 AM, Tomeu Vizoso wrote:
The EMC clock needs some extra information for changing its rate.
Some regulators can run on different operating modes (opmodes). This
allows systems to choose the most efficient opmode for each regulator.
This patch builds on top of (291d761 regulator: Document binding for
regulator suspend state for PM state) adding a regulator-initial-mode
DT property to
On Fri, 7 Nov 2014 12:09:33 +
Mark Rutland wrote:
> Hi,
>
> On Fri, Nov 07, 2014 at 11:14:09AM +, Alban Bedel wrote:
> > Allow embedding an FDT blob in the kernel image, this is mostly
> > useful to run new kernels on boards with old bootloaders.
>
> I am very much not keen on
Some regulators support their operating mode to be changed on startup
or by consumers when the system is running while others only support
their operating mode to be changed while the system has entered in a
suspend state.
The regulator Device Tree binding documents a set of properties to
The of_get_regulator_init_data() function is used to extract the regulator
init_data but information on how to extract certain data is defined in the
static regulator descriptor (e.g: how to map the hardware operating modes).
Add a const struct regulator_desc * parameter to the function signature
Drivers can use the of_regulator_match() function to parse the regulator
init_data from DT. A match table is used to specify the name of the node
containing the regulators, the device node and to return the init_data
to the caller.
But also the static regulator descriptor is needed to correctly
Hello Mark,
This is the fifth version of the series that adds regulator initial
and suspend operating modes support. It relies on the existing work
that added suspend states bindings. The opmodes are parsed by the
regulator core and drivers should only define a translation function
to map between
The "regulator-initial-mode" and "regulator-mode" DT properties allows
to configure the regulator operating modes at startup or when a system
enters into a susend state.
But these properties use as valid values the operating modes supported
by each device while the core deals with the standard
Am 07.11.2014 um 12:56 schrieb Stefan Seyfried:
> Hi Paul,
>
> Am 07.11.2014 um 12:53 schrieb Paul Bolle:
>> Wild guess: is CONFIG_RCU_NOCB_CPU perhaps set in your
>> v3.18-rc3 .config?
>
> Yes it is:
> tux@linux:~> zgrep CONFIG_RCU_NOCB_CPU /proc/config.gz
> CONFIG_RCU_NOCB_CPU=y
> #
On Thu, Nov 06, 2014 at 12:23:21PM +, Matt Fleming wrote:
> +static unsigned int __rotation_period = 250; /* ms */
There's two things being conflated here I think, even though they're
related.
The one is how long we'll let RMIDs settle before trying to reuse them,
the second is how often we
On Thu, Nov 06, 2014 at 11:20:48PM +0100, Jiri Kosina wrote:
> On Thu, 6 Nov 2014, Seth Jennings wrote:
>
> > > Thanks a lot for having started the work on this!
> > >
> > > We will be reviewing it carefully in the coming days and will getting
> > > back
> > > to you (I was surprised to see
On 10/21/14 17:06, Sebastian Reichel wrote:
> Hi,
>
> This is the RFCv2 patchset adding DT support to the si4713
> radio transmitter i2c driver. The changes can be summarized
> as follows:
>
> * Move regulator information back into the driver. The
>regulators needed are documented in the
On Fri, Nov 07, 2014 at 06:31:54AM -0600, Josh Poimboeuf wrote:
> On Thu, Nov 06, 2014 at 09:24:23PM +0100, Vojtech Pavlik wrote:
> > On Thu, Nov 06, 2014 at 10:58:57AM -0800, Christoph Hellwig wrote:
> >
> > > On Thu, Nov 06, 2014 at 07:51:57PM +0100, Vojtech Pavlik wrote:
> > > > I don't think
On 11/06/2014 08:09 PM, Dmitry Torokhov wrote:
On Thu, Nov 06, 2014 at 03:51:02PM +0200, Grygorii Strashko wrote:
Device's clocks need to be enabled always at probing time
if !CONFIG_PM_RUNTIME - in that way, device will become accesible
and, later, its clocks can be disabled/enabled during
401 - 500 of 1372 matches
Mail list logo
