On Thu, Jun 12, 2014 at 09:37:16AM +0200, Peter Zijlstra wrote:
> On Thu, Jun 12, 2014 at 04:00:11PM +0900, HATAYAMA Daisuke wrote:
> > Also, I checked cpuid on the system with Neharlem processor where I
> > have never seen CondChg bit is set.
> >
> > [root@localhost ~]# ./cpuid -r
> > CPU 0:
> >
On Mon, Jun 16, 2014 at 04:13:29PM +0100, Will Deacon wrote:
> MSIs look just like memory accesses made by the device, so the SMMU
> will translate them to point at the GIC ITS (doorbell). The ITS then
> has tables to work out how to route the MSI.
>
> So, if IOMMU_CAP_INTR_REMAP is simply
On 6/16/2014 10:14 AM, Nick Krause wrote:
>From what I know yes so I would close the bug at the the link in
my previous email and just void my patch.
Cheers Nick
We shouldn't be kfree-ing an skb anyway. Should use kfree_skb().
There is still a leak if skb is non-null and the skb is non
On Thu, Jun 12, 2014 at 04:12:18PM -0600, Alex Williamson wrote:
> Alex Williamson (3):
> iommu: Add sysfs support for IOMMUs
> iommu/intel: Make use of IOMMU sysfs support
> iommu/amd: Add sysfs support
I like the general approach. But why do you only enable the x86 iommus?
>From what I know yes so I would close the bug at the the link in
my previous email and just void my patch.
Cheers Nick
On Mon, Jun 16, 2014 at 11:12 AM, Levente Kurusa wrote:
> On 06/16/2014 05:08 PM, Nicholas Krause wrote:
>>
>> Signed-off-by: Nicholas Krause
>> ---
>>
On Thu, Jun 05, 2014 at 06:03:11PM +0100, Antonios Motakis wrote:
> The ARM SMMU supports the IOMMU_NOEXEC protection flag. Add the
> corresponding IOMMU capability.
>
> Signed-off-by: Antonios Motakis
> ---
> drivers/iommu/arm-smmu.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git
On Mon, Jun 16, 2014 at 03:53:44PM +0100, Joerg Roedel wrote:
> On Sun, Jun 08, 2014 at 12:31:29PM +0200, Christoffer Dall wrote:
> > On Thu, Jun 05, 2014 at 07:03:12PM +0200, Antonios Motakis wrote:
> > > With an ARM SMMU, interrupt remapping should always be safe from the
> > > SMMU's point of
On 06/16/2014 05:08 PM, Nicholas Krause wrote:
Signed-off-by: Nicholas Krause
---
drivers/infiniband/hw/cxgb4/cm.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/infiniband/hw/cxgb4/cm.c b/drivers/infiniband/hw/cxgb4/cm.c
index f9477e2..2d56983 100644
---
On 2014-06-15 18:28, Hugh Dickins wrote:
On Sat, 14 Jun 2014, Fabian Frederick wrote:
Use GFP_NOFS instead of its definition.
Cc: Jens Axboe
Signed-off-by: Fabian Frederick
---
block/bio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/bio.c b/block/bio.c
index
The bug is open here https://bugzilla.kernel.org/show_bug.cgi?id=44631.
I would recommend closing it now as I seem to have fixed it.
Cheers Nick
On Mon, Jun 16, 2014 at 11:08 AM, Nicholas Krause wrote:
> Signed-off-by: Nicholas Krause
> ---
> drivers/infiniband/hw/cxgb4/cm.c | 8 +++-
> 1
Signed-off-by: Nicholas Krause
---
drivers/infiniband/hw/cxgb4/cm.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/infiniband/hw/cxgb4/cm.c b/drivers/infiniband/hw/cxgb4/cm.c
index f9477e2..2d56983 100644
--- a/drivers/infiniband/hw/cxgb4/cm.c
+++
On 6/16/2014 10:03 AM, Nicholas Krause wrote:
Signed-off-by: Nicholas Krause
---
drivers/infiniband/hw/cxgb4/cm.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/infiniband/hw/cxgb4/cm.c b/drivers/infiniband/hw/cxgb4/cm.c
index f9477e2..2d56983 100644
---
On Thu, Jun 05, 2014 at 06:03:09PM +0100, Antonios Motakis wrote:
> Exposing the XN flag of the SMMU driver as IOMMU_NOEXEC instead of
> IOMMU_EXEC makes it enforceable, since for IOMMUs that don't support
> the XN flag pages will always be executable.
>
> Signed-off-by: Antonios Motakis
> ---
>
Signed-off-by: Nicholas Krause
---
drivers/infiniband/hw/cxgb4/cm.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/infiniband/hw/cxgb4/cm.c b/drivers/infiniband/hw/cxgb4/cm.c
index f9477e2..2d56983 100644
--- a/drivers/infiniband/hw/cxgb4/cm.c
+++
Use netdev_* where applicable.
Signed-off-by: Stephan Gabert
Signed-off-by: Nicolas Pfeiffer
---
drivers/staging/wlags49_h2/wl_cs.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/wlags49_h2/wl_cs.c
b/drivers/staging/wlags49_h2/wl_cs.c
index
...
On Fri, Jun 13, 2014 at 9:02 PM, Eric W. Biederman
wrote:
> Rafael Tinoco writes:
>
>> Okay,
>>
>> Tests with the same script were done.
>> I'm comparing : master + patch vs 3.15.0-rc5 (last sync'ed rcu commit)
>> and 3.9 last bisect good.
>>
>> Same tests were made. I'm comparing the
On Mon, 16 Jun 2014, Peter Chen wrote:
> On Fri, Jun 13, 2014 at 10:19:36AM -0400, Alan Stern wrote:
> > On Fri, 13 Jun 2014, Peter Chen wrote:
> >
> > > OK, we can keep our g_xxx gadget driver just support the basic feature.
> > > But
> > > the bug that causes gadget driver load fail due to
Signed-off-by: Stephan Gabert
Signed-off-by: Nicolas Pfeiffer
---
drivers/staging/wlags49_h2/wl_cs.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/wlags49_h2/wl_cs.c
b/drivers/staging/wlags49_h2/wl_cs.c
index e658000..4239f0c 100644
---
On Mon, Jun 16, 2014 at 04:38:01PM +0200, Andi Kleen wrote:
> > I think this issue started when some of the Go developers questioned
> > why the kernel needed to provide a very complex interface--parsing an
> > ELF shared shared library--for very simple functionality--looking up
> > the address of
As mentioned in net/core/dev.c register_netdev() explicitly returns a
negative errno code on failure.
So in case of failure, one should rather test whether ret is negative
than just unlike 0.
Signed-off-by: Stephan Gabert
Signed-off-by: Nicolas Pfeiffer
---
drivers/staging/wlags49_h2/wl_cs.c
The appended patches fix up wl_cs.c from the wireless device driver wlags49
of Agere Systems Inc.
Most modifications resulted from checkpatch.pl.
Stephan Gabert (5):
staging/wlags49_h2: checkpatch: including instead of
staging/wlags49_h2: checkpatch: added spaces around equal sign
As warned by checkpatch.pl, one should use #include
instead of #include and #include
instead of #include .
Signed-off-by: Stephan Gabert
Signed-off-by: Nicolas Pfeiffer
---
drivers/staging/wlags49_h2/wl_cs.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Hereby the checkpatch message
ERROR: spaces required around that '=' (ctx:VxV)
gets resolved
and the neighboring equal signs are positioned in the same column.
Signed-off-by: Stephan Gabert
Signed-off-by: Nicolas Pfeiffer
---
drivers/staging/wlags49_h2/wl_cs.c | 10 +-
1 file
Hi Vince,
On 15/06/14 07:03, Vince Weaver wrote:
>
> Transition to using the new generic PERF_PMU_CAP_NO_INTERRUPT method for
> failing a sampling event when no PMU interrupt is available.
>
> Signed-off-by: Vince Weaver
> @@ -866,6 +856,15 @@ static int __init init_hw_perf_events(void)
>
On Thu, Jun 05, 2014 at 08:43:59AM +0800, Axel Lin wrote:
> of_find_node_by_name() walks the allnodes list, and can thus walk
> outside of the parent node. Use of_get_child_by_name() instead.
Applied, thanks.
signature.asc
Description: Digital signature
On Mon, Jun 16, 2014 at 07:08:50AM -0700, Ian Lance Taylor wrote:
> On Sun, Jun 15, 2014 at 7:36 PM, Andi Kleen wrote:
> >
> > I haven't looked into this in detail, but my initial assumption would
> > be that it wouldn't be useful to add new vdso interfaces just for Go.
> > After all would you
Il 16/06/2014 13:53, Nadav Amit ha scritto:
On 6/16/14, 2:09 PM, Paolo Bonzini wrote:
Il 16/06/2014 12:33, Nadav Amit ha scritto:
Do you get this if the input register has bit 31 set?
No. To be frank, the scenario may be considered a bit synthetic: the
guest assigns a value to a
On Mon, 2014-06-16 at 02:00PM +0900, Jongsung Kim wrote:
> On 06/13/2014 12:44 AM, Sören Brinkmann wrote:
> > Hi Jongsung,
>
> Hi Sören,
>
> > Does this interrupt need to be enabled? There is nothing checking
> > that bit and handling this IRQ in the handler, AFAICT. And you solve
> > this by
On 06/14/2014 05:09 PM, Fabian Frederick wrote:
> use mm.h definition
>
> Cc: Nathan Fontenot
> Cc: Marcelo Henrique Cerri
> Signed-off-by: Fabian Frederick
Acked-by: Nathan Fontenot
> ---
> drivers/crypto/nx/nx-842.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff
On Sun, Jun 08, 2014 at 12:31:29PM +0200, Christoffer Dall wrote:
> On Thu, Jun 05, 2014 at 07:03:12PM +0200, Antonios Motakis wrote:
> > With an ARM SMMU, interrupt remapping should always be safe from the
> > SMMU's point of view, as it is properly handled by the GIC.
> >
> > Signed-off-by:
On Mon, 16 Jun 2014, Jean Delvare wrote:
> As far as I know, the CS5535 and CS5536 chipsets are companions of the
> Geode series of processors, which are 32-bit only. So the CS5535
> drivers are not needed on x86-64, except for build testing purpose.
>
> This aligns the dependencies to what
On Mon, 16 Jun 2014, Jean Delvare wrote:
> As far as I know the Timberdale chip was only used as a companion for
> Intel Atom E600 series processors. As such, its drivers are only
> useful on X86_32.
>
> Signed-off-by: Jean Delvare
> Cc: Samuel Ortiz
> Cc: Lee Jones
> ---
> Patch already sent
Hi Alex,
On Thu, May 22, 2014 at 05:07:23PM -0600, Alex Williamson wrote:
> Alex Williamson (16):
> PCI: Add DMA alias iterator
> PCI: define pci_dev_flags as bit shifts
> PCI: quirk pci_for_each_dma_alias()
> PCI: quirk dma_alias_devfn for Ricoh devices
> PCI: quirk
On Mon, Jun 16, 2014 at 04:07:19PM +0200, Torsten Duwe wrote:
> > > TPM RNG is a crook ;-)
> >
> > I think the word you mean is "crock" (as in "crock of sh*t"?) :-)
>
> Actually, I was thinking of a crutch. Makes you walk slowly, but better
> than nothing. Seems I've bent the wrong tube.
Heh.
On Mon, 16 Jun 2014, Allen Yu wrote:
> On Sat, 14 Jun 2014, Alan Stern wrote:
>
> > > dev->power.is_suspended is set after core suspends device during system
> > suspend.
> > > This flag mostly means device is not operational (all I/O been
> > > quiesced, no more data read or write acceptible,
On Mon, Jun 16, 2014 at 04:29:15PM +0200, Michal Hocko wrote:
> > They're all in the mainline now.
>
> git grep CFTYPE_ON_ON_DFL origin/master didn't show me anything.
lol, it should have been CFTYPE_ONLY_ON_DFL.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe
Hi,
On Sun, Jun 15, 2014 at 03:29:40AM +, Paul Walmsley wrote:
> Hi,
>
> On Fri, 13 Jun 2014, Felipe Balbi wrote:
>
> > On Sat, Jun 14, 2014 at 02:57:32AM +, Paul Walmsley wrote:
> > > > > > > From: Sathya Prakash M R
> > > > > > >
> > > > > > > Add DSS hwmod data for AM43xx.
> > > >
> I think this issue started when some of the Go developers questioned
> why the kernel needed to provide a very complex interface--parsing an
> ELF shared shared library--for very simple functionality--looking up
> the address of a magic function. This approach has required special
> support not
On Mon, Jun 16, 2014 at 12:52:10PM +0200, Andreas Schwab wrote:
> Dan Carpenter writes:
> > Adding "--param allow-store-data-races=0" to the GCC options for the
> > kernel breaks C=1 because Sparse isn't expecting a GCC option with that
> > format.
> Please try --param=allow-store-data-races=0
On 06/15/2014 11:47 PM, Heiko Schocher wrote:
Driver for the TI TMP103.
The TI TMP103 is similar to the TMP102. It differs from the TMP102
by having only 8 bit registers.
Signed-off-by: Heiko Schocher
Hello Heiko,
Almost there.
---
+static int tmp103_probe(struct i2c_client *client,
+
Dropping the const qualifiers prevents "passing argument 1 of ‘of_node_put’
discards ‘const’ qualifier from pointer target type" type warnings when
compiling the code dropping reference to cpu_of_node, codec_of_node or
platform_of_node with with an of_node_put() function call.
This lets us to
On Mon 16-06-14 10:12:33, Tejun Heo wrote:
> On Mon, Jun 16, 2014 at 04:04:48PM +0200, Michal Hocko wrote:
> > > For whatever reason, a user is stuck with thread-level granularity for
> > > controllers which work that way, the user can use the old hierarchies
> > > for them for the time being.
> >
On Mon, Jun 16, 2014 at 4:08 PM, wrote:
> Today I have tried with 3.15 the behavior is same as before.
None of these patches were in 3.15, so that should behave as before.
Cheers,
Tom
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Tue, Jun 10, 2014 at 5:13 PM, wrote:
> I see contradiction of drivers/base/Kconfig here i.e, If I configure
> DELL_RBU=y I cannot configure FW_LOADER_USER_HELPER=n.
> with this patch https://lkml.org/lkml/2014/6/4/327 i cannot have
> FW_LOADER_USER_HELPER=n & DELL_RBU=y at the same time.
>
On Sun, Jun 15, 2014 at 08:56:35PM +0200, Sam Ravnborg wrote:
> On Tue, Jun 10, 2014 at 05:20:08PM -0400, Peter Hurley wrote:
> > On 06/10/2014 03:24 PM, Sam Ravnborg wrote:
> > >>From: Peter Hurley
> > >>Date: Mon, 9 Jun 2014 19:21:43 -0400
> > >>Subject: [PATCH] serial: sunsab: Test for no tx
Hi all,
While fuzzing with trinity inside a KVM tools guest running the latest -next
kernel I've stumbled on the following spew:
[ 430.429005] ==
[ 430.429005] [ INFO: possible circular locking dependency detected ]
[ 430.429005]
On 16 June 2014 14:20, Lee Jones wrote:
>> From: Micky Ching
>>
>> rtsx driver using a single function for transfer data, dma map/unmap are
>> placed in one fix function. We need map/unmap dma in different place(for
>> mmc async driver), so add three function for dma map, dma transfer and
>> dma
> cros_ec_spi makes the assumption that a 0-length message will put the
> spi chip select back to normal (non cs_toggle mode). This used to be
> the case back on kernel-3.8 on the spi-s3c64xx driver but doesn't
> appear to be true anymore. It seems like it was a pretty questionable
> assumption
On 06/16/2014 12:49 AM, Vincent Guittot wrote:
Hi Bart,
Guenter sent similar patch few days ago
https://lkml.org/lkml/2014/6/12/743
with additional patches for ARM and powerpc architecture
https://lkml.org/lkml/2014/6/13/399
https://lkml.org/lkml/2014/6/13/407
Still not applied, though, so
On Mon, Jun 16, 2014 at 01:07:00PM +0200, Vitaly Kuznetsov wrote:
> some old Xen hypervisors (prior to 3.2) forbid DomUs to register
> NMI callbacks. E.g. we have the following code in xen-3.1:
>
> if ( (d->domain_id != 0) || (v->vcpu_id != 0) )
> return -EINVAL;
>
> Commit
When $srctree or $objtree are relative paths, we cannot change directory
and refer to them in the same subshell. Do the redirection outside of
the subshell to fix this.
Reported-by: Ilya Dryomov
Signed-off-by: Michal Marek
---
scripts/package/builddeb | 10 +-
1 file changed, 5
On Jun 16, 2014, at 7:13 AM, Anil Belur wrote:
> From: Anil Belur
>
> fixed: WARNING: line over 80 characters, used a new variable 'check' to
> store the offset. Replace "unsigned long" with "u64" type fir
> 'cur_index'
>
> Signed-off-by: Anil Belur
> ---
>
On Mon, Jun 09, 2014 at 02:38:59PM +0100, Catalin Marinas wrote:
> On Mon, Jun 09, 2014 at 02:24:29PM +0100, Leif Lindholm wrote:
> > On Mon, Jun 09, 2014 at 12:03:56PM +0100, Catalin Marinas wrote:
> > > A quick grep through the kernel shows that we have other set_pte() calls
> > > without
On 06/15/2014 10:41 PM, George Cherian wrote:
On 6/16/2014 10:29 AM, Guenter Roeck wrote:
On 06/15/2014 07:42 PM, George Cherian wrote:
This is the driver for the USB ID pin detection. This driver
handles only the USB ID pin changes generated by cable
insertion/removal.
Signed-off-by: George
* Tero Kristo [140616 07:03]:
> On 05/07/2014 01:20 PM, Peter Ujfalusi wrote:
> >Modify the clock nodes for the ATL clocks to use the ATL clock driver to
> >handle them.
> >
> >Add the ATL device node at the same time for DRA7.
> >
> >Signed-off-by: Peter Ujfalusi
>
> This patch missed the
On Mon, Jun 09, 2014 at 02:24:29PM +0100, Leif Lindholm wrote:
> On Mon, Jun 09, 2014 at 12:03:56PM +0100, Catalin Marinas wrote:
> > So I'm proposing an alternative patch (which needs some benchmarking as
> > well to see if anything is affected, maybe application startup time).
I don't like the
On Mon, Jun 16, 2014 at 04:04:48PM +0200, Michal Hocko wrote:
> > For whatever reason, a user is stuck with thread-level granularity for
> > controllers which work that way, the user can use the old hierarchies
> > for them for the time being.
>
> So he can mount memcg with new cgroup API and
Hi Tom,
Today I have tried with 3.15 the behavior is same as before.
Do you have any update on this?
Regards
Balaji Singh
-Original Message-
From: Singh, B B
Sent: Tuesday, June 10, 2014 8:44 PM
To: 'Tom Gundersen'
Cc: LKML; Ming Lei; Greg KH; Abhay Salunke; Stefan Roese; Arnd
On Mon, Jun 16, 2014 at 09:17:04AM -0400, Peter Hurley wrote:
> tty->closing cannot be set on ipw_open() because the ipwireless tty
> driver does not call any functions that set tty->closing.
>
> CC: Jiri Kosina
Acked-by: David Sterba
--
To unsubscribe from this list: send the line
The tegra-cpufreq driver is only for Tegra20, an upcoming driver for
Tegra124 will be separate, so this is not needed.
Thanks,
- Mikko
On 06/16/2014 04:35 PM, Tomeu Vizoso wrote:
Instead of setting a direct correlation to the CPU frequency. This allows
for other devices to influence the final
On Sun, Jun 15, 2014 at 7:36 PM, Andi Kleen wrote:
>
> I haven't looked into this in detail, but my initial assumption would
> be that it wouldn't be useful to add new vdso interfaces just for Go.
> After all would you really want to force ever Go user to upgrade their
> kernel just to get fast
On Mon, Jun 16, 2014 at 07:22:07AM -0400, Theodore Ts'o wrote:
> On Mon, Jun 16, 2014 at 09:31:08AM +0200, Torsten Duwe wrote:
> > > 2) Fixed a bug in patch #2 so that it would work correctly if the rng
> > > driver doesn't have an init function (which happens to be the case for
> > > the tpm-rng
Sricharan,
On Monday 16 June 2014 07:23 AM, Sricharan R wrote:
> This series does some cleanups, fixes for handling two interrupts
> getting mapped twice to same crossbar and provides support for
> hardwired IRQ and crossbar definitions.
>
> On certain platforms such as DRA7, SPIs 0, 1, 2, 3, 5,
On Mon 16-06-14 09:57:41, Tejun Heo wrote:
> Hello, Michal.
>
> On Mon, Jun 16, 2014 at 02:59:15PM +0200, Michal Hocko wrote:
> > > There sure is a question of how fast userland will move to the new
> > > interface.
> >
> > Yeah, I was mostly thinking about those who would need to to bigger
> >
It should be mentioned that calling clk_set_rate on the EMC clock
currently does absolutely nothing (except probably returning an error).
The rate switching sequence is not implemented (nor is the clock tree
entirely correct. For example, the kernel thinks that PLL_M is disabled).
Another
On 05/07/2014 01:20 PM, Peter Ujfalusi wrote:
Modify the clock nodes for the ATL clocks to use the ATL clock driver to
handle them.
Add the ATL device node at the same time for DRA7.
Signed-off-by: Peter Ujfalusi
This patch missed the merge window due to long dependency chain, however
Tony
For cxgb3,
Acked-by: Steve Wise
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hello, Michal.
On Mon, Jun 16, 2014 at 02:59:15PM +0200, Michal Hocko wrote:
> > There sure is a question of how fast userland will move to the new
> > interface.
>
> Yeah, I was mostly thinking about those who would need to to bigger
> changes. AFAIR threads will no longer be distributable
Hi Steve,
any comments on this? How can we get this fixed upstream?
Thanks!
metze
Am 10.06.2014 12:03, schrieb Björn Baumbach:
> commit d81b8a40e2ece0a9ab57b1fe1798e291e75bf8fc
> ("CIFS: Cleanup cifs open codepath")
> changed disposition to FILE_OPEN.
>
> Signed-off-by: Björn Baumbach
>
Peter,
Ingo Molnar schreef op di 03-06-2014 om 14:07 [+0200]:
> Peter Zijlstra (12):
> [...]
> sched/idle, x86: Switch from TS_POLLING to TIF_POLLING_NRFLAG
This introduces this obviously correct warning (on 32 bit x86):
arch/x86/kernel/apm_32.c: In function 'apm_do_idle':
On Mon, Jun 16, 2014 at 09:17:14AM -0400, Peter Hurley wrote:
> Since at least before 2.6.30, tty drivers that do not drop the tty lock
> while closing cannot observe ASYNC_CLOSING set while holding the
> tty lock; this includes the tty driver's open() and hangup() methods,
> since the tty core
On Mon, Jun 16, 2014 at 09:17:06AM -0400, Peter Hurley wrote:
> Since at least before 2.6.30, it has not been possible to observe
> a hung up file pointer in a tty driver's open() method unless/until
> the driver open() releases the tty_lock() (eg., before blocking).
>
> This is because
On Tue, Jun 10, 2014 at 08:00:01AM +0100, Wang Weidong wrote:
> The STR Instruction Encoding T4 points that the is in the
> range 0-255.So split the instruction into two for Thumb-2. Just
> like commit 874d5d3ccc("ARM: 6623/1: Thumb-2: Fix out-of-range
> offset for Thumb-2 in proc-v7.S").
>
>
Move the definition of __peri_clk_init() up in "clk-kona.c", in
preparation for the next patch (so it's defined before it's needed).
Move kona_ccu_init() and __kona_clk_init() as well.
Done as a separate patch so doing so doesn't obscure other changes.
Signed-off-by: Alex Elder
---
Add a flag that tracks whether a clock has already been initialized.
Use it to avoid initializing a clock more than once.
Signed-off-by: Alex Elder
---
drivers/clk/bcm/clk-kona.c | 12
drivers/clk/bcm/clk-kona.h | 7 +++
2 files changed, 19 insertions(+)
diff --git
Currently only peripheral clocks are supported for Broadcom platforms
that use Kona style CCUs for clocking. This series adds support for
bus clocks as well.
One motivation for doing this is that there exist peripheral clocks
that cannot be configured without having first enabled a related bus
The last thing done for CCU setup is a call to kona_ccu_init().
This locks and enables write access on the CCU, then calls
__kona_clk_init() for all of the clocks it provides. The purpose of
this was to get or set the initial state of all the registers
related to each clock.
There's no reason to
Add bus clock support. A bus clock has a subset of the components
present in a peripheral clock (again, all optional): a gate; CCU
policy management bits; and if needed, bits to control hysteresis.
Signed-off-by: Alex Elder
---
drivers/clk/bcm/clk-kona-setup.c | 96
Allow a clock to specify a "prerequisite" clock, identified by its
name. The prerequisite clock must be prepared and enabled before a
clock that depends on it is used. In order to simplify locking, we
require a clock and its prerequisite to be associated with the same
CCU. (We'll just
Define the bus clock "bsc3_apb". This bus clock has to be managed
using the CCU policy mechanism, so add the definitions required for
that to the clock and its CCU.
This one bus clock in particular is defined because it is needed
by peripheral clock "bsc3". Our boot loader does not properly
Add the bus clock named "bsc3_apb" to the list of those provided by
the slave CCU.
Signed-off-by: Alex Elder
---
arch/arm/boot/dts/bcm11351.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/bcm11351.dtsi b/arch/arm/boot/dts/bcm11351.dtsi
index
On Mon, Jun 09, 2014 at 02:21:20PM +0100, Liu hua wrote:
> 于 2014/5/6 20:15, Will Deacon 写道:
> > On Sat, May 03, 2014 at 02:44:46PM +0100, Liu Hua wrote:
> Sorry to reply you so late. These days I am working on kdump feature for LPAE
> enabled
> kernel. And now I think this patch is not good.
>
Hi,
here is an initial implementation of EMC scaling for Tegra124, I'm most
interested in feedback on the approach.
The present incarnation is very much specific to Tegra, but I'm sure that we
could find an API that can be shared across SoC families.
I have looked at using existing frameworks
Instead of setting a direct correlation to the CPU frequency. This allows
for other devices to influence the final effective EMC frequency.
In the future, this should be done instead by an ACTMON driver,
which would also take load stats into account when calculating the
floor EMC frequency.
Add a device node for the EMC found on Tegra124.
Signed-off-by: Tomeu Vizoso
---
arch/arm/boot/dts/tegra124.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/tegra124.dtsi b/arch/arm/boot/dts/tegra124.dtsi
index 6e6bc4e..5aa42ff 100644
---
Adds functionality for registering memory bandwidth needs and setting
the EMC clock rate based on that.
Also adds API for setting floor and ceiling frequency rates.
Signed-off-by: Tomeu Vizoso
---
.../bindings/arm/tegra/nvidia,tegra124-emc.txt | 26
drivers/memory/Kconfig
Request it based solely on the current mode's refresh rate. More
accurate requirements can be requested in future patches.
Signed-off-by: Tomeu Vizoso
---
drivers/gpu/drm/tegra/dc.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/gpu/drm/tegra/dc.c
Hello.
On 06/16/2014 12:27 AM, Nick Krause wrote:
From 62b0d77a1430f74b7f5c008c5e8bec11604b33b0 Mon Sep 17 00:00:00 2001
From: Nick
Date: Sun, 15 Jun 2014 16:16:14 -0400
Subject: [PATCHv2] Fixes return logic of function of pch_gbe_alloc_tx_buffers()
Here is the fixed patch changed return
On Fri, Jun 13, 2014 at 4:58 PM, Julius Werner wrote:
>> This is just to export a fixed log to userspace (like a DMI table) or
>> the kernel will actually use the data in some way? Based on the link,
>> it looks like the former to me.
>
> I could imagine both. The link is an in-kernel driver that
On Mon, Jun 09, 2014 at 12:08:13AM +0600, Alexander Bersenev wrote:
> This patch enables two IR devices in dts:
> - One IR device physically found on Cubieboard 2
> - One IR device physically found on Cubietruck
>
> Signed-off-by: Alexander Bersenev
> Signed-off-by: Alexsey Shestacov
Applied,
On Wed, 11 Jun 2014, Adam Thomson wrote:
> This patch adds support for DA9150 Charger & Fuel-Guage IC Charger.
>
> Signed-off-by: Adam Thomson
> ---
> drivers/power/Kconfig | 23 ++
> drivers/power/Makefile | 1 +
> drivers/power/da9150-charger.c | 790
>
Hello Lee,
On 16/06/2014 14:50, Lee Jones wrote:
>> The HLCDC IP available on some Atmel SoCs (i.e. at91sam9n12, at91sam9x5
>> family or sama5d3 family) exposes 2 subdevices:
>> - a display controller (controlled by a DRM driver)
>> - a PWM chip
>>
>> Add support for the MFD device which will
On Sun, Jun 15, 2014 at 08:01:27PM -0700, Hugh Dickins wrote:
> On Fri, 6 Jun 2014, Sasha Levin wrote:
> > On 06/06/2014 02:49 PM, Kirill A. Shutemov wrote:
> > > On Fri, Jun 06, 2014 at 11:26:14AM -0700, Linus Torvalds wrote:
> > >> > On Fri, Jun 6, 2014 at 10:43 AM, Dave Jones wrote:
> > >>> >
On 6/15/2014 9:26 PM, Nick wrote:
This patch fixes memory by checking in function,
*get_skuff if it is be passing a Null skb
struct.
Cheers Nick
Signed-off-by: Nick
---
drivers/infiniband/hw/cxgb4/cm.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
First try to find the named clock variants then fall back to the already
existing handling of a nameless declared baudclk.
This also adds the missing documentation for this already existing variant.
Signed-off-by: Heiko Stuebner
---
.../bindings/serial/snps-dw-apb-uart.txt | 31
Hi,
On Mon, Jun 09, 2014 at 12:08:11AM +0600, Alexander Bersenev wrote:
> This patch adds pins for two IR controllers on A20
>
> Signed-off-by: Alexander Bersenev
> Signed-off-by: Alexsey Shestacov
Applied, thanks.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android
Signed-off-by: Peter Hurley
---
drivers/tty/tty_io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
index 3411071..714320b 100644
--- a/drivers/tty/tty_io.c
+++ b/drivers/tty/tty_io.c
@@ -688,7 +688,7 @@ static void
Hi,
On Mon, Jun 09, 2014 at 12:08:12AM +0600, Alexander Bersenev wrote:
> This patch adds records for two IR controllers on A20
>
> Signed-off-by: Alexander Bersenev
> Signed-off-by: Alexsey Shestacov
> ---
> arch/arm/boot/dts/sun7i-a20.dtsi | 18 ++
> 1 file changed, 18
In the context of the final tty & port close, flushing the tx
ring buffer after the hardware has already been shutdown and
the ring buffer freed is neither required nor desirable.
uart_flush_buffer() performs 3 operations:
1. Resets tx ring buffer indices, but the tx ring buffer has
already
Uart port drivers may reconfigure termios settings based on available
hardware support; set/clear ASYNC_CTS_FLOW and ASYNC_CHECK_CD _after_
calling the port driver's .set_termios method.
Signed-off-by: Peter Hurley
---
drivers/tty/serial/serial_core.c | 5 +++--
1 file changed, 3 insertions(+),
501 - 600 of 1732 matches
Mail list logo
