Hi,
On Friday 24 June 2016 13:09:36 Pranay Kr. Srivastava wrote:
> When a timeout occurs or a recv fails, then
> instead of abruplty killing nbd block device
> wait for it's users to finish.
>
> This is more required when filesystem(s) like
> ext2 or ext3 don't expect their buffer heads to
> disa
Dear Lucky Beneficiary,
You were among the lucky beneficiary selected to receive this donations Award
sum of ?950,000.00 (NINE HUNDRED AND FIFTY THOUSAND EURO ). Each as charity
donations/aid from the Qatar Foundation to promote your business, educational,
and development in order to reduce
On Sun, Jun 26, 2016 at 12:28:31AM -0700, Stephen Boyd wrote:
> The msm chipidea controller uses two main clks, an AHB clk to
> read/write the MMIO registers and a core clk called the system
> clk that drives the controller itself. Add support for these clks
> as they're required in all designs.
>
Heiko & Sean
On 06/24/2016 12:16 AM, Heiko Stuebner wrote:
Am Donnerstag, 23. Juni 2016, 10:32:53 schrieb Sean Paul:
On Tue, Jun 14, 2016 at 7:46 AM, Yakir Yang wrote:
eDP controller need to declare which vop provide the video source,
and it's defined in GRF registers.
But different chips ha
On Tue, Jun 28, 2016 at 11:19:59PM +0200, Rasmus Villemoes wrote:
SNIP
> > - save_arg(void *);
> > + if (spec.cpumask) {
>
> As I hinted in the other mail, I think it's better just to put the
> fmt[1]=='b' here and not change struct printf_spec.
>
> > +
Sean,
On 06/23/2016 10:33 PM, Sean Paul wrote:
On Tue, Jun 14, 2016 at 7:46 AM, Yakir Yang wrote:
There're an register define error in ANALOGIX_DP_PLL_REG_1 which introduced
by commit bcec20fd5ad6 ("drm: bridge: analogix/dp: add some rk3288 special
registers setting").
The PHY PLL input clock
Sean,
On 06/23/2016 09:27 PM, Sean Paul wrote:
On Tue, Jun 14, 2016 at 7:46 AM, Yakir Yang wrote:
As vendor document indicate, when REF_CLK bit set 0, then DP
phy's REF_CLK should switch to 24M source clock.
But due to IC PHY layout mistaken, some chips need to flip this
bit(like RK3288), and
On Tue, 2016-06-28 at 14:13 +0300, Yaniv Machani wrote:
> From: Maital Hahn
>
> Some drivers (e.g. wl18xx) expect that the last stage in the
> de-initialization process will be stopping the beacons, similar to
> ap. Update ieee80211_stop_mesh() flow accordingly.
>
How well have you tested that w
* Javier Martinez Canillas [160627 12:24]:
>
> Hello Tony,
>
> This is another series with trivial fixes for DTC warnings about mismatches
> between unit names and reg properties in different device nodes. The series
> fixes only some of the reported warning and there are still a lot remaining.
Hi
On Wed, Jun 29, 2016 at 12:36 PM, Markus Pargmann wrote:
> Hi,
>
> On Friday 24 June 2016 13:09:36 Pranay Kr. Srivastava wrote:
>> When a timeout occurs or a recv fails, then
>> instead of abruplty killing nbd block device
>> wait for it's users to finish.
>>
>> This is more required when file
Hi Linus,
here are a bunch of fixes for pin control. Just drivers and
a MAINTAINERS fixup.
Please pull them in!
Yours,
Linus Walleij
The following changes since commit 33688abb2802ff3a230bd2441f765477b94cc89e:
Linux 4.7-rc4 (2016-06-19 21:30:02 -0700)
are available in the git repository at:
On Tue, 2016-06-28 at 14:13 +0300, Yaniv Machani wrote:
>
> net/mac80211/mesh.c | 33 -
> net/mac80211/util.c | 3 ---
> net/wireless/mesh.c | 2 +-
That's not a good patch - one change is mac80211 and the other
cfg80211.
> - .ht_opmode = IEEE80211_HT_OP_MOD
On Friday 24 June 2016 13:09:34 Pranay Kr. Srivastava wrote:
> spinlocked ranges should be small and not contain calls into huge
> subfunctions. Fix my mistake and just get the pointer to the socket
> instead of doing everything with spinlock held.
>
> Reported-by: Mikulas Patocka
> Signed-off-by
On Tue, 2016-06-28 at 14:15 +0300, Yaniv Machani wrote:
> From: Meirav Kama
>
> MP received data frames from another MP. Frames are forwarded
> from Rx to Tx to be transmitted to a third MP.
> Upon cloning the skb, the tx_info was zeroed, and the
> hw_queue wasn't set correctly, causing frames to
On Tue, 2016-06-28 at 14:15 +0300, Yaniv Machani wrote:
> From: Maital Hahn
>
> In the reconfigure process for mesh interface, moved the
> reconfiguration
> of the mesh peers to be done only after restarting the beacons,
> the same as it is done for AP.
>
> Signed-off-by: Maital Hahn
> Acked-by
Also - your subject lines should explain the *fix*, not the *bug*
johannes
On 2016년 06월 29일 06:18, Michael Turquette wrote:
> Quoting Rob Herring (2016-06-28 13:55:18)
>> On Fri, Jun 24, 2016 at 01:12:52PM +0900, Jongsung Kim wrote:
>>> There is no way to set additional flags for a DT-initialized fixed-
>>> factor-clock, and it can be problematic i.e., when the clock rate
Hi,
Problems:
1. Deadlocks on prepare lock in following scenario:
- prepare_enable(some external clock through i2c)
- i2c transfer
- prepare_enable(i2c lock in SoC)
- deadlock
See [1]. We implemented a workaround for this in few places like
10ff4c5239a1 ("i2c: exynos5: Fix possibl
On 06/27/2016 12:55 AM, Andy Lutomirski wrote:
> Hi all-
>
>
> Known issues:
> - tcp md5, virtio_net, and virtio_console will have issues. Eric Dumazet
>has a patch for tcp md5, and Michael Tsirkin says he'll fix virtio_net
>and virtio_console.
>
How about PTRACE_SETREGS, it's using
On Tue, Jun 28, 2016 at 07:19:29PM -0400, Steven Rostedt wrote:
> trace_printk() is a very helpful tool for debugging the kernel. It adds
> lots of tricks to optimize itself to prevent any "heisenbugs". That is,
> having the addition of tracing cause the bug to change its timing and
> disappear. On
On Tue, Jun 28, 2016 at 06:37:24PM +0800, Chen Feng wrote:
> Thanks for you reply.
>
> On 2016/6/28 0:57, Vladimir Davydov wrote:
> > On Mon, Jun 27, 2016 at 07:02:15PM +0800, Chen Feng wrote:
> >> In my platform, there can be cache a lot of memory in
> >> ion page pool. When shrink memory the nr_
On Tue, Jun 28, 2016 at 10:36:29AM -0700, Huang, Ying wrote:
> From: Huang Ying
>
> madvise_free_huge_pmd should return 0 if the fallback PTE operations are
> required. In madvise_free_huge_pmd, if part pages of THP are discarded,
> the THP will be split and fallback PTE operations should be use
On Tue, Jun 28, 2016 at 10:36:30AM -0700, Huang, Ying wrote:
> From: Huang Ying
>
> The definition of return value of madvise_free_huge_pmd is not clear
> before. According to the suggestion of Minchan Kim, change the type of
> return value to bool and return true if we do MADV_FREE successfully
Hi Linus,
please pull from the 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
to receive the following updates:
Another two bug fixes for 4.7:
- The revert of patch which removed boot information for systems using an
intermediate boot k
Exported leds had maximum brightness previously unset, thus having
value 255. Set maximum brightness of leds that can only be turned
off or on to 1, making the behavior more consistent with other leds
having binary state.
Signed-off-by: Matej Groma
---
Changes from v1:
made commit message
On Wednesday 29 June 2016 02:58 AM, Rhyland Klein wrote:
Add regulators to the Tegra210 Smaug DTS file including
support for the max77620 PMIC.
Signed-off-by: Rhyland Klein
Looks fine to me from DT property perspective.
Acked-by: Laxman Dewangan
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX50
> drivers/pinctrl/freescale/Kconfig: bool "IMX50 pinctrl driver"
>
> ...meaning that it currently is not being bu
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX51
> drivers/pinctrl/freescale/Kconfig: bool "IMX51 pinctrl driver"
>
> ...meaning that it currently is not being bu
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX53
> drivers/pinctrl/freescale/Kconfig: bool "IMX53 pinctrl driver"
>
> ...meaning that it currently is not being bu
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX1
> drivers/pinctrl/freescale/Kconfig: bool "IMX1 pinctrl driver"
>
> ...meaning that it currently is not being buil
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX21
> drivers/pinctrl/freescale/Kconfig: bool "i.MX21 pinctrl driver"
>
> ...meaning that it currently is not being b
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX25
> drivers/pinctrl/freescale/Kconfig:bool "IMX25 pinctrl driver"
>
> ...meaning that it currently is not being
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX27
> drivers/pinctrl/freescale/Kconfig: bool "IMX27 pinctrl driver"
>
> ...meaning that it currently is not being bu
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX6Q
> drivers/pinctrl/freescale/Kconfig: bool "IMX6Q/DL pinctrl driver"
>
> ...meaning that it currently is not being
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> None of these files have anything modular in them, so they
> don't need to be bringing in module.h and all its dependencies.
>
> Cc: Linus Walleij
> Cc: linux-g...@vger.kernel.org
> Signed-off-by: Paul Gortmaker
Patch applied.
Yours,
Li
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX35
> drivers/pinctrl/freescale/Kconfig: bool "IMX35 pinctrl driver"
>
> ...meaning that it currently is not being bu
Hi Andrew,
Am Montag, den 27.06.2016, 12:12 -0500 schrieb Andrew F. Davis:
> Some SoCs contain reset controls for modules that are memory-mapped to
> areas shared with other module configuration settings. This requires
> synchronization across all drivers accessing this memory area. This
> series
Hi Lee,
Am Dienstag, den 28.06.2016, 09:56 +0100 schrieb Lee Jones:
> Philipp,
>
> I need this to go into the -rcs too.
>
> Can I add it with your Ack please?
I have already added your patches to my branch, and I intend to send a
pull request for it tomorrow. I am afraid applying this patch in
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX6Q
> drivers/pinctrl/freescale/Kconfig: bool "IMX6Q/DL pinctrl driver"
>
> ...meaning that it currently is not being
Yury Norov writes:
> @@ -174,6 +177,7 @@ _dl_tlsdesc_dynamic:
> stp x29, x30, [sp,#-(32+16*NSAVEXREGPAIRS)]!
> cfi_adjust_cfa_offset (32+16*NSAVEXREGPAIRS)
> mov x29, sp
> + DELOUSE(0)
>
> /* Save just enough registers to support fast path, if we fall
>
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX6SL
> drivers/pinctrl/freescale/Kconfig: bool "IMX6SL pinctrl driver"
>
> ...meaning that it currently is not being
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX6SX
> drivers/pinctrl/freescale/Kconfig: bool "IMX6SX pinctrl driver"
>
> ...meaning that it currently is not being
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX6UL
> drivers/pinctrl/freescale/Kconfig: bool "IMX6UL pinctrl driver"
>
> ...meaning that it currently is not being
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX7D
> drivers/pinctrl/freescale/Kconfig: bool "IMX7D pinctrl driver"
>
> ...meaning that it currently is not being bu
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_VF610
> drivers/pinctrl/freescale/Kconfig: bool "Freescale Vybrid VF610 pinctrl
> driver"
>
> ...meaning that it curre
On Mon, Jun 27, 2016 at 09:25:45PM +1000, Balbir Singh wrote:
>
>
> On 26/05/16 16:22, js1...@gmail.com wrote:
> > From: Joonsoo Kim
> >
> > Hello,
> >
> > Changes from v2
> > o Rebase on next-20160525
> > o No other changes except following description
> >
> > There was a discussion with Mel
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX28
> drivers/pinctrl/freescale/Kconfig: bool
>
> ...meaning that it currently is not being built as a module by anyo
On 29/06/2016 at 08:12:21 +0200, Alexander Stein wrote :
> > +#if defined(CONFIG_CPU_V7)
> > + dsb();
> > + wfi();
> > +#else
> > + asm volatile ("mcr p15, 0, %0, c7, c0, 4" \
> > + : : "r" (0) : "memory");
> > +#endif
>
> Why not defining wfi() for __LINUX_ARM_ARCH__ <
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_MXS
> drivers/pinctrl/freescale/Kconfig: bool
>
> ...meaning that it currently is not being built as a module by anyone
On Tue, Jun 28, 2016 at 07:23:23PM +0800, Chen Feng wrote:
> Hello,
>
> On 2016/6/23 10:52, Joonsoo Kim wrote:
> > On Wed, Jun 22, 2016 at 05:23:06PM +0800, Chen Feng wrote:
> >> Hello,
> >>
> >> On 2016/5/26 14:22, js1...@gmail.com wrote:
> >>> From: Joonsoo Kim
> >>>
> >>> Until now, reserved p
From: James Ban
This is a patch for adding description for da9212/da9214.
Signed-off-by: James Ban
---
Changes since PATCH V1
- add compatible strings for da9212 and da9214.
This patch applies against linux-next and next-20160624
.../devicetree/bindings/regulator/da9211.txt | 47 +
On Sun, Jun 26, 2016 at 4:46 AM, Paul Gortmaker
wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/pinctrl/freescale/Kconfig:config PINCTRL_IMX23
> drivers/pinctrl/freescale/Kconfig: bool
>
> ...meaning that it currently is not being built as a module by anyo
On Wed, 29 Jun 2016, Philipp Zabel wrote:
> Am Dienstag, den 28.06.2016, 09:56 +0100 schrieb Lee Jones:
> > Philipp,
> >
> > I need this to go into the -rcs too.
> >
> > Can I add it with your Ack please?
>
> I have already added your patches to my branch, and I intend to send a
> pull request f
From: Zhao Qiang
Date: Mon, 27 Jun 2016 09:30:22 +0800
> Signed-off-by: Zhao Qiang
Applied to net-next, thanks.
Hi Stephen
On Tue, Jun 28, 2016 at 8:04 PM, Stephen Boyd wrote:
> Almost, except that this flag should be set in the common clk
> framework and not in each driver. The large majority of cases
> will want that. Only a few will want to clear it, and then we can
> hide that fact by having a differe
On Fri, Jun 24, 2016 at 3:06 PM, Amitoj Kaur Chawla
wrote:
> of_find_node_by_name does an of_node_get on its return value,
> so an of_node_put is needed on this value before the corresponding
> variable goes out of scope.
>
> The Coccinelle semantic patch used to make this change is as follows:
>
From: Harini Katakam
Date: Mon, 27 Jun 2016 13:09:59 +0530
> Marvell 88E currently uses the generic marvell config ANEG function.
> This function has a sequence accessing Page 5 and Register 31,
> both of which are not defined or reserved for this PHY.
> Hence this patch adds a new config ANE
On Tue, Jun 28, 2016 at 07:03:04PM -0700, a...@linux-foundation.org wrote:
>
> The patch titled
> Subject: mm, compaction: abort free scanner if split fails
> has been removed from the -mm tree. Its filename was
> mm-compaction-abort-free-scanner-if-split-fails.patch
>
> This patch was
On Fri, Jun 17, 2016 at 12:15 PM, Neil Armstrong
wrote:
> In order to support the Qualcomm MDM9615 SoC, add support for the TLMM
> using the Qualcomm pinctrl generic driver.
>
> Note: the pinctrl is partial, need Documentation to complete all the groups.
> Signed-off-by: Neil Armstrong
Patch ap
From: Amitoj Kaur Chawla
Date: Mon, 27 Jun 2016 14:34:50 +0530
> pci_free_consistent's argument 'struct pci_dev' should be NULL not 0.
>
> The Coccinelle semantic patch used to make this change is as follows:
> @@
> @@
>
> pci_free_consistent(
> - 0
> + NULL
> , ...)
>
> Signed-off-by: Amito
On Tue, 28 Jun 2016, Stefan Agner wrote:
> This patchset adds RN5T567 PMIC support which is used on the
> Toradex Colibri iMX7S/iMX7D modules. The existing RN5T618 is from
> the same family, hence this patchset uses the same driver and adds
> variant support.
>
> The Colibris currently do not us
This is a ThinkPad T440s with a stable 64bit hardened Gentoo.
If it is docked then the described behaviour happens.
I do run latest kernel, former kernel versions show the same behaviour.
All other functionality of the resumed system is fine, so it is just the
monitor which needs an extra kick.
A
On Fri, Jun 17, 2016 at 12:15 PM, Neil Armstrong
wrote:
> Signed-off-by: Neil Armstrong
Patch applied with the ACKs.
Yours,
Linus Walleij
Amit Pundir writes:
> From: xerox_lin
Please sanitize name here. Then resend.
thanks
--
balbi
signature.asc
Description: PGP signature
On Sun, Jun 26, 2016 at 7:21 AM, Stephen Boyd wrote:
> The function selection bitfield is not always 3 bits wide.
> Sometimes it is 4 bits wide. Let's use the npins struct member to
> determine how many bits wide the function selection bitfield is
> so we clear the correct amount of bits in the r
The same can be done for the pthread types, following the x32 example.
Andreas.
diff --git a/sysdeps/aarch64/nptl/bits/pthreadtypes.h
b/sysdeps/aarch64/nptl/bits/pthreadtypes.h
index 13984a7..49bb402 100644
--- a/sysdeps/aarch64/nptl/bits/pthreadtypes.h
+++ b/sysdeps/aarch64/nptl/bits/pthreadtyp
On Tue, 28 Jun 2016, Yoshinori Sato wrote:
> Signed-off-by: Yoshinori Sato
> ---
> Documentation/devicetree/bindings/mfd/sm501.txt | 45
> +
This needs a DT Ack, but you haven't sent it to the DT list.
Did you run ./scripts/get_maintainer.pl?
> drivers/mfd/sm501.c
Oh, and the subject line needs to reflect the subsystem you are
submitting to.
On Wed, 29 Jun 2016, Lee Jones wrote:
> On Tue, 28 Jun 2016, Yoshinori Sato wrote:
>
> > Signed-off-by: Yoshinori Sato
> > ---
> > Documentation/devicetree/bindings/mfd/sm501.txt | 45
> > +
>
On Sun, Jun 26, 2016 at 12:28:32AM -0700, Stephen Boyd wrote:
> We need to pick the correct phy at runtime based on how the SoC
> has been wired onto the board. If the secondary phy is used, take
> it out of reset and mux over to it by writing into the TCSR
> register. Make sure to do this on reset
On 06/28/2016 02:33 PM, Herbert Xu wrote:
> On Tue, Jun 28, 2016 at 12:15:43PM +0200, Krzysztof Kozlowski wrote:
>> Oops:
>
> Thanks, there was a typo where it said k instead of j in the second
> loop.
>
> ---8<---
> This patch resolves a number of issues with the mb speed test
> function:
>
> *
On 29/06/2016 05:17, Xiao Guangrong wrote:
>>
>> +++ b/arch/x86/kvm/mmu.c
>> @@ -2516,13 +2516,17 @@ static int set_spte(struct kvm_vcpu *vcpu, u64
>> *sptep,
>> gfn_t gfn, kvm_pfn_t pfn, bool speculative,
>> bool can_unsync, bool host_writable)
>> {
>> -u64 spte
On Tue 2016-06-28 13:04:47, Tejun Heo wrote:
> Hello,
>
> On Mon, Jun 27, 2016 at 04:33:50PM +0200, Petr Mladek wrote:
> > OK, so you suggest to do the following:
> >
> > 1. Add a flag into struct kthread_worker that will prevent
> > from further queuing.
>
> This doesn't add any protecti
On Wed, Jun 29, 2016 at 10:16:10AM +0200, Krzysztof Kozlowski wrote:
>
> Seems to work fine except:
> 1. The updates are always 1.
Yes the test function only does digest so it's always one update.
> 2. For bigger blocks it reports always 1 or 3 cycles per byte:
Yes the average cycles per-byte s
On 2016-06-29 01:12, Lee Jones wrote:
> On Tue, 28 Jun 2016, Stefan Agner wrote:
>
>> This patchset adds RN5T567 PMIC support which is used on the
>> Toradex Colibri iMX7S/iMX7D modules. The existing RN5T618 is from
>> the same family, hence this patchset uses the same driver and adds
>> variant s
From: Grygorii Strashko
Date: Mon, 27 Jun 2016 12:05:11 +0300
> TI CPDMA currently uses a bitmap for tracking descriptors alloactions
> allocations, but The genalloc already handles the same and can be used
> as with special memory (SRAM) as with DMA cherent memory chank
> (dma_alloc_coherent()).
On Tue, Jun 28, 2016 at 01:46:04PM -0700, Kees Cook wrote:
> On Tue, Jun 28, 2016 at 9:14 AM, Emese Revfy wrote:
> > On Tue, 28 Jun 2016 13:57:49 +0100
> > Mark Rutland wrote:
> >
> >> On Tue, Jun 28, 2016 at 01:34:07PM +0200, Emese Revfy wrote:
> >> > This patch set is based on the "Add support
Hi,
Baolin Wang writes:
>> Baolin Wang writes:
>>> For supporting the usb charger, it adds the usb_charger_init() and
>>> usb_charger_exit() functions for usb charger initialization and exit.
>>>
>>> It will report to the usb charger when the gadget state is changed,
>>> then the usb charger ca
On Tue 2016-06-28 15:17:56, Steven Rostedt wrote:
> On Mon, 27 Jun 2016 15:54:33 +0200
> Petr Mladek wrote:
>
> > 1st patch adds one more paranoid check of the modified function on x86.
> >
> > Plus there are 3 small changes that appeared when hunting down
> > the 1st patch.
> >
> > Petr Mladek
Since commit 103544d86976 ("ACPI,PCI,IRQ: reduce resource requirements")
the penalty values are calculated on the fly rather than boot time.
This works fine for PCI interrupts but not so well for the ISA interrupts.
Whether an ISA interrupt is in use or not information is not available
inside the
The change introduced in commit 103544d86976 ("ACPI,PCI,IRQ: reduce
resource requirements") omitted the initially assigned POSSIBLE penalty
when the IRQ is active.
The original code would assign the POSSIBLE value divided by the number
of possible IRQs during initialization.
Later, if the IRQ is
Trying to make the ISA and PCI init functionality common turned out to be
a bad idea. ISA path depends on external functionality. Restoring the
previous behavior and limiting the refactoring to PCI interrupts only.
This reverts commit 1fcb6a813c4f ("ACPI,PCI,IRQ: remove redundant code in
acpi_irq_
On 06/29/2016 10:19 AM, Herbert Xu wrote:
> On Wed, Jun 29, 2016 at 10:16:10AM +0200, Krzysztof Kozlowski wrote:
>>
>> Seems to work fine except:
>> 1. The updates are always 1.
>
> Yes the test function only does digest so it's always one update.
>
>> 2. For bigger blocks it reports always 1 or
The omitted parenthesis prevents the addition operation when
acpi_penalize_isa_irq function is called.
Signed-off-by: Sinan Kaya
---
drivers/acpi/pci_link.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/pci_link.c b/drivers/acpi/pci_link.c
index 8c08971..c983bf
On Sun, Jun 26, 2016 at 7:21 AM, Stephen Boyd wrote:
> The msm8974 pinctrl variant has a couple USB HSIC "glue"
> registers that let us mux between the pinctrl register settings
> or the HSIC core settings for the HSIC pins (gpio 144 and gpio
> 145). Support this method of operation by adding hsi
On Wednesday 29 June 2016 09:57:14, Alexandre Belloni wrote:
> On 29/06/2016 at 08:12:21 +0200, Alexander Stein wrote :
> > > +#if defined(CONFIG_CPU_V7)
> > > + dsb();
> > > + wfi();
> > > +#else
> > > + asm volatile ("mcr p15, 0, %0, c7, c0, 4" \
> > > + : : "r" (0) : "memory")
Hi Felipe,
On 29 June 2016 at 16:20, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>>> Baolin Wang writes:
For supporting the usb charger, it adds the usb_charger_init() and
usb_charger_exit() functions for usb charger initialization and exit.
It will report to the usb
On Mon, Jun 27, 2016 at 4:23 PM, Amitoj Kaur Chawla
wrote:
> pinctrl_register returns an ERR_PTR on error.
>
> The Coccinelle semantic patch used to make this change is as follows:
>
> @@
> expression e,e1,e2;
> @@
>
> e = pinctrl_register(...)
> ... when != e = e1
> if (
> - e == NULL
> + IS
Hi again
On Wed, Jun 29, 2016 at 10:07 AM, Ricardo Ribalda Delgado
wrote:
> - I can send it as a proper patch if you prefer tat.
Just realised how bad the code is treated by gmail.
You can navigate more easily through the code here:
https://github.com/ribalda/linux/tree/clk-platform-v4
Regar
On 6/27/2016 5:05 PM, ok...@codeaurora.org wrote:
> On 2016-06-27 16:04, Wim Osterholt wrote:
>> On Mon, Jun 27, 2016 at 04:22:18AM -0400, ok...@codeaurora.org wrote:
>>> > However, an earlier try on my Inspiron 510m did not work.
>>> > I'll do a clean retry later today, just to make sure.
>>>
>>>
Hi,
Baolin Wang writes:
> For supporting the usb charger, it adds the usb_charger_init() and
> usb_charger_exit() functions for usb charger initialization and exit.
>
> It will report to the usb charger when the gadget state is changed,
> then the usb charger can do the power
On Sun, Jun 26, 2016 at 12:28:33AM -0700, Stephen Boyd wrote:
> When the RESET bit is set in the USBCMD register it resets quite
> a few of the wrapper's registers to their reset state. This
> includes the GENCONFIG and GENCONFIG2 registers. Currently this
> is done by the usb phy and ehci-msm driv
Adding Thunderbolt(TM) networking documentation.
Signed-off-by: Amir Levy
---
Documentation/00-INDEX | 2 +
Documentation/thunderbolt-networking.txt | 135 +++
2 files changed, 137 insertions(+)
create mode 100644 Documentation/thunderbolt-network
This first patch updates the registers file to
reflect that it isn't only for Cactus Ridge.
No functional change intended.
Signed-off-by: Amir Levy
---
drivers/thunderbolt/nhi_regs.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/thunderbolt/nhi_regs.h b/driver
Handling the transmission to second peer and receiving from it.
This includes communication with upper layer, the network stack
and configuration of Thunderbolt(TM) HW.
Signed-off-by: Amir Levy
---
drivers/thunderbolt/icm_nhi.c | 15 +
drivers/thunderbolt/net.c | 1475 +
On 29 June 2016 at 16:34, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> For supporting the usb charger, it adds the usb_charger_init() and
>> usb_charger_exit() functions for usb charger initialization and exit.
>>
>> It will report to the usb charger when the gadget stat
Firmware-based (a.k.a ICM - Intel Connection Manager) controller is
used for establishing and maintaining the Thunderbolt Networking
connection. We need to be able to communicate with it.
Signed-off-by: Amir Levy
---
drivers/thunderbolt/Makefile |2 +
drivers/thunderbolt/icm_nhi.c | 1332 ++
This is version 2 of Thunderbolt(TM) driver for non-Apple hardware.
Changes since v1:
- Separation to 2 modules.
- Moved ICM specific registers definition to ICM header file.
- Added new Thunderbolt device IDs.
- Renamed the Thunderbolt networking documentation.
- General cleanups
These patc
Negotiation states that a peer goes through in order to establish
the communication with the second peer.
This includes communication with upper layer and additional
infrastructure support to communicate with the second peer through ICM.
Signed-off-by: Amir Levy
---
drivers/thunderbolt/Makefile
Updating the Kconfig Thunderbolt(TM) description.
Signed-off-by: Amir Levy
---
drivers/thunderbolt/Kconfig | 25 +
drivers/thunderbolt/Makefile | 2 +-
2 files changed, 22 insertions(+), 5 deletions(-)
diff --git a/drivers/thunderbolt/Kconfig b/drivers/thunderbolt/Kcon
Adding the new Thunderbolt(TM) device IDs to the list.
Signed-off-by: Amir Levy
---
include/linux/pci_ids.h | 44 ++--
1 file changed, 26 insertions(+), 18 deletions(-)
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index c58752f..2d4cc50
1 - 100 of 844 matches
Mail list logo
