On Tue, Jun 02, 2015 at 04:14:33PM +0300, Ivan T. Ivanov wrote:
> On recent Qualcomm platforms VBUS and ID lines are not routed to
> USB PHY LINK controller. Use extcon framework to receive connect
> and disconnect ID and VBUS notification.
>
> Signed-off-by: Ivan T. Ivanov
> ---
> Changes sice v
* Rusty Russell wrote:
> As the comment in arch/x86/include/asm/paravirt_types.h says:
>
>* Get/set interrupt state. save_fl and restore_fl are only
>* expected to use X86_EFLAGS_IF; all other bits
>* returned from save_fl are undefined, and may be ignored by
>*
Hi Peter,
Peter Zijlstra wrote 2015-06-03 PM 04:55:27:
>
> Re: [RFC][PATCH 1/7] sched: Replace post_schedule with a balance
callback list
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most
---
.../devicetree/bindings/gpio/gpio-generic.txt | 19 +
drivers/gpio/gpio-generic.c| 81 ++-
2 files changed, 78 insertions(+), 22 deletions(-)
create mode 100644 Documentation/devicetree/bindings/gpio/gpio-generic.txt
diff --git a/Documenta
On Fri, Jun 05, 2015 at 03:13:38PM +0800, pang.xun...@zte.com.cn wrote:
> > It will make sched_setscheduler() etc.. a little more expensive, but
> > that doesn't matter, those are not critical things at all.
>
> Another side effect it may have is that it will introduce some latency,
> because we
On Thu, Jun 04, 2015 at 05:08:11PM -0700, John Stultz wrote:
> I'm not sure how this follows. Leap smearing is a different behavior
> and I'd like to support it (as a separate clockid) as well, but adding
> that support doesn't change that the existing behavior applying the
> leapsecond to UTC/CLOC
On Fri, 2015-06-05 at 15:03 +0800, Peter Chen wrote:
> On Tue, Jun 02, 2015 at 04:14:33PM +0300, Ivan T. Ivanov wrote:
> > On recent Qualcomm platforms VBUS and ID lines are not routed to
> > USB PHY LINK controller. Use extcon framework to receive connect
> > and disconnect ID and VBUS notificati
* H. Peter Anvin wrote:
> I really dislike deep hierarchies, as I said, because my experience has been
> that they are more confusing than they are helpful, especially over time.
> The
> arch-example of badness is of course arch/x86/kernel, which is a total
> catch-all, but
Well, directory
Пятница, 5 июня 2015, 8:51 +02:00 от Romain Baeriswyl
:
> ---
> .../devicetree/bindings/gpio/gpio-generic.txt | 19 +
> drivers/gpio/gpio-generic.c| 81 ++-
> 2 files changed, 78 insertions(+), 22 deletions(-)
> create mode 100644 Documentati
Hi Dmitry:
Thank you for your suggestion.
We will base on the top of mainline driver and re-submit the patch.
James
-Original Message-
From: linux-input-ow...@vger.kernel.org
[mailto:linux-input-ow...@vger.kernel.org] On Behalf Of Dmitry Torokhov
Sent: Friday, June 05, 2015 1:38 PM
To: j
Hello Andy,
2015-06-03 15:30 GMT+06:00 Andy Shevchenko :
> On Wed, 2015-06-03 at 13:55 +0600, Alexander Kuleshov wrote:
>> This patch introduces the setup_builtin_cmdline function which appends or
>> overrides boot_command_line with the builtin_cmdline if CONFIG_CMDLINE_BOOL
>> is set.
>
>> Previo
>>> + hz = 100/delta;
>
> This needs to be on of the do_div family.
>
> Dave.
Hi Dave,
I build-tested the patch for both 32-bit and 64-bit x86. If my
understanding is correct, since the divisor is 64-bit here, the
compiler will do "if (delta > 100) hz = 0; else hz =
100/(s32)delta"
* John Stultz wrote:
> So I suspect the problem is the change to clock_was_set_seq in
> timekeeping_update is done prior to mirroring the time state to the
> shadow-timekeeper. Thus the next time we do update_wall_time() the updated
> sequence is overwritten by whats in the shadow copy. The a
2015-06-03 15:30 GMT+06:00 Andy Shevchenko :
> On Wed, 2015-06-03 at 13:55 +0600, Alexander Kuleshov wrote:
>> This patch introduces the setup_builtin_cmdline function which appends or
>> overrides boot_command_line with the builtin_cmdline if CONFIG_CMDLINE_BOOL
>> is set.
>
>> Previously this fun
On Fri, 05 Jun 2015, "m...@ellerman.id.au" wrote:
> Hi Dave,
>
> Today's linux-next merge of the drm tree got a conflict in
> drivers/gpu/drm/i915/intel_ringbuffer.c between commit 4f47c99a9be7
> ("drm/i915:
> Move WaBarrierPerformanceFixDisable:skl to skl code from chv code") from the
> drm-inte
Currently we have to hold the single cma_mutex when alloc cma pages,
it is ok when there is only one cma area in system.
However, when there are several cma areas, such as in our Android smart
phone, the single cma_mutex prevents concurrent cma page allocation.
This patch removes the single cma_mu
On 06/04/2015 11:05 PM, Jean-Baptiste Theou wrote:
Hi Guenter,
I based my work on the work done in mpc8xxx_wdt.c, which is in mainline.
Yes, you mentioned that before. However, that is a driver for a specific
chip, not a generic driver like this one. That driver is only messy for
one chip. You
Minor warnings spotted by checkpatch.pl in lustre regarding const correctness:
struct seq_operations should be const.
Signed-off-by: Xavier Roche
---
drivers/staging/lustre/lustre/llite/vvp_dev.c | 2 +-
drivers/staging/lustre/lustre/lmv/lproc_lmv.c | 2 +-
drivers/staging/lustre/lustre/lov/lov
On 06/04/2015 07:40 PM, David Miller wrote:
>
> I think your Subject meant to say "fixes for 4.2" right?
>
> Because we're currently finishing up 4.1.x and the next merge
> window will be for 4.2.x
>
Hi David,
Ralf only accepts patches for MIPS 4.2 that have been posted before
4.1-rc5. This is
> Ingo Molnar wrote:
>* George Spelvin wrote:
>> Did you use rtc_cmos_read()? [...]
> Yeah, so initially I did, but then after I noticed the overhead I introduced:
> which compiles to a single INB instruction.
>
> This didn't change the delay/cost behavior.
>
> The numbers I cited, with tens of
Hi Guys,
On Fri, May 29, 2015 at 2:35 PM, Ming Lei wrote:
> Hi Guys,
>
> There are about 3 advantages to use direct I/O and AIO on
> read/write loop's backing file:
>
> 1) double cache can be avoided, then memory usage gets
> decreased a lot
>
> 2) not like user space direct I/O, there isn't cost
On 06/04/2015 05:49 PM, Alexei Starovoitov wrote:
> On 6/4/15 3:56 AM, Markos Chandras wrote:
>> Here are some fixes for MIPS/BPF. The first 5 patches do some cleanup
>> and lay the groundwork for the final one which introduces assembly
>> helpers
>> for MIPS and MIPS64. The goal is to speed up cer
The CONFIG_ prefix is reserved for Kconfig options in Make and CPP
syntax. Various static analysis tools rely on this naming convention
and check if CONFIG_ prefixed symbols are defined Kconfig. Hence add
yet another prefix AMD_ to CONFIG_REG_{BASE,END,SISE} to apply to this
convention and make s
+ Marcel, wireless list, and bt list.
On 06/05/15 07:12, Jonas Thiem wrote:
Hi Jeremiah,
thanks for responding!
I did have my mobile phone very nearby also connected to the bluetooth
headphones while my laptop was still using 11n wifi. I didn't have any
noticeable issues with bluetooth there.
* George Spelvin wrote:
> > Ingo Molnar wrote:
> >* George Spelvin wrote:
> >> Did you use rtc_cmos_read()? [...]
>
> > Yeah, so initially I did, but then after I noticed the overhead I
> > introduced:
> > which compiles to a single INB instruction.
> >
> > This didn't change the delay/cost
Acked-by: Ralf Baechle
Ralf
--
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/
On Thu, Jun 04, 2015 at 12:13:41PM +0800, Jiang Liu wrote:
For drivers/irqchip/irq-brcmstb-l2.c:
Acked-by: Ralf Baechle
Ralf
--
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.ker
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
# HEAD: b44a2b53becf2485f484bd6bb6c1d963ebc339f8 perf/x86/intel/pt: Fix a
refactoring bug
The biggest chunk of the changes are two regressio
Hi YH,
2015-06-05 8:15 GMT+02:00 YH Huang :
> On Mon, 2015-05-25 at 10:14 +0800, Yingjoe Chen wrote:
>> On Thu, 2015-05-21 at 21:29 +0800, YH Huang wrote:
>
> This patch series add the use of display PWM driver and documentation
> for Mediatek SoCs. The driver is used to support the backlight of
>
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
# HEAD: 425be5679fd292a3c36cb1fe423086708a99f11a x86/asm/irq: Stop relying
on magic JMP behavior for early_idt_handlers
Misc fixes:
- early
Commit-ID: cf991de2f614f454b3cb2a300c06ecdf69f3a70d
Gitweb: http://git.kernel.org/tip/cf991de2f614f454b3cb2a300c06ecdf69f3a70d
Author: Andy Lutomirski
AuthorDate: Thu, 4 Jun 2015 17:13:44 -0700
Committer: Ingo Molnar
CommitDate: Fri, 5 Jun 2015 09:41:22 +0200
x86/asm/msr: Make wrmsrl_s
Hi Caesar,
thanks for investigating this.
Am Freitag, 5. Juni 2015, 12:47:55 schrieb Caesar Wang:
> In general, the correct flow is:
>
> cpu off:
> reset_control_assert
> regmap_update_bits(pmu, PMU_PWRDN_CON, BIT(pd), BIT(pd))
>
> cpu on:
> regmap_update_bits(pmu, PMU_PWRDN_CON, B
On 05/06/15 00:02, Paul Walmsley wrote:
> Hi folks
>
> just a brief comment on this one:
>
> On Thu, 30 Apr 2015, Boris Brezillon wrote:
>
>> Clock rates are stored in an unsigned long field, but ->round_rate()
>> (which returns a rounded rate from a requested one) returns a long
>> value (erro
On 5 June 2015 at 04:59, Stephen Warren wrote:
> On 05/29/2015 03:06 PM, Eric Anholt wrote:
>> We're currently using a fixed frequency clock specified in the DT, so
>> enabling is a no-op. However, the RPi firmware-based clocks driver
>> can actually disable unused clocks, so when switching to us
Remove sparse warnings:
drivers/net/ethernet/xilinx/ll_temac_main.c:65:16: warning: cast removes
address space of expression
drivers/net/ethernet/xilinx/ll_temac_main.c:70:9: warning: cast removes
address space of expression
drivers/net/ethernet/xilinx/ll_temac_main.c:127:16: warning: cast
removes
A few remarks, perhaps not of the kind you'd like for an RFC, that I
hope are still relevant after Herbert's comment.
On Wed, 2015-06-03 at 15:44 -0700, Tadeusz Struk wrote:
> --- a/crypto/asymmetric_keys/Makefile
> +++ b/crypto/asymmetric_keys/Makefile
> @@ -8,6 +8,7 @@ asymmetric_keys-y := asymm
Warnings found by sparse:
arch/microblaze/kernel/dma.c:157:5: warning: symbol
'dma_direct_mmap_coherent' was not declared. Should it be static?
arch/microblaze/kernel/kgdb.c:35:14: warning: symbol 'pvr' was not
declared. Should it be static?
Signed-off-by: Michal Simek
---
arch/microblaze/kerne
On 2015/6/5 14:41, Ingo Molnar wrote:
* Alexei Starovoitov wrote:
On 6/4/15 7:04 AM, Ingo Molnar wrote:
# perf record -e bpf_source.c cmdline
to create a eBPF filter from source,
Use
# perf record -e bpf_object.o cmdline
to create a eBPF filter from object intermedia.
Use
# perf b
On Mon, Jun 01, 2015 at 04:05:44PM +0800, Jiang Liu wrote:
For arch/mips/alchemy/common/irq.c:
Acked-by: Ralf Baechle
Ralf
--
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.kerne
On Mon, Jun 01, 2015 at 04:05:30PM +0800, Jiang Liu wrote:
Acked-by: Ralf Baechle
Ralf
--
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
Hi Michael,
On Fri, Jun 05, 2015 at 06:50:30PM +1000, Michael Ellerman wrote:
> diff --cc include/linux/intel-iommu.h
> index a81ceeeaa3d1,0af9b03e2b1c..
> --- a/include/linux/intel-iommu.h
> +++ b/include/linux/intel-iommu.h
> @@@ -355,9 -349,8 +357,11 @@@ struct intel_iommu
>
>
The whole migrate_task{,s}() locking seems a little shaky, there's a
lot of dropping an require happening. Pull the locking up into the
callers as far as possible to streamline the lot.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sched/core.c | 76 +++--
Employ the new lockdep lock pinning annotation to ensure no
'accidental' lock-breaks happen with rq->lock.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sched/core.c | 42 +++---
kernel/sched/deadline.c |8
kernel/sched/fair.c | 11
In order to be able to use pull_rt_task() from a callback, we need to
do away with the return value.
Since the return value indicates if we should reschedule, do this
inside the function. Since not all callers currently do this, this can
increase the number of reschedules due rt balancing.
Too ma
Currently an hrtimer callback function cannot free its own timer
because __run_hrtimer() still needs to clear HRTIMER_STATE_CALLBACK
after it. Freeing the timer would result in a clear use-after-free.
Solve this by using a scheme similar to regular timers; track the
current running timer in hrtime
Remove the direct {push,pull} balancing operations from
switched_{from,to}_dl() / prio_changed_dl() and use the balance
callback queue.
Again, err on the side of too many reschedules; since too few is a
hard bug while too many is just annoying.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/s
We still have a few pending issues with the deadline code, one of which
is that switching between scheduling classes can 'leak' CBS state.
Close the hole by retaining the current CBS state when leaving
SCHED_DEADLINE and unconditionally programming the deadline timer.
The timer will then reset the
Heiko,
在 2015年06月05日 16:45, Heiko Stübner 写道:
Hi Caesar,
thanks for investigating this.
Am Freitag, 5. Juni 2015, 12:47:55 schrieb Caesar Wang:
In general, the correct flow is:
cpu off:
reset_control_assert
regmap_update_bits(pmu, PMU_PWRDN_CON, BIT(pd), BIT(pd))
cpu on:
reg
Mike stumbled over a cute bug where the RT/DL balancing ops caused a bug.
The exact scenario is __sched_setscheduler() changing a (runnable) task from
FIFO to OTHER. In swiched_from_rt(), where we do pull_rt_task() we temporarity
drop rq->lock. This gap allows regular cfs load-balancing to step in
lock_release() takes this nested argument that's mostly pointless
these days, remove the implementation but leave the argument a
rudiment for now.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/locking/lockdep.c | 119 +++
1 file changed, 18 inserti
Shouldn't we make it a proper function sine there is going to have to be a
function call involved anyway?
On June 5, 2015 1:42:56 AM PDT, tip-bot for Andy Lutomirski
wrote:
>Commit-ID: cf991de2f614f454b3cb2a300c06ecdf69f3a70d
>Gitweb:
>http://git.kernel.org/tip/cf991de2f614f454b3cb2a300c06
Generalize the post_schedule() stuff into a balance callback list.
This allows us to more easily use it outside of schedule() and cross
sched_class.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sched/core.c | 36
kernel/sched/deadline.c | 21 +
In preparation to reworking set_cpus_allowed_ptr() move some code
around. This also removes some superfluous #ifdefs and adds comments
to some #endifs.
textdata bss dec hex filename
122115321738144 1081344 15031020 e55aec
defconfig-build/vmlinux.pre
12211532
In order to be able to use pull_dl_task() from a callback, we need to
do away with the return value.
Since the return value indicates if we should reschedule, do this
inside the function. Since not all callers currently do this, this can
increase the number of reschedules due rt balancing.
Too ma
In order to remove dropping rq->lock from the
switched_{to,from}()/prio_changed() sched_class methods, run the
balance callbacks after it.
We need to remove dropping rq->lock because its buggy,
suppose using sched_setattr()/sched_setscheduler() to change a running
task from FIFO to OTHER.
By the
Reduce duplicate logic; normalize_task() is a simplified version of
__sched_setscheduler(). Parametrize the difference and collapse.
This reduces the amount of check_class_changed() sites.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sched/core.c | 65 ++---
Remove the direct {push,pull} balancing operations from
switched_{from,to}_rt() / prio_changed_rt() and use the balance
callback queue.
Again, err on the side of too many reschedules; since too few is a
hard bug while too many is just annoying.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/s
Add a lockdep annotation that WARNs if you 'accidentially' unlock a
lock.
This is especially helpful for code with callbacks, where the upper
layer assumes a lock remains taken but a lower layer thinks it maybe
can drop and reacquire the lock.
By unwittingly breaking up the lock, races can be int
On Fri, Jun 05, 2015 at 09:29:13AM +0200, Peter Zijlstra wrote:
> That leaves the question; for who is this exact second edge important?
Distributed applications using the UTC time scale.
Many control applications are done with a 1 millisecond period.
Having the time wrong by a second for 10 or 1
This whole patchset looks find to me.
Some tips for the future.
On Wed, Jun 03, 2015 at 04:43:20PM -0400, James Simmons wrote:
> From: John L. Hammond
>
> In lnet/lnet/ and lnet/selftest/ assume a kernel build (assume that
> __KERNEL__ is defined). Remove some common code only needed for user
>
On Wed, Jun 03, 2015 at 04:43:24PM -0400, James Simmons wrote:
> Currently the lnet headers used by user land contain various internal
> LNet structures that are only used by kernel space. Move the user land
> structures to headers used by user land. The kernel structures are
> relocated to headers
I'm fine with merging this patch as is.
On Wed, Jun 03, 2015 at 04:43:26PM -0400, James Simmons wrote:
> + struct lnet_peer*msg_txpeer; /* peer I'm sending to */
> + struct lnet_peer*msg_rxpeer; /* peer I received from */
> +
> + void*msg_pri
This message is too late, /me going to see new series :)
05.06.2015, 12:02, "Kirill Tkhai" :
> В Чт, 04/06/2015 в 12:49 +0200, Peter Zijlstra пишет:
> On Thu, Jun 04, 2015 at 12:07:03PM +0300, Kirill Tkhai wrote:
--- a/include/linux/hrtimer.h
+++ b/include/linux/hrtimer.h
@@ -391
On Fri, 2015-06-05 at 11:04 +0200, Richard Cochran wrote:
> On Fri, Jun 05, 2015 at 09:29:13AM +0200, Peter Zijlstra wrote:
> > That leaves the question; for who is this exact second edge important?
>
> Distributed applications using the UTC time scale.
>
> Many control applications are done with
On Fri, Jun 05, 2015 at 12:02:01PM +0300, Kirill Tkhai wrote:
> Yeah, it's safe for now, but it may happen difficulties with a support
> in the future, because barrier logic is not easy to review. But it seems
> we may simplify it a little bit. Please, see the comments below.
> > @@ -394,8 +399,24
On Fri, Jun 05, 2015 at 12:03:34PM +0300, Kirill Tkhai wrote:
> This message is too late, /me going to see new series :)
Never too late, and thanks for looking at them. The new patch is
basically the same as the last proposal (except build fixes and a
comment).
--
To unsubscribe from this list: se
В Чт, 04/06/2015 в 12:49 +0200, Peter Zijlstra пишет:
On Thu, Jun 04, 2015 at 12:07:03PM +0300, Kirill Tkhai wrote:
> > > --- a/include/linux/hrtimer.h
> > > +++ b/include/linux/hrtimer.h
> > > @@ -391,11 +391,25 @@ extern u64 hrtimer_get_next_event(void);
> > > * A timer is active, when it is en
On 04/06/15 22:19, Stephen Boyd wrote:
On 05/27, Sudeep Holla wrote:
The clocks for the CPUs are provided by SCP and are managed by this
clock driver. So the cpufreq device needs to be added only after the
clock get registered and removed when this driver is unloaded.
This patch manages the c
On Thu, 4 Jun 2015, John Stultz wrote:
> On Wed, Jun 3, 2015 at 5:56 PM, Jeremiah Mahler wrote:
> So I suspect the problem is the change to clock_was_set_seq in
> timekeeping_update is done prior to mirroring the time state to the
> shadow-timekeeper. Thus the next time we do update_wall_time() th
(Cc'ing David)
On Wed, 27 May, at 04:45:48PM, Ethan Zhao wrote:
> As descriped in https://bugzilla.kernel.org/show_bug.cgi?id=98721
> When kernel 4.0.4 was tested on Oracle and HP system with UEFI mode, no
> output and
> login on console.
>
> Simplefb was broken on these systems when orig_video_
On Thu, Jun 04, 2015 at 05:27:28PM -0500, Dinh Nguyen wrote:
> This is my mistake. I applied Alan Tull's patch for suspend-to-ram which
> also touches drivers/edac/altera_edac.c.
>
> https://git.kernel.org/cgit/linux/kernel/git/dinguyen/linux.git/commit/?h=socfpga_for_next_arria10&id=d44a92eb044f4
Those errors prevented the script from running. Just changed some tabs to
spaces.
Signed-off-by: Philipp Trommler
---
.../python/Perf-Trace-Util/lib/Perf/Trace/Core.py | 28 +++---
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/tools/perf/scripts/python/Perf-Tra
On Fri, Jun 05, 2015 at 09:37:09AM +0800, Wan ZongShun wrote:
> Boris, I means I put this KERCZ Mircro in pci_ids.h, and I also will
> send the other patch to instead the following '0x790b' of codes. I
> think it is reasonable, right?
No, it means two things:
* why does it contain KERNCZ? What do
Hi Linus,
The following changes since commit c65b99f046843d2455aa231747b5a07a999a9f3d:
Linux 4.1-rc6 (2015-05-31 19:01:07 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git
tags/iommu-fixes-v4.1-rc6
for you to fetch changes up to 2d
On Tue, 02 Jun, at 05:09:14PM, Zhang, Jonathan Zhixiong wrote:
> Thank you for the feedback, Matt.
>
> Given that IA64 does not set EFI_MEMMAP, it appears to me there
> are following options:
> A. Keep status quota and copy x86's efi_mem_attributes() code
> to arm64.
Let's avoid this option.
> B
Add a device tree node for the On-Chip One Time Programmable
Controller (OCOTP) and the On-Chip ROM.
Signed-off-by: Sanchayan Maity
---
arch/arm/boot/dts/vfxxx.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi
index
Hello,
This patchset implements SoC bus support for Freescale Vybrid platform,
implementing the following
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-devices-soc
and is the fifth revision. Tested on a Colibri VF61 module after
rebasing on shawn's for-next branch.
Arnd and Shawn I d
This adds a SoC driver to be used by the Freescale Vybrid SoC's.
We create the "fsl" directory for holding the different Freescale
designs. Driver utilises syscon to get the various register values
needed. After this sysfs exposes some SoC specific properties as
below:
> cd /sys/devices/soc0
> ls
05.06.2015, 12:10, "Peter Zijlstra" :
> On Fri, Jun 05, 2015 at 12:02:01PM +0300, Kirill Tkhai wrote:
>> Yeah, it's safe for now, but it may happen difficulties with a support
>> in the future, because barrier logic is not easy to review. But it seems
>> we may simplify it a little bit. Please,
Hi
On Fri, Jun 5, 2015 at 11:17 AM, Matt Fleming wrote:
> (Cc'ing David)
>
> On Wed, 27 May, at 04:45:48PM, Ethan Zhao wrote:
>> As descriped in https://bugzilla.kernel.org/show_bug.cgi?id=98721
>> When kernel 4.0.4 was tested on Oracle and HP system with UEFI mode, no
>> output and
>> login on
On 05/06/15 03:58, Rusty Russell wrote:
>
> Subject: x86: rename save_fl/restore_fl paravirt ops to highlight eflags.
> From: Rusty Russell
>
> As the comment in arch/x86/include/asm/paravirt_types.h says:
>
>* Get/set interrupt state. save_fl and restore_fl are only
>* expecte
On 04/06/15 23:07, Stephen Boyd wrote:
On 05/22, Daniel Thompson wrote:
+
+#include
Are you using this include?
+#include
Are you using this include?
Not very much?
Turns out I was relying on these to get kzalloc() defined but there are
better headers for me to use for that!
+#i
On 04/06/15 21:20, Stephen Boyd wrote:
On 05/27, Sudeep Holla wrote:
+
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+
+struct scpi_clk {
+ u32 id;
+ const char *name;
+ struct clk_hw hw;
+ struct scpi_dvfs_info *info;
+ unsigned lon
On Fri, Jun 05, 2015 at 10:37:07AM +0300, Ivan T. Ivanov wrote:
>
> On Fri, 2015-06-05 at 15:03 +0800, Peter Chen wrote:
> > On Tue, Jun 02, 2015 at 04:14:33PM +0300, Ivan T. Ivanov wrote:
> > > On recent Qualcomm platforms VBUS and ID lines are not routed to
> > > USB PHY LINK controller. Use ext
Am Freitag, 5. Juni 2015, 17:00:02 schrieb Caesar Wang:
> Heiko,
>
> 在 2015年06月05日 16:45, Heiko Stübner 写道:
> > Hi Caesar,
> >
> >
> > thanks for investigating this.
> >
> > Am Freitag, 5. Juni 2015, 12:47:55 schrieb Caesar Wang:
> >> In general, the correct flow is:
> >>
> >> cpu off:
> >>
On 06/05/2015 05:35 AM, Roger Quadros wrote:
> Hi,
>
> On Wed, 3 Jun 2015 22:52:47 +0300
> Grygorii Strashko wrote:
>
>> Hi Geert,
>>
>> On 05/19/2015 12:38 PM, Geert Uytterhoeven wrote:
>>> On Mon, May 18, 2015 at 4:52 PM, grygorii.stras...@linaro.org
>>> wrote:
On 05/18/2015 05:31 PM, Th
On Fri, 5 Jun 2015, Peter Zijlstra wrote:
> /*
> + * We require the migration_base for
> lock_hrtimer_base()/switch_hrtimer_base()
> + * such that hrtimer_callback_running() can unconditionally dereference
> + * timer->base->cpu_base
> + */
> +static struct hrtimer_cpu_base migration_cpu_base = {
Hi Thomas,
File include/linux/irqnr.h provides several helper interfaces to walk
all/active irq descriptors. And the typical usage mode for those
interfaces is as below:
a) for_each_irq_desc(i, desc) {
b) do_pre_work();
c) raw_spin_lock_irq(&desc->lock);
d)
Am Freitag, 5. Juni 2015, 13:28:06 schrieb Herbert Xu:
Hi Herbert,
>
> Steffen, I think we need to revisit the idea of having a list
> of callbacks.
Ok, I will reactivate my patch with the list.
>
> Cheers,
--
Ciao
Stephan
--
To unsubscribe from this list: send the line "unsubscribe linux-ke
* Peter Zijlstra wrote:
> RFC: a possible alternative API would be something like:
>
> int cookie = lockdep_pin_lock(&foo);
> ...
> lockdep_unpin_lock(&foo, cookie);
Yeah, this would be even nicer.
> Where we pick a random number for the pin_count; this makes it
> impossible to sneak a
[ Cc'ing Boris and Tony. Folks original patch is here,
https://lkml.kernel.org/r/1433185940-24770-4-git-send-email-zjzh...@codeaurora.org
]
On Mon, 01 Jun, at 12:12:20PM, Jonathan (Zhixiong) Zhang wrote:
> From: "Jonathan (Zhixiong) Zhang"
>
> With ACPI APEI firmware first handling, generic
* Peter Zijlstra wrote:
> Employ the new lockdep lock pinning annotation to ensure no
> 'accidental' lock-breaks happen with rq->lock.
btw., could we perhaps reorder this series a bit and first see that it properly
detects the original locking bug, and then only fix the bug?
To make sure the
On Thu, 4 Jun 2015, Arnd Bergmann wrote:
> int get_timespec64(struct timespec64 *ts, const struct timespec __user *uts)
> {
> struct timespec64 tmp;
> int ret;
>
> if (sizeof(tmp) == sizeof(*ts))
> return copy_from_user(&tmp, uts, sizeof(*ts)) ? -EFAULT : 0;
>
>
2015-06-05 17:20 GMT+08:00 Borislav Petkov :
> On Fri, Jun 05, 2015 at 09:37:09AM +0800, Wan ZongShun wrote:
>> Boris, I means I put this KERCZ Mircro in pci_ids.h, and I also will
>> send the other patch to instead the following '0x790b' of codes. I
>> think it is reasonable, right?
>
> No, it mea
On Thu, Jun 04, 2015 at 11:04:36AM -0700, Doug Anderson wrote:
> The dw_hdmi_connector_get_modes() function accidentally forgets to
> return the number of modes it added, although it has this information
> stored in a local variable. Let's fix that.
>
> Without this fix, drm_helper_probe_single_c
* H. Peter Anvin wrote:
> Shouldn't we make it a proper function sine there is going to have to be a
> function call involved anyway?
Yeah, so what I think should be done instead is to flip around the API:
make wrmsrl_safe() the primary API and derive wrmsr_safe() from that,
because it's the s
On Fri, 5 Jun 2015, Jiang Liu wrote:
> 4) Called during cpu_up()
> kernel/irq/chip.c:irq_cpu_online()
> arch/x86/kernel/apic/vector.c:__setup_vector_irq()
>
> 5) Called from free running process context
> arch/x86/kernel/topology.c: arch_register_cpu()
> arch/x86/kernel/apic/io_apic.c: print_IO_AP
* Thomas Gleixner wrote:
> On Thu, 4 Jun 2015, John Stultz wrote:
> > On Wed, Jun 3, 2015 at 5:56 PM, Jeremiah Mahler wrote:
> > So I suspect the problem is the change to clock_was_set_seq in
> > timekeeping_update is done prior to mirroring the time state to the
> > shadow-timekeeper. Thus the
This patch set provides a workaround to avoid the following problem.
It's based on Linux 4.1-rc3 mainstream kernel.
I've tested this patch set on x86-64 machine and KVM.
Problem
--
There're cases where autoconfig_irq() fails during boot.
In these cases, the console doesn't
Allow drivers to set security label(e.g. smack, selinux) to be used
for their device nodes on devtmpfs. In this manner, some systems
(e.g. Android, tizen etc.) can allow setting of security label on
devtmpfs nodes even if there is no udev.
Namjae Jeon (3):
driver: core: add uid gid to class devn
1 - 100 of 805 matches
Mail list logo
