On Wed, Feb 19, 2014 at 07:40:36AM -0800, Andi Kleen wrote:
> > > [ C(DTLB) ] = {
> > > [ C(OP_READ) ] = {
> > > [ C(RESULT_ACCESS) ] = 0x81d0, /*
> > > MEM_UOP_RETIRED.ALL_LOADS */
> > > [ C(RESULT_MISS) ] = 0x0108, /*
> > >
Currently the we display all detected features/libraries
by following rules:
- if one of the features is missing
- if it's build from clean tree
This patch changes changes this behavior in several ways.
- We no longer display all detected features, only detected
libraries are displayed by
Adding dump of interesting build directories to the
make VF=1 output.
$ make VF=1
BUILD: Doing 'make -j4' parallel build
Auto-detecting system features:
... dwarf: [ on ]
... glibc: [ on ]
... gtk2: [ on
Adding libdw DWARF post unwind support, which is part
of elfutils-devel/libdw-dev package from version 0.158.
The new code is contained in unwin-libdw.c object, and
implements unwind__get_entries unwind interface function.
New Makefile variable NO_LIBDW_DWARF_UNWIND was added to
control its
Hi,
On Tue, 2014-02-18 at 21:31 +0300, Sergei Shtylyov wrote:
> On 02/18/2014 08:14 PM, Ivan T. Ivanov wrote:
>
> >>> From: "Ivan T. Ivanov"
>
> >>> Allows controller to be specified via device tree.
> >>> Pass PHY phandle specified in DT to core driver.
>
> >>> Signed-off-by: Ivan T.
On 02/19/2014 06:06 AM, Fengguang Wu wrote:
Hi Dirk,
FYI, we noticed the below changes on commit
1abc4b20b85b42e8573957e54b193385cf48b0d6
("cpufreq / intel_pstate: remove idle time and duration from sample and
calculations"):
This commit was a LONG time ago. How does this compare to the
Hi,
On Tue, 2014-02-18 at 13:26 -0800, Courtney Cavin wrote:
> On Tue, Feb 18, 2014 at 02:21:19PM +0100, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
> >
> > Document device tree binding information as required by
> > the Qualcomm USB controller.
> >
> > Signed-off-by: Ivan T. Ivanov
>
Define the main clock frequency for the new main clock node in
at91sam9rlek.dts
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/at91sam9rlek.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/at91sam9rlek.dts
b/arch/arm/boot/dts/at91sam9rlek.dts
index
at91sam9rl now has a device tree, add it to the at91_dt_defconfig.
Signed-off-by: Alexandre Belloni
---
arch/arm/configs/at91_dt_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/at91_dt_defconfig
b/arch/arm/configs/at91_dt_defconfig
index
> > [ C(DTLB) ] = {
> > [ C(OP_READ) ] = {
> > [ C(RESULT_ACCESS) ] = 0x81d0, /* MEM_UOP_RETIRED.ALL_LOADS
> > */
> > [ C(RESULT_MISS) ] = 0x0108, /*
> > DTLB_LOAD_MISSES.CAUSES_A_WALK */
> > },
Actually I tested on the wrong system earlier,
On 02/19/2014 04:27 PM, Steven Rostedt wrote:
> Hmm, I wonder if this is because msleep() sets the tasks state to
> TASK_UNINTERRUPTIBLE, and hrtimer_nanosleep sets it to
> TASK_INTERRUPTIBLE.
No, it is because freezable_schedule() is called via do_nanosleep() in
hrtimer call path and msleep()
On Tue, Feb 18, 2014 at 03:11:59PM -0800, Dave Hansen wrote:
> I noticed that perf's dTLB-load-misses even t isn't working on my
> Ivybridge system:
>
> > Performance counter stats for 'system wide':
> >
> > 0 dTLB-load-misses
> >
Since txe use doorbell and not circular buffer
we have to cheat in write slot counting, txe always consume all the
slots upon write. In order for it to work we need to track
slots using mei_hbuf_empty_slots() instead of tracking it in mei layer
Signed-off-by: Tomas Winkler
---
On 02/19/2014 10:22 AM, Boris Ostrovsky wrote:
On 02/19/2014 05:15 AM, Alexander Gordeev wrote:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range()
> +config I2C_IMC
> + tristate "Intel iMC (LGA 2011) SMBus Controller"
> + depends on PCI && X86
> + select I2C_DIMM_BUS
> + help
> + If you say yes to this option, support will be included for the Intel
> + Integrated Memory Controller SMBus host controller interface.
On Wednesday, February 19, 2014 01:46:39 PM Jiang Liu wrote:
> Hi Rafael,
> We have following code to deal with existing users.
> +#ifdef ACPI_HOTPLUG_OST
> +#define acpi_evaluate_hotplug_ost acpi_evaluate_ost
Well, I'd very much prefer the users to be updated.
> +#else
>
While running Documentation/watchdog/src/watchdog-simple.c
and quiting by Ctrl-C, fallowing error is displayed:
mei_me :00:16.0: wd: stop failed to complete ret=-512.
The whatchdog core framework is not able to propagate
-ESYSRESTART or -EINTR. Also There is no much sense in
restarting the
Add reduce credits to wd_send to remove code
repetition and simplify error handling
Signed-off-by: Tomas Winkler
Signed-off-by: Alexander Usyskin
---
drivers/misc/mei/interrupt.c | 7 +++---
drivers/misc/mei/wd.c| 52 +++-
2 files changed, 30
A client has to acquire host buffer
before writing, we add lock like wrapper
to replace the code snippet
if (dev->hbuf_is_ready)
dev->hbuf_is_ready = false;
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/amthif.c| 7 +-
drivers/misc/mei/client.c| 56
From: Alexander Usyskin
1. Propagate ENOTTY to user space if the client is not present
in the system
2. Use ETIME consistently on timeouts
3. Return EIO on write failures
4. Return ENODEV on recoverable device failures such as resets
Signed-off-by: Alexander Usyskin
Signed-off-by: Tomas
On Wed, Feb 19, 2014 at 03:23:36PM +, Lee Jones wrote:
> Since when has maintaining core code been the responsibility of the
> leaf driver developers? If you're aware that the core code is
> sub-standard then it's you who should be fixing it.
No, there isn't this clear divide between core and
On Tue, Feb 18, 2014 at 09:23:29PM +0100, Thomas Gleixner wrote:
> On Tue, 18 Feb 2014, Jason Cooper wrote:
>
> > Thomas,
> >
> > Here is a small round of fixes for irq-orion.c. They've been in -next
> > for over a week. Please pull.
> >
> > We have a set of watchdog changes depending on this
Add a device tree for the at91sam9rl-ek. For now it supports:
- MMC
- dbgu
- usart1
- watchdog
- nand
- leds
- buttons
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/Makefile | 2 +
arch/arm/boot/dts/at91sam9rlek.dts | 151 +
2 files
Define at91sam9rl clocks in at91sam9rl dtsi file.
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/at91sam9rl.dtsi | 231 +-
1 file changed, 229 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/at91sam9rl.dtsi
On Wed, 19 Feb 2014 08:54:57 -0600, Rob Herring wrote:
> On Wed, Feb 19, 2014 at 8:14 AM, Grant Likely wrote:
> > From: Kevin Hao
> >
> > In the current implementation of __of_match_node(), it will compare
> > each given match entry against all the node's compatible strings
> > with
On Wed, 19 Feb 2014 12:53:53 +0100
Sebastian Andrzej Siewior wrote:
> Since we replaced msleep() by hrtimer I see now and then (rarely) this:
>
> | [] Waiting for /dev to be fully populated...
> | =
> | [ BUG: udevd/229 still has locks held! ]
> |
From: Boris BREZILLON
This patch prepare the transition to common clk for sam9 dt boards by
replacing the timer init callback.
Clocks registration cannot be done in early init callback (as formerly done
by the old clk implementation) because it requires dynamic allocation
which is not ready yet
This adds preliminary DT support for the at91sam9rl.
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/at91sam9rl.dtsi | 628 ++
arch/arm/mach-at91/at91sam9rl.c | 16 +
2 files changed, 644 insertions(+)
create mode 100644
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-at91/Kconfig b/arch/arm/mach-at91/Kconfig
index 4f0e800e7e71..7013b7b66a1e 100644
--- a/arch/arm/mach-at91/Kconfig
+++ b/arch/arm/mach-at91/Kconfig
@@ -137,7 +137,6 @@
This series adds DT support for the at91sam9rl SoC, then the at91sam9rl-ek
evaluation board.
While the at91sam9rl dtsi should be almost complete (still missing LCD and
touchscreen bits). The at91sam9rlek DT now support the following tested
features:
- MMC
- dbgu
- usart1
- watchdog
- nand
-
This patch encloses sam9rl old clk registration in
#if defined(CONFIG_OLD_CLK_AT91)/#endif sections.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/at91sam9rl.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-at91/at91sam9rl.c
On Wed, Feb 19, 2014 at 11:59:08AM +0100, Torvald Riegel wrote:
> On Tue, 2014-02-18 at 14:58 -0800, Paul E. McKenney wrote:
> > On Tue, Feb 18, 2014 at 10:40:15PM +0100, Torvald Riegel wrote:
> > > xagsmtp4.20140218214207.8...@vmsdvm9.vnet.ibm.com
> > > X-Xagent-Gateway: vmsdvm9.vnet.ibm.com
On Tue, 18 Feb 2014, Torvald Riegel wrote:
On Tue, 2014-02-18 at 22:40 +0100, Peter Zijlstra wrote:
On Tue, Feb 18, 2014 at 10:21:56PM +0100, Torvald Riegel wrote:
Well, that's how atomics that aren't volatile are defined in the
standard. I can see that you want something else too, but that
On Thu, Feb 13, 2014 at 06:21:38PM +0200, Ivan T. Ivanov wrote:
> Qualcomm Universal Peripheral (QUP) core is an AHB slave that
> provides a common data path (an output FIFO and an input FIFO)
> for serial peripheral interface (SPI) mini-core. SPI in master
> mode supports up to 50MHz, up to four
Hi All,
I read the code in do_anonymous_page of the latest linux kernel.
I am pretty confused how pte_mkspecial to make the zero-page COW on
x86 architecture
static int do_anonymous_page(struct mm_struct *mm, struct vm_area_struct *vma,
unsigned long address, pte_t *page_table,
> > I think that's a pretty unfair ask. I could understand if the
> > patch(es) didn't apply, or were hindered by the new API change, but I
> > do not believe that is the case?
>
> Let me make it very clear to you. If you want your code in, you help
> maintaining the larger code base. I'm
On 02/19/2014 05:15 AM, Alexander Gordeev wrote:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
On Wed, Feb 19, 2014 at 12:49:33PM +0900, SeongJae Park wrote:
> 2 debugging messages were just commented out for normal case. Let them
> be activated on debug mode without explicit code modification.
Are you sure this doesn't just always send the messages to the debug log
all the time now?
On Feb 18, 2014, at 6:06 PM, Stephen Boyd wrote:
> On 02/10/14 15:23, Kumar Gala wrote:
>>
>> Kumar Gala (6):
>> ARM: dts: msm: split out msm8660 and msm8960 soc into dts include
>> ARM: msm: kill off hotplug.c
>> clocksource: qcom: Move clocksource code out of mach-msm
>>
Thomas! Hi!
On Tue, Feb 18, 2014 at 09:51:31PM +0100, Thomas Gleixner wrote:
> On Mon, 17 Feb 2014, Jason Cooper wrote:
> > On Fri, Feb 07, 2014 at 01:08:36PM -0500, Jason Cooper wrote:
> > > On Tue, Feb 04, 2014 at 10:30:53PM +0100, Thomas Gleixner wrote:
> > > > On Tue, 4 Feb 2014, Jason
Hi,
On 17.02.2014 10:05, Krzysztof Kozlowski wrote:
Add document describing device tree bindings for MAX14577 MFD
drivers: MFD core, extcon, regulator and charger.
Both MAX14577 and MAX77836 chipsets are documented.
Signed-off-by: Krzysztof Kozlowski
Cc: Kyungmin Park
Cc: Tomasz Figa
Cc:
On Fri, Dec 20, 2013 at 05:45:13PM -0800, Andy Lutomirski wrote:
> Add i2c_scan_dimm_bus to declare that a particular i2c_adapter
> contains DIMMs. This will probe (and autoload modules!) for useful
> SMBUS devices that live on DIMMs. i2c_imc calls it.
Hmm, after thinking about it for a while
Hello.
On 18-02-2014 14:11, Alexander Gordeev wrote:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Hi,
On 17.02.2014 10:05, Krzysztof Kozlowski wrote:
Add document describing device tree bindings for MAX14577 MFD
drivers: MFD core, extcon, regulator and charger.
Both MAX14577 and MAX77836 chipsets are documented.
Signed-off-by: Krzysztof Kozlowski
Cc: Kyungmin Park
Cc: Tomasz Figa
Cc:
On Wed, Feb 19, 2014 at 03:20:07PM +0100, Ulf Hansson wrote:
> Also note that, Russell has already applied the corresponding part in
> the amba bus (patch 1)
Why would this depend on an AMBA patch and if it does surely the two
need to be merged together somehow?
signature.asc
Description:
On Wed, Feb 19, 2014 at 03:19:00PM +0100, Krzysztof Kozlowski wrote:
> As I understand the suspend mode (correct me if I'm wrong), the
> regulator core during suspend to mem:
> 1. Calls suspend_set_state().
> 2. rstate->disabled is true so the ops->set_suspend_disable() is called.
> 3. The
Hello, Lee.
On Wed, Feb 19, 2014 at 03:01:21PM +, Lee Jones wrote:
> I think that's a pretty unfair ask. I could understand if the
> patch(es) didn't apply, or were hindered by the new API change, but I
> do not believe that is the case?
Let me make it very clear to you. If you want your
> > Can I do this as a subsequent patch though? The current patch fits
> > neatly onto our internal stable kernel (currently v3.10). The added
> > work will require back-porting Hans' patch-set, which has not yet
> > reached Mainline.
>
> Hmm I'll apply Hans' patchset pretty soon and we still
On Wed, Feb 19, 2014 at 8:14 AM, Grant Likely wrote:
> From: Kevin Hao
>
> In the current implementation of __of_match_node(), it will compare
> each given match entry against all the node's compatible strings
> with of_device_is_compatible().
>
> To achieve multiple compatible strings per node
On Wed, 19 Feb 2014 14:13:54 +0900
Daeseok Youn wrote:
> >From 6297aabeff748777b520cc0ee835af0a3ddc79e2 Mon Sep 17 00:00:00 2001
> From: Daeseok Youn
> Date: Wed, 19 Feb 2014 10:49:12 +0900
> Subject: [PATCH] atm: solos-pci: make solos_bh() as static
>
> sparse says:
>
>
Hi Tim,
On Tue, 2014-02-18 at 22:21 -0800, Tim Bird wrote:
> Ivan,
>
> I'm having tremendous problems getting this driver to initialize. For
> some reason, I can't get the driver to actually transition the
> hardware into peripheral mode. At first I was getting a lot of probe
> deferrals,
On Wed, 19 Feb 2014 14:11:15 +0900
Daeseok Youn wrote:
> >From 932e928d53b1e588dc17019e7f9fa7a61b8b7468 Mon Sep 17 00:00:00 2001
> From: Daeseok Youn
> Date: Wed, 19 Feb 2014 10:35:41 +0900
> Subject: [PATCH] atm: ambassador: use NULL instead of 0 for pointer
>
> sparse says:
>
>
On Wed, 19 Feb 2014 14:12:46 +0900
Daeseok Youn wrote:
> >From c320d2ea1ed51c88255c33a50c74fa3598ab7be6 Mon Sep 17 00:00:00 2001
> From: Daeseok Youn
> Date: Wed, 19 Feb 2014 10:10:11 +0900
> Subject: [PATCH] atm: nicstar: use NULL instead of 0 for pointer
>
> sparse says:
>
>
19.02.2014 18:50, J. Bruce Fields пишет:
On Wed, Feb 19, 2014 at 02:26:33PM +0400, Stanislav Kinsbursky wrote:
18.02.2014 19:44, J. Bruce Fields пишет:
On Tue, Feb 18, 2014 at 07:19:31PM +0400, Stanislav Kinsbursky wrote:
18.02.2014 02:19, J. Bruce Fields пишет:
On Sat, Feb 15, 2014 at
L: lines are for the email addresses of traditional mailing lists.
W: lines are for URLs.
Convert two L: misuses to W: links.
Signed-off-by: Joe Perches
Reported-by: Paul Bolle
---
diff --git a/MAINTAINERS b/MAINTAINERS
index 60a5f85..adfbf3f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@
css_offline callback exported by the cgroup core is not intended to get
rid of all the charges but rather to get rid of cached charges for the
soon destruction. For the memory controller we have 2 different types of
"cached" charges which prevent from the memcg destruction (because they
pin memcg
On Wed, Feb 19, 2014 at 02:26:33PM +0400, Stanislav Kinsbursky wrote:
> 18.02.2014 19:44, J. Bruce Fields пишет:
> >On Tue, Feb 18, 2014 at 07:19:31PM +0400, Stanislav Kinsbursky wrote:
> >>18.02.2014 02:19, J. Bruce Fields пишет:
> >>>On Sat, Feb 15, 2014 at 09:51:20AM +0800, Weng Meiling wrote:
> Please try to avoid this sort of misdirected yelling, it's not helping
I don't see any misdirected yelling
> anything to complain that people are following the recommendations of
> the maintainer or to demand that this somehow gets hacked around in
> arch/ when we're trying to convince all the
On Wed, 2014-02-19 at 11:26 +0100, Paul Bolle wrote:
> Andrew, Joe,
>
> (You two touched this script the most, it seems.)
>
> The MAINTAINERS entry for the "TARGET SUBSYSTEM" uses an http address
> for one of its L: lines. The "DC395x SCSI driver" does that too. This
> shows up as a useless line
On Tue, 2014-02-18 at 14:14 -0800, Linus Torvalds wrote:
> On Tue, Feb 18, 2014 at 1:21 PM, Torvald Riegel wrote:
> >>
> >> So imagine that you have some clever global optimizer that sees that
> >> the program never ever actually sets the dirty bit at all in any
> >> thread, and then uses that
On Feb 19, 2014, at 9:13, Trond Myklebust
wrote:
> Hi Linus,
>
> The following changes since commit b28a960c42fcd9cfc987441fa6d1c1a471f0f9ed:
>
> Linux 3.14-rc2 (2014-02-09 18:15:47 -0800)
>
> are available in the git repository at:
>
>
On 19/02/14 09:52, Ian Campbell wrote:
On Tue, 2014-02-18 at 13:02 -0800, Luis R. Rodriguez wrote:
On Sun, Feb 16, 2014 at 10:57 AM, Stephen Hemminger
wrote:
On Fri, 14 Feb 2014 18:59:37 -0800
"Luis R. Rodriguez" wrote:
From: "Luis R. Rodriguez"
It doesn't make sense for some interfaces
> > The patch 'mei: set client's read_cb to NULL when flow control fails'
> > (accb884b32e82f943340688c9cd30290531e73e0) Which is in
> > char-misc-linus, still haven't make it to the upstream...I thought it
> > would be in rc3 already.
>
> No, you sent it too late for that.
>
> > I can either
Due to the available runtime PM callbacks for CONFIG_PM, we are now
able to put the device into complete low power state at system suspend.
Previously only the resources controlled by the driver were put into
low power state at system suspend. Both the amba bus and a potential
power domain were
Hi Hanjun,
On 18/02/14 16:23, Hanjun Guo wrote:
> Get apic id from MADT or _MAT method is not implemented on arm/arm64,
> and ACPI 5.0 introduces GIC Structure for it, so this patch introduces
> map_gic_id() to get apic id followed the ACPI 5.0 spec.
>
> Signed-off-by: Hanjun Guo
> ---
>
On Wed, Feb 19, 2014 at 01:44:41PM +0100, Krzysztof Kozlowski wrote:
> I want to push whole MAX77836 patchset through Lee Jones' MFD tree and I
> still need acks from power and regulator subsystems.
> I would appreciate if you could find time to look at these patches and
> let me know your
On Wed, Feb 19, 2014 at 09:58:08AM +, Winkler, Tomas wrote:
>
> >
> > This patch fails to apply to my char-misc-next branch (I've pulled in
> > 3.14-rc3 into this branch now):
> > checking file drivers/misc/mei/amthif.c
> > checking file drivers/misc/mei/client.c
> > Hunk #4
On Wed, Feb 19, 2014 at 12:32:02PM +0200, Ivan Khoronzhuk wrote:
> >> + aemif->clk = devm_clk_get(dev, NULL);
> >> + if (IS_ERR(aemif->clk)) {
> >> + dev_err(dev, "cannot get clock 'aemif'\n");
> >> + return PTR_ERR(aemif->clk);
> > No freeing memory?
>
> There is no need to
On Wednesday 19 February 2014 01:19 AM, Mike Turquette wrote:
> Quoting Santosh Shilimkar (2014-02-10 12:26:49)
>> Mike,
>>
>> Can you please look at these couple of keystone clock fixes ?
>> Without these, we have seen some random kernel crashes. I
>> have included the dts fix since both fixes
From: Borislav Petkov
Let's use the more common "unusable".
Cc: Eric Biederman
Cc: ke...@lists.infradead.org
Signed-off-by: Borislav Petkov
---
include/linux/kexec.h | 2 +-
kernel/kexec.c| 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/linux/kexec.h
On 4 February 2014 16:58, Ulf Hansson wrote:
> Convert to the SET_PM_RUNTIME_PM macro while defining the runtime PM
> callbacks. This means the callbacks becomes available for both
> CONFIG_PM_SLEEP and CONFIG_PM_RUNTIME, which is needed to handle the
> combinations of these scenarios.
>
> Cc:
From: "Ivan T. Ivanov"
Accessing GCC on MSM8974 trough < GCC_XO_CLK> lead to NULL
pointer dereference. Fix this.
Signed-off-by: Ivan T. Ivanov
---
drivers/clk/qcom/gcc-msm8974.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/clk/qcom/gcc-msm8974.c
On Wed, 2014-02-19 at 13:08 +0900, Mark Brown wrote:
> On Tue, Feb 18, 2014 at 09:12:09AM +0100, Krzysztof Kozlowski wrote:
> > On Tue, 2014-02-18 at 09:35 +0900, Mark Brown wrote:
>
> > > I don't understand the above? Are you saying that suspend mode actually
> > > turns off the regulator or
Adds a selftest function for the of_match_node function. of_match_node
is supposed to handle precedence for the compatible property as well as
the name and device_type values. This patch adds some test case data and
a function that makes sure each test node matches against the correct
entry of an
From: Kevin Hao
This reverts commit 06b29e76a74b2373e6f8b5a7938b3630b9ae98b2.
As pointed out by Grant Likely, we should also take the type and name
into account when searching the best compatible match. That means the
match with compatible, type and name should be better than the match
just with
Hi all,
I've taken Kevin's latest rework and done even more rework on it. :-) I
didn't quite like how it was looking so I rolled his scoring code
directly into __of_device_is_compatible() so that the function always
returns a score in a way that is still compatible with the existing
users (ie.
From: Kevin Hao
In the current implementation of __of_match_node(), it will compare
each given match entry against all the node's compatible strings
with of_device_is_compatible().
To achieve multiple compatible strings per node with ordering from
specific to generic, this requires given
On 10 February 2014 13:51, Mark Brown wrote:
> On Mon, Feb 10, 2014 at 01:33:50PM +0100, Ulf Hansson wrote:
>> On 4 February 2014 20:16, Mark Brown wrote:
>
>> > This seems like a fairly hideous thing to be having to open code in an
>> > individual driver, it all looks generic and like something
The testcase data is usable by any platform. This patch moves it into
the drivers/of directory so it can be included by any architecture.
Using the test cases requires manually adding #include
to the end of the boards .dtsi file and enabling CONFIG_OF_SELFTEST. Not
pretty though. A useful
2014-02-19 21:38 GMT+09:00 Sergei Shtylyov :
> Hello.
>
>
> On 19-0202014 9:07, Daeseok Youn wrote:
>
>> From 2a428e5e45bca3fc38fad17b9e2e14c5e6514ca0 Mon Sep 17 00:00:00 2001
>> From: Daeseok Youn
>> Date: Wed, 19 Feb 2014 10:56:37 +0900
>> Subject: [PATCH] ata: libahci: make
On Wednesday 19 February 2014 08:40 AM, Ivan Khoronzhuk wrote:
> Add bindings for TI Async External Memory Interface (AEMIF) controller.
>
> The Async External Memory Interface (EMIF16/AEMIF) controller is intended to
> provide a glue-less interface to a variety of asynchronous memory devices
Hi Linus,
The following changes since commit b28a960c42fcd9cfc987441fa6d1c1a471f0f9ed:
Linux 3.14-rc2 (2014-02-09 18:15:47 -0800)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-3.14-4
for you to fetch changes up to
On 2014/2/19 18:12, Maarten Lankhorst wrote:
> op 19-02-14 05:53, Jiang Liu schreef:
>> On some platforms, ACPI _DSM method (nouveau_op_dsm_muid, function 0)
>> has special requirements on the fourth parameter, which is different
>> from ACPI specifications. So revert to the private
Hi Linus,
The following changes since commit 38dbfb59d1175ef458d006556061adeaa8751b72:
Linus 3.14-rc1 (2014-02-02 16:42:13 -0800)
are available in the git repository at:
git://git.linaro.org/people/lee.jones/mfd.git tags/mfd-fixes-3.14-1
for you to fetch changes up to
Intel Baytrail I2C controllers can be enumerated from PCI as well as from
ACPI. In order to support this add the Baytrail PCI IDs to the driver.
Signed-off-by: Mika Westerberg
---
Changes to previous version:
* Removed "-%d" from the adapter name.
drivers/i2c/busses/i2c-designware-pcidrv.c |
Hi Dirk,
FYI, we noticed the below changes on commit
1abc4b20b85b42e8573957e54b193385cf48b0d6
("cpufreq / intel_pstate: remove idle time and duration from sample and
calculations"):
test case: snb-drag/sysbench/fileio/600s-100%-1HDD-btrfs-64G-1024-seqrd-sync
559f56c70fc90bd
Hello, Lee.
On Wed, Feb 19, 2014 at 08:30:25AM +, Lee Jones wrote:
> Can I do this as a subsequent patch though? The current patch fits
> neatly onto our internal stable kernel (currently v3.10). The added
> work will require back-porting Hans' patch-set, which has not yet
> reached Mainline.
On Wed, Feb 19, 2014 at 02:51:36PM +0100, Michal Simek wrote:
> On 02/19/2014 01:17 PM, Mark Brown wrote:
> > Like I said I've never seen the user you're adding for the regmap API so
> > I've no particular opinion on it.
> 2/2 is the code where I would like to use this when clk subsystem
> start
Hi Philipp,
On 02/07/2014 01:54 PM, srinivas kandagatla wrote:
Hi Philipp,
Thankyou for looking at the patches.
On 05/02/14 09:28, Philipp Zabel wrote:
Hi Srinivas,
...
the patchset looks good to me for the soft resets. But for the powerdown
bits I am wondering whether the reset
On Tue, Feb 18, 2014 at 04:11:01PM +0530, Sachin Kamat wrote:
> Propagate the error value returned by the function instead.
Applied, thanks.
signature.asc
Description: Digital signature
On 02/17/2014 04:56 PM, Maarten Lankhorst wrote:
> This allows reservation objects to be used in dma-buf. it's required
> for implementing polling support on the fences that belong to a dma-buf.
>
> Signed-off-by: Maarten Lankhorst
> Acked-by: Mauro Carvalho Chehab
> #drivers/media/v4l2-core/
On Tue, Feb 18, 2014 at 10:09:43AM +, Etched Pixels wrote:
> Mark Brown wrote:
> > It's a very real problem which affects actual kernels that distro style
> > users are building.
> Only because you persist in trying to keep the old static minor
> numbers even though they are not needed by
On 02/17/2014 04:57 PM, Maarten Lankhorst wrote:
> Android syncpoints can be mapped to a timeline. This removes the need
> to maintain a separate api for synchronization. I've left the android
> trace events in place, but the core fence events should already be
> sufficient for debugging.
>
> v2:
On 02/19/2014 01:17 PM, Mark Brown wrote:
> On Wed, Feb 19, 2014 at 12:44:50PM +0100, Michal Simek wrote:
>> On 02/19/2014 12:41 PM, Lee Jones wrote:
>
>>> I believe you were waiting for Arnd and/or Mark to comment.
>
>> yes on Arnd because Mark already applied that regmap part.
>> But of course
2014-02-19 8:27 GMT+09:00 Dave Jones :
> On Tue, Feb 18, 2014 at 02:32:02PM -0800, David Rientjes wrote:
> > On Tue, 18 Feb 2014, Dave Jones wrote:
> >
> > > /proc/self/make-it-fail is a boolean, but accepts any number, including
> > > negative ones. Change variable to unsigned, and cap upper
On Mon, Feb 10, 2014 at 05:44:17PM +, Mark Rutland wrote:
> Hi,
>
> I've been working on adding support for heterogeneous pmus (as would be found
> in big.LITTLE systems) to the arm perf backend, and in the process of doing so
> I've noticed a few issues in the core perf code that would be
Add bindings for TI Async External Memory Interface (AEMIF) controller.
The Async External Memory Interface (EMIF16/AEMIF) controller is intended to
provide a glue-less interface to a variety of asynchronous memory devices like
ASRA M, NOR and NAND memory. A total of 256M bytes of any of these
These patches introduce Async External Memory Interface (EMIF16/AEMIF)
controller driver for Davinci/Keystone archs.
For more informations see documentation:
Davinci DM646x - http://www.ti.com/lit/ug/sprueq7c/sprueq7c.pdf
OMAP-L138 - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf
Kestone -
Add new AEMIF driver for EMIF16 Texas Instruments controller.
The EMIF16 module is intended to provide a glue-less interface to
a variety of asynchronous memory devices like ASRA M, NOR and NAND
memory. A total of 256M bytes of any of these memories can be
accessed at any given time via 4 chip
In the casee of your ACPI-enabled AMBA device I believe the BIOS, which
provides the ACPI tables, is expected to set the interrupt type.
On February 19, 2014 4:07:09 AM PST, Thomas Gleixner wrote:
>On Wed, 19 Feb 2014, carl peng wrote:
>> At last, the device will be connected to AMBA bus, so
401 - 500 of 1390 matches
Mail list logo
