Hi Linus,
One more bug fix for v3.18. I debated whether or not to send you this
merge request because we're at such a late rc. The bug isn't critical
in that there is only one system known to be affected and the patch is
easy to backport. The codepath is used by pretty much every DT based
system,
On Wed, Dec 03, 2014 at 11:32:12PM +0800, Andy Yan wrote:
> diff --git a/drivers/gpu/drm/bridge/Kconfig b/drivers/gpu/drm/bridge/Kconfig
> index 884923f..26162ef 100644
> --- a/drivers/gpu/drm/bridge/Kconfig
> +++ b/drivers/gpu/drm/bridge/Kconfig
> @@ -3,3 +3,8 @@ config DRM_PTN3460
>
From: Thierry Reding
This new function is similar to clk_set_parent(), except that it doesn't
actually change the parent. It merely checks that the given parent clock
can be a parent for the given clock.
A situation where this is useful is to check that a particular setup is
valid before
Vlastimil Babka writes:
> On 12/01/2014 03:06 PM, Aneesh Kumar K.V wrote:
>> "Kirill A. Shutemov" writes:
>>
>>> On Mon, Dec 01, 2014 at 11:16:43AM +0530, Aneesh Kumar K.V wrote:
This make sure that we try to allocate hugepages from local node if
allowed by mempolicy. If we can't, we
On Wed, Dec 3, 2014 at 3:23 PM, Jean-Michel Hautbois
wrote:
> 2014-12-03 16:22 GMT+01:00 Grant Likely :
>> On Wed, Dec 3, 2014 at 1:27 PM, Jean-Michel Hautbois
>> wrote:
>>> Hi,
>>>
>>> I am using linux-next on a i.MX6 board, and it seems that there is a
>>> regression probably in DT parsing.
>>
On Wed, Dec 03, 2014 at 11:29:26PM +0800, Andy Yan wrote:
> +int imx_hdmi_bind(struct device *dev, struct device *master,
> + void *data, struct drm_encoder *encoder,
> + const struct imx_hdmi_plat_data *plat_data)
> {
> struct platform_device *pdev =
Sorry for the noise, I sent the email before finishing my answer.
On Wed, 3 Dec 2014 16:34:49 +0100
Boris Brezillon wrote:
> On Wed, 3 Dec 2014 16:15:36 +0100
> Nicolas Ferre wrote:
>
> > Le 03/12/2014 15:56, Nicolas Ferre a écrit :
> > > Le 01/12/2014 11:27, Boris Brezillon a écrit :
> > >>
Rockchip RK3288 hdmi is compatible with dw_hdmi
this patch is depend on patch by Mark Yao
see https://lkml.org/lkml/2014/12/2/161
drm: rockchip: Add basic drm driver
Signed-off-by: Andy Yan
---
Changes in v16: None
Changes in v15:
- remove THIS_MODULE in platform driver
Changes in v14: None
Signed-off-by: Andy Yan
---
Changes in v16:
- modify clocks bindings
- descrbie ddc-i2c-bus as optional
Changes in v15: None
Changes in v14: None
Changes in v13: None
Changes in v12: None
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8:
- Add documentation for
On Wed, 3 Dec 2014, Jonathan Corbet wrote:
On Wed, 3 Dec 2014 20:53:45 +0900
SeongJae Park wrote:
Documentation/cgroups/cpusets.txt | 6 +++---
Documentation/cgroups/memory.txt | 8
2 files changed, 7 insertions(+), 7 deletions(-)
I applied patch 1 to my docs tree, but this
some platform may not support all the display mode,
add mode_valid interface check it
Signed-off-by: Andy Yan
---
Changes in v16: None
Changes in v15: None
Changes in v14:
- remove drm_connector_register, because imx-drm core has registered
connector
Changes in v13: None
Changes in v12: None
HDMI_IH_I2CMPHY_STAT0 is a clear on write register, which indicates i2cm
operation status(i2c transfer done or error), every hdmi phy register
configuration must check this register to make sure the configuration
has complete. But the indication bit should be cleared after check, otherwise
the
On Wed, 3 Dec 2014 16:15:36 +0100
Nicolas Ferre wrote:
> Le 03/12/2014 15:56, Nicolas Ferre a écrit :
> > Le 01/12/2014 11:27, Boris Brezillon a écrit :
> >> The EBI (External Bus Interface) is used to access external peripherals
> >> (NOR, SRAM, NAND, and other specific devices like ethernet
RK3288 HDMI will not work without the spare bit of
HDMI_PHY_CONF0 enable
Signed-off-by: Andy Yan
---
Changes in v16: None
Changes in v15: None
Changes in v14: None
Changes in v13: None
Changes in v12: None
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8: None
Changes
On rockchip rk3288, only word(32-bit) accesses are
permitted for hdmi registers. Byte width accesses (writeb,
readb) generate an imprecise external abort.
Signed-off-by: Andy Yan
---
Changes in v16: None
Changes in v15:
- remove unio of the multi-byte register access, adviced by Philipp Zabel
Signed-off-by: Andy Yan
---
Changes in v16:
- describe ddc-i2c-bus as optional
- add common clocks bindings
Changes in v15: None
Changes in v14: None
Changes in v13: None
Changes in v12: None
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8:
- correct some spelling
the original imx hdmi driver is under drm/imx/,
which depends on imx-drm, so move the imx hdmi
driver out to drm/bridge and rename it to dw_hdmi
Signed-off-by: Andy Yan
---
Changes in v16: None
Changes in v15:
- add prefix dw_hdmi/DW_HDMI for public used dw_hdmi structs
adviced by Philipp
hdmi phy configuration is platform specific, which can be adusted
according to the board to get the best SI
Signed-off-by: Andy Yan
---
Changes in v16: None
Changes in v15: None
Changes in v14: None
Changes in v13:
- split phy configuration from patch#4
Changes in v12: None
Changes in v11:
On Wed, Dec 3, 2014 at 7:02 AM, Romain Perier wrote:
> Hi,
>
> My part looks good and unchanged (first commit), however I would
> prefer a confirmation from Grant about the full merge.
>
> Thanks,
> Romain
Looks okay to me.
g.
>
> 2014-12-03 5:27 GMT+01:00 Stephen Rothwell :
>> Hi Grant,
>>
>>
IMX6 and Rockchip RK3288 and JZ4780 (Ingenic Xburst/MIPS)
use the interface compatible Designware HDMI IP, but they
also have some lightly differences, such as phy pll configuration,
register width, 4K support, clk useage, and the crtc mux configuration
is also platform specific.
To reuse the imx
drm driver may probe before the i2c bus, so the driver should
defer probing until it is available
Signed-off-by: Andy Yan
Reviewed-by: Daniel Kurtz
---
Changes in v16: None
Changes in v15: None
Changes in v14: None
Changes in v13: None
Changes in v12:
- refactor of_node_put(ddc_node)
Changes
CHECK: Alignment should match open parenthesis
+ if ((hdmi->vic == 10) || (hdmi->vic == 11) ||
+ (hdmi->vic == 12) || (hdmi->vic == 13) ||
CHECK: braces {} should be used on all arms of this statement
+ if (hdmi->hdmi_data.video_mode.mdvi)
[...]
+ else {
[...]
We found Freescale imx6 and Rockchip rk3288 and Ingenic JZ4780 (Xburst/MIPS)
use the interface compatible Designware HDMI IP, but they also have some
lightly differences, such as phy pll configuration, register width(imx hdmi
register is one byte, but rk3288 is 4 bytes width and can only be
On Thu 2014-10-30 07:14:17, Dave Chinner wrote:
> On Wed, Oct 29, 2014 at 11:23:38AM -0700, Jason B. Akers wrote:
> > The following series enables the use of Solid State hybrid drives
> > ATA standard 3.2 defines the hybrid information feature, which provides a
> > means for the host driver to
2014-12-03 16:22 GMT+01:00 Grant Likely :
> On Wed, Dec 3, 2014 at 1:27 PM, Jean-Michel Hautbois
> wrote:
>> Hi,
>>
>> I am using linux-next on a i.MX6 board, and it seems that there is a
>> regression probably in DT parsing.
>
> Are you able to bisect down to the offending commit?
I am trying
Le 02/12/2014 09:47, Boris Brezillon a écrit :
> The EBI (External Bus Interface) is used to access external peripherals
> (NOR, SRAM, NAND, and other specific devices like ethernet controllers).
> Each device is assigned a CS line and an address range and can have its
> own configuration
Ok, Thanks Martin.
On Wed, Dec 3, 2014 at 8:51 PM, Martin K. Petersen
wrote:
>> "Sreekanth" == Sreekanth Reddy writes:
>
> Sreekanth> Anyone who aware of mpt2sas/mpt3sas driver's can please
> Sreekanth> review this patch set.
>
> It's on my todo list.
>
> --
> Martin K. Petersen Oracle
Benjamin Herrenschmidt writes:
> On Tue, 2014-12-02 at 12:57 +0530, Aneesh Kumar K.V wrote:
>> Now, hash_preload can possibly insert an hpte in hash page table even if
>> the access is not allowed by the pte permissions. But i guess even that
>> is ok. because we will fault again, end-up calling
On Tue, Dec 2, 2014 at 10:02 PM, Chris Rorvick wrote:
>
>> while a "good" _before_ a subsequent bad is
>> also trustworthy (because if the "good" kernel contained the bug and
>> you should have marked it bad, we'd then go on to test all the commits
>> that were *not* the bug, so we'd never see a
On Wed, Dec 3, 2014 at 1:27 PM, Jean-Michel Hautbois
wrote:
> Hi,
>
> I am using linux-next on a i.MX6 board, and it seems that there is a
> regression probably in DT parsing.
Are you able to bisect down to the offending commit?
Thanks,
g.
>
> Here is the DT I am using :
> vbx-leds {
>
On Tue, Dec 02, 2014 at 11:41:23PM +0100, Rickard Strandqvist wrote:
> Remove function mem_cgroup_lru_names_not_uptodate() that is not used anywhere.
>
> This was partially found by using a static code analysis program called
> cppcheck.
>
> Signed-off-by: Rickard Strandqvist
> ---
>
> "Sreekanth" == Sreekanth Reddy writes:
Sreekanth> Anyone who aware of mpt2sas/mpt3sas driver's can please
Sreekanth> review this patch set.
It's on my todo list.
--
Martin K. Petersen Oracle Linux Engineering
--
To unsubscribe from this list: send the line "unsubscribe
Hi Linus,
Single fix for a regression introduced in this development cycle, where
dm on top of dif/dix is broken. From Darrick Wong.
Please pull!
git://git.kernel.dk/linux-block.git for-linus
Darrick J. Wong (1):
block:
srcu callbacks are running in atomic context, we can't allocate using
__GFP_WAIT.
Signed-off-by: Sasha Levin
---
drivers/gpu/drm/amd/amdkfd/kfd_process.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_process.c
On Tue, 02 Dec 2014 16:23:49 -0600
Larry Finger wrote:
> On 12/02/2014 02:12 PM, Michael Büsch wrote:
> > On Tue, 2 Dec 2014 23:01:29 +0300
> > Andrey Skvortsov wrote:
> >
> >> On Mon, Dec 01, 2014 at 10:10:23PM +0100, Michael Büsch wrote:
> >>> On Mon, 1 Dec 2014 23:46:38 +0300
> >>> Andrey
On 12/01/2014 04:37 AM, Masami Hiramatsu wrote:
> (2014/11/29 1:01), Steve Capper wrote:
>> On 27 November 2014 at 06:07, Masami Hiramatsu
>> wrote:
>>> (2014/11/27 3:59), Steve Capper wrote:
The crash is extremely easy to reproduce.
I've not observed any missed events on a kprobe
Hi,
On 12/03/14 at 11:35am, Joerg Roedel wrote:
> Hi,
>
> On Wed, Dec 03, 2014 at 12:01:23PM +0800, WANG Chao wrote:
> >From your experience It seems like swiotlb isn't working well with
> > crashkernel=X,high alone. What about using crashkernel=X,low with
> > crashkernel=X,high? Is there any
Le 03/12/2014 15:56, Nicolas Ferre a écrit :
> Le 01/12/2014 11:27, Boris Brezillon a écrit :
>> The EBI (External Bus Interface) is used to access external peripherals
>> (NOR, SRAM, NAND, and other specific devices like ethernet controllers).
>> Each device is assigned a CS line and an address
On Wed, Dec 3, 2014 at 2:24 AM, Frank Rowand wrote:
> On 11/27/2014 9:56 AM, Leif Lindholm wrote:
>> Add a global binding for the chosen node.
>> Include a description of the stdout-path, and an explicit statement on
>> its extra options in the context of a UART console.
>>
>> Opening description
Felipe,
Question about the patch[1].
I want to change the code in a way to not touch fifo thresholds for each
message.
Because:
1. dev->threshold is valid only with checking of transfer direction.
So, if last transfer was transmission and ISR get RRDY interrupt from slave
receiver,
then
On 2 December 2014 at 12:15, Thierry Reding wrote:
> On Mon, Nov 24, 2014 at 01:28:17PM +0100, Tomeu Vizoso wrote:
>> The ACTMON block can monitor several counters, providing averaging and firing
>> interrupts based on watermarking configuration. This implementation monitors
>> the MCALL and
When running in non-cache coherent configuration the memory that was
allocated with dma_alloc_coherent() has a custom mapping and so there is no
1-to-1 relationship between the kernel virtual address and the PFN. This
means that virt_to_pfn() will not work correctly for those addresses and the
Le 01/12/2014 11:27, Boris Brezillon a écrit :
> The EBI (External Bus Interface) is used to access external peripherals
> (NOR, SRAM, NAND, and other specific devices like ethernet controllers).
> Each device is assigned a CS line and an address range and can have its
> own configuration
On 03/12/2014 15:23, Nadav Amit wrote:
> I think it is better just to replace the last line with:
>
> *(u64 *)(dest + XSAVE_HDR_OFFSET) = xsave->xsave_hdr.xstate_bv
Right, this matches
u64 xstate_bv = *(u64 *)(src + XSAVE_HDR_OFFSET);
...
xsave->xsave_hdr.xstate_bv =
On Wed, Dec 03, 2014 at 05:52:18PM +0300, Alexander Kochetkov wrote:
>
> 03 дек. 2014 г., в 17:49, Felipe Balbi написал(а):
>
> > NAK, if you want to add traces, use, well, tracepoints :-) It makes no
> > sense to hack stuff like this.
>
> It's for testing only the problem reported not for
Hi list,
[16623.095403] BUG: unable to handle kernel paging request at 010600d0
[16623.095445] IP: [] xfrm_selector_match+0x25/0x2f6
[16623.095480] PGD aeaea067 PUD 85d95067 PMD 0
[16623.095513] Oops: [#1] SMP
[16623.095543] Modules linked in: netconsole xt_nat xt_multiport veth
On 03/12/14 13:41, Tim Sander wrote:
>>> Even with using the FIQ on a Linux SMP system you have not heard from me
>>> before, as i knew that this is not your problem (and that is not to say
>>> that there where none!). The only interface Linux has been making
>>> available is set_fiq_handler. So
Hello,
On Tue, Dec 02, 2014 at 08:14:52PM -0800, Linus Torvalds wrote:
> I added Tejun to the Cc, just because I wanted to give him a heads-up
> that I am tentatively starting to blame him in my dark little mind..
Yeap, keeping watch on the thread and working on a patch to dump more
workqueue
03 дек. 2014 г., в 17:49, Felipe Balbi написал(а):
> NAK, if you want to add traces, use, well, tracepoints :-) It makes no
> sense to hack stuff like this.
It's for testing only the problem reported not for upstream :)
The hack stuff like this is to allow for me to see what happens on the
Hi Nicolas,
On Wed, 3 Dec 2014 15:32:49 +0100
Nicolas Ferre wrote:
> Le 01/12/2014 11:27, Boris Brezillon a écrit :
> > The Matrix registers are provided to configure internal bus behavior on
> > at91 SoCs.
> > Some registers might be access by several drivers (e.g. to configure
> > external
On Wed, 03 Dec 2014 03:20:19 +0008, Jason Wang said:
> > Still broken in next-20141201, and bisection fingers this commit:
> >
> > commit e0b46d0ee9c240c7430a47e9b0365674d4a04522
> > Author: Herbert Xu
> > Date: Fri Nov 7 21:22:23 2014 +0800
> >
> > tun: Use iovec iterators
> > What's the
On Wed, Dec 03, 2014 at 06:34:02PM +0400, Alexander Kochetkov wrote:
> Signed-off-by: Alexander Kochetkov
> ---
> drivers/i2c/busses/i2c-omap.c | 45
> ++---
> 1 file changed, 42 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-omap.c
On Wed, 2014-12-03 at 17:04 +1100, Michael Ellerman wrote:
> On powerpc we can end up with IMA=y and PPC_PSERIES=n which leads to:
>
> warning: (IMA) selects TCG_IBMVTPM which has unmet direct dependencies
> (TCG_TPM && PPC_PSERIES)
> tpm_ibmvtpm.c:(.text+0x14f3e8): undefined reference to
On Tuesday 02 December 2014 09:36:00 Doug Anderson wrote:
> On Tue, Dec 2, 2014 at 1:33 AM, Arnd Bergmann wrote:
> > On Monday 01 December 2014 15:04:59 Doug Anderson wrote:
> >> On Mon, Dec 1, 2014 at 2:50 PM, Russell King - ARM Linux
> >> wrote:
> > I recently looked at another vendor tree
On Tue, Aug 05, 2014 at 09:46:55PM +0200, Oleg Nesterov wrote:
> A simple test-case from Kirill Shutemov
>
> cat /proc/self/maps >/dev/null
> chmod +x /proc/self/net/packet
> exec /proc/self/net/packet
>
> makes lockdep unhappy, cat/exec take seq_file->lock + cred_guard_mutex
Carry out NACK and AL handling to main event loop as it should be.
The change affects omap3530 and early boards.
Tested and simulated on omap3730 (Beagleboard XM C).
Signed-off-by: Alexander Kochetkov
---
drivers/i2c/busses/i2c-omap.c | 39 ++-
1 file
Signed-off-by: Alexander Kochetkov
---
drivers/i2c/busses/i2c-omap.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
index 4563200..53b4234 100644
--- a/drivers/i2c/busses/i2c-omap.c
+++
The main reason is to avoid CON register access by omap_i2c_xfer_msg()
function, after transfer was submitted to IP.
The change takes into account comment from the code:
"Don't write stt and stp together on some hardware."
That mean, what some hardware doesn't support "Full transfers",
transfers
Signed-off-by: Alexander Kochetkov
---
drivers/i2c/busses/i2c-omap.c | 45 ++---
1 file changed, 42 insertions(+), 3 deletions(-)
diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
index 66506db..d2dfabe 100644
---
This pacth series intended for fixing problem reported
by Tony Lindgren here[1]
One of first four patched could fix the problem.
Last patch provide event trace so I could resolve problem.
It could be applied using 'git am' or 'patch -p1 ...'
Patches are rebased on branch 'i2c/for-next' of
The main reason is to avoid CON register access by omap_i2c_xfer_msg()
function, after transfer was submitted to IP.
Also changed NACK logic to wait ARDY so we can be sure what STP has
been sent on back to back transfers.
Tested on dm3730 (Beagleboard XM C).
Signed-off-by: Alexander Kochetkov
Le 01/12/2014 11:27, Boris Brezillon a écrit :
> The Matrix registers are provided to configure internal bus behavior on
> at91 SoCs.
> Some registers might be access by several drivers (e.g. to configure
> external memory bus timings), hence we declare this register set as a
> syscon device.
>
>
On Tue, Dec 02, 2014 at 08:54:13AM -0800, John Stultz wrote:
> On Tue, Dec 2, 2014 at 8:35 AM, Chris Wilson wrote:
> > On Tue, Dec 02, 2014 at 04:36:22PM +0100, Daniel Vetter wrote:
> >> +static inline unsigned long nsecs_to_jiffies_timeout(const u64 m)
> >> +{
> >> + u64 usecs = div_u64(m +
Am 03.12.2014 um 15:08 schrieb Harald Geyer:
> Richard Weinberger writes:
>> Harald,
>>
>> Am 03.12.2014 um 13:18 schrieb Harald Geyer:
>>> Hi Richard,
>>>
>>> thanks for all the work you put into this!
>>>
>>> Richard Weinberger writes:
I have also a question on your driver. Why you
On Wed, 3 Dec 2014 16:02:28 +0200
"Michael S. Tsirkin" wrote:
> On Tue, Dec 02, 2014 at 07:39:30PM +0100, Cornelia Huck wrote:
> > On Tue, 2 Dec 2014 13:44:06 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > balloon device is not part of virtio 1.0 spec. Still, it's easy enough
> > > to make
All the bit operations (such as find_first_zero_bit()) read sizeof(long) bytes
at a time. If we allocated less than sizeof(long) bytes for the bitmask we
would be accessing invalid memory when working with the bitmask.
Change the allocator to allocate sizeof(long) multiples for the bitmask.
Paolo Bonzini wrote:
> Userspace is expecting non-compacted format for KVM_GET_XSAVE, but
> struct xsave_struct might be using the compacted format. Convert
> in order to preserve userspace ABI.
>
> Likewise, userspace is passing non-compacted format for KVM_SET_XSAVE
> but the kernel will
Ralf
I remember now that we have applied to our tree the proposed patch
titled "MIPS HIGHMEM fixes for cache aliasing and non-DMA I/O".
This patch changes the semantics of flush_dcache_page() by using
page_mapped() instead of mapping_mapped() to decide if the flush should
be lazy. Is it this
Hello Catalin,
On 03/12/2014 11:32, Catalin Marinas wrote:
The reasons behind this proposal aren't clear. Are you trying
to optimise mmio register accesses by avoiding TLB misses?
I am trying to minimize TLB "pollution" by using a "huge" page.
The ARM manual states: "Support for
On Tue, Dec 02, 2014 at 09:00:17AM -0500, Mike Snitzer wrote:
> On Tue, Dec 02 2014 at 3:43am -0500,
> zhangxiao wrote:
>
> > Hi Experts,
> >
> > See drivers/md/dm-bufio.c as below:
> > 50 /*
> > 51 * Buffer hash
> > 52 */
> > 53 #define DM_BUFIO_HASH_BITS 20
> > 54 #define
So what *is* the difference in perf_event_attr between
.exclude_hv
and
.exclude_guest
.exclude_host
>From what I gather .exclude_hv excluces hypervisor counts if the hardware
supports that type of measurement, but only Power implements this.
.exclude_guest and
On 12/03/2014 01:38 PM, Ganesh Mahendran wrote:
> In current zram, we use DEVICE_ATTR() to define sys device attributes.
> SO, we need to set (S_IRUGO | S_IWUSR) permission and other
> arguments manually.
> Linux kernel has already provided macro DEVICE_ATTR_[RW|RO|WO] to define
> sys device
On 27 November 2014 at 01:38, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The SET_PM_RUNTIME_PM_OPS() and SET_RUNTIME_PM_OPS() macros are
> identical except that one of them is not empty for CONFIG_PM set,
> while the other one is not empty for CONFIG_PM_RUNTIME set,
> respectively.
>
On 12/03/2014 05:09 AM, Michal Marek wrote:
> On 2014-12-01 17:39, Shuah Khan wrote:
>> On 12/01/2014 08:47 AM, Michal Marek wrote:
>>> On 2014-11-11 21:27, Shuah Khan wrote:
diff --git a/Makefile b/Makefile
index 05d67af..ccbd2e1 100644
--- a/Makefile
+++ b/Makefile
@@
On 26/11/14 15:24, Krzysztof Kozlowski wrote:
> Audio subsystem clocks are located in separate block. If clock for this
> block (from main clock domain) 'mau_epll' is gated then any read or
> write to audss registers will block.
>
> This was observed on Exynos 5420 platforms (Arndale Octa and
Lars,
normally set_pte_at() is invoked in a
cache_flush_*()
set_pte_at()
tlb_flush_*()
sequence. So I'm wondering if you're trying to fix something in set_pte_at
that actually ought to be fixed in the cache_flush_*() function.
I'm wondering, have you identified which cache flush
On 12/03/2014 04:56 AM, Michael Ellerman wrote:
> On Wed, 2014-12-03 at 20:32 +1100, Stephen Rothwell wrote:
>> Hi Shuah,
>>
>> Today's linux-next merge of the kselftest tree got a cselftests/kcmp:
>> Always try to build the testonflict in
>> tools/testing/selftests/kcmp/Makefile between commit
Richard Weinberger writes:
> Harald,
>
> Am 03.12.2014 um 13:18 schrieb Harald Geyer:
> > Hi Richard,
> >
> > thanks for all the work you put into this!
> >
> > Richard Weinberger writes:
> >> I have also a question on your driver. Why you increment
> >> DHT11_DATA_BIT_LOW/timeres by one in the
On Wed, Dec 3, 2014 at 9:41 PM, Richard Cochran
wrote:
> In any case, I find it hard to believe that the traditional method is
> really so bad. The explanation of why this new way is needed boils
> down to: "unix programming is so hard to get right."
Surely, this can be said about any new
On 12/03/14 14:24, SF Markus Elfring wrote:
Sorry. I misread your email. If the code looks like this:
foo = kmalloc();
if (!foo)
goto kmalloc_failed;
The "kmalloc_failed" doesn't add any information.
I find that this such a name approach would fit to your
2014-12-03 14:40+0100, Paolo Bonzini:
> This is the size of the XSAVES area. This completes guest support
> for XSAVES (with no support yet for supervisor states, i.e. XSS == 0
> always in guests for now).
>
> Suggested-by: Radim Krčmář
> Signed-off-by: Paolo Bonzini
> ---
Reviewed-by: Radim
It is the flush_dcache_page() that was called from the file-system
reading the page contents into memory.
- Lars
On Wed, 2014-12-03 at 14:42 +0100, Ralf Baechle wrote:
> Lars,
>
> normally set_pte_at() is invoked in a
>
> cache_flush_*()
> set_pte_at()
> tlb_flush_*()
>
> sequence. So
On Wed, 3 Dec 2014 15:45:41 +0900
Masahiro Yamada wrote:
> The arch header directories "include/asm-*" were moved long ago.
> Now we should check the existence of arch/*/include/uapi/asm/Kbuild
> to see if an architecture supports the headers installation.
> (Actually, "um" is the only
On Tue, Dec 02, 2014 at 07:39:30PM +0100, Cornelia Huck wrote:
> On Tue, 2 Dec 2014 13:44:06 +0200
> "Michael S. Tsirkin" wrote:
>
> > balloon device is not part of virtio 1.0 spec. Still, it's easy enough
> > to make it handle endian-ness exactly as other virtio 1.0 devices: what
> > we gain
On Wed, 3 Dec 2014 20:53:45 +0900
SeongJae Park wrote:
> Documentation/cgroups/cpusets.txt | 6 +++---
> Documentation/cgroups/memory.txt | 8
> 2 files changed, 7 insertions(+), 7 deletions(-)
I applied patch 1 to my docs tree, but this one doesn't apply. Which
kernel did you base
Richard Weinberger writes:
> Am 03.12.2014 um 13:58 schrieb Harald Geyer:
> > Richard Weinberger writes:
> >> Currently the driver uses pr_* and dev_* functions.
> >> Change all logging functions to dev_* style to be consistent
> >> and have the correct device prefix in all messages.
> >
> > Yes,
On 12/02/2014 09:26 AM, Kevin Hilman wrote:
Doug Anderson writes:
Hi,
On Mon, Dec 1, 2014 at 2:08 PM, Doug Anderson wrote:
Hi,
On Mon, Dec 1, 2014 at 11:51 AM, Kevin Hilman wrote:
Chris Zhong writes:
devices, since we still lack power_domain driver, so the other power rail
of rk3288
On Wed, Dec 3, 2014 at 2:50 AM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> After commit b2b49ccbdd54 (PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is
> selected) PM_RUNTIME is always set if PM is set, so #ifdef blocks
> depending on CONFIG_PM_RUNTIME may now be changed to depend on
>
A patch to the slicoss.c file to fix some of the long line issues found by the
checkpath.pl tool
Signed-off-by: Sean Cleator
---
drivers/staging/slicoss/slicoss.c | 39 ++-
1 file changed, 26 insertions(+), 13 deletions(-)
diff --git
Minimal implementation for KMX61 6-axis accelerometer/magnetometer. It exports
raw accel/magn readings together with scale and sampling frequency.
This driver uses two IIO devices one for accelerometer and one for magnetometer.
Datasheet will be available at:
We use WUFE (Wake Up from Sleep Engine) and BTSE (Back to Sleep Engine)
to detect general motion input.
Signed-off-by: Daniel Baluta
---
drivers/iio/imu/kmx61.c | 433 +++-
1 file changed, 426 insertions(+), 7 deletions(-)
diff --git
From: lyz
This patche to add a generic PHY driver for ROCKCHIP usb PHYs,
currently this driver can support RK3288. The RK3288 SoC have
three independent USB PHY IPs which are all configured through a
set of registers located in the GRF (general register files)
module. This driver powered off
From: lyz
Add a driver for the Rockchip SoC internal USB2.0 PHY.
This driver currently support RK3288.
Signed-off-by: lyz
---
.../devicetree/bindings/phy/rockchip-usb-phy.txt | 17 ++
drivers/phy/Kconfig| 7 +
drivers/phy/Makefile
Per sensor state (ACTIVE/STANDBY) is saved in driver's
private data (acc_stby/mag_stby) and restored when
resume is called.
Signed-off-by: Daniel Baluta
---
drivers/iio/imu/kmx61.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/drivers/iio/imu/kmx61.c
Signed-off-by: Daniel Baluta
---
drivers/iio/imu/kmx61.c | 59 +
1 file changed, 59 insertions(+)
diff --git a/drivers/iio/imu/kmx61.c b/drivers/iio/imu/kmx61.c
index 5b44371..893f7c8 100644
--- a/drivers/iio/imu/kmx61.c
+++
Populate the PM domains from DT, and provide support to hook up devices
to their respective PM domain.
The always-on power area (e.g. C5 on r8a7740) is created as a PM domain
without software control, to allow Run-Time management of module clocks
for hardware blocks inside this area.
Special
Add a device node for the System Controller, with subnodes that
represent the hardware power area hierarchy.
Hook up all devices to their respective PM domains.
Add a minimal device node for the Coresight-ETM hardware block, and hook
it up to the D4 PM domain, so the R-Mobile System Controller
For code that deals with cpuid, this makes things a bit more readable.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/cpuid.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c
index d82204ac555e..2c561dba81c0 100644
---
If CONFIG_PM_RUNTIME is not set, the clocks must be enabled before the
devices can be used.
Currently these clocks are enabled by the !CONFIG_PM_RUNTIME version of
pm_clk_notify, activated by the hack in drivers/sh/pm_runtime.c, but
this will go away soon (at least for DT).
On detach, disabling
Hi Simon, Magnus,
This patch series enables DT support for PM domains on Renesas R-Mobile SoCs.
Currently it's limited to R-Mobile A1 (r8a7740), but given the similarity of
the SYSC System-Controller on the various SH-Mobile/R-Mobile SoCs, and the
abstraction of PM domains in DT, it
601 - 700 of 2110 matches
Mail list logo
