On Fri, Jun 02, 2017 at 07:44:04PM +0200, Jason A. Donenfeld wrote:
> On Fri, Jun 2, 2017 at 7:26 PM, Theodore Ts'o wrote:
> > I tried making /dev/urandom block.
> > So if you're a security focused individual who is kvetching
> > And if we're breaking
>
> Yes yes, bla bla,
On Fri, Jun 02, 2017 at 07:44:04PM +0200, Jason A. Donenfeld wrote:
> On Fri, Jun 2, 2017 at 7:26 PM, Theodore Ts'o wrote:
> > I tried making /dev/urandom block.
> > So if you're a security focused individual who is kvetching
> > And if we're breaking
>
> Yes yes, bla bla, predictable response.
On Fri, Jun 02, 2017 at 01:36:23PM -0400, Bandan Das wrote:
> Christoffer Dall writes:
>
> > On Thu, Jun 01, 2017 at 04:05:49PM -0400, Bandan Das wrote:
> >> Jintack Lim writes:
> >> ...
> >> > +/**
> >> > + * kvm_arm_setup_shadow_state -- prepare
On Fri, Jun 02, 2017 at 01:36:23PM -0400, Bandan Das wrote:
> Christoffer Dall writes:
>
> > On Thu, Jun 01, 2017 at 04:05:49PM -0400, Bandan Das wrote:
> >> Jintack Lim writes:
> >> ...
> >> > +/**
> >> > + * kvm_arm_setup_shadow_state -- prepare shadow state based on emulated
> >> > mode
>
On 05/27/2017 11:52 PM, Noam Camus wrote:
From: Noam Camus
This commit adds the configuration CONFIG_EZNPS_MEM_ERROR.
If set, it will cause the kernel to handle user memory error
as a machine check exception.
It is required in order to align the NPS simulator memory
error
On 05/27/2017 11:52 PM, Noam Camus wrote:
From: Noam Camus
This commit adds the configuration CONFIG_EZNPS_MEM_ERROR.
If set, it will cause the kernel to handle user memory error
as a machine check exception.
It is required in order to align the NPS simulator memory
error handling to the one
On 6/2/2017 10:39 AM, Steve Kemp wrote:
>> Create an security module that looks for the attribute
> For what it is worth I thought this seemed like an interesting project
> for a beginner, so I did just that. I wrote up the experience here:
>
>
On 6/2/2017 10:39 AM, Steve Kemp wrote:
>> Create an security module that looks for the attribute
> For what it is worth I thought this seemed like an interesting project
> for a beginner, so I did just that. I wrote up the experience here:
>
>
On 06/02/2017 11:52 AM, Scott Branden wrote:
> Use consistent license headers for Broadcom files by
> placing additional comments outside of standard legal header.
>
> Also, update legal header to 2017 format as "Broadcom Corporation"
> has changed to "Broadcom".
>
> Signed-off-by: Scott Branden
On 06/02/2017 11:52 AM, Scott Branden wrote:
> Use consistent license headers for Broadcom files by
> placing additional comments outside of standard legal header.
>
> Also, update legal header to 2017 format as "Broadcom Corporation"
> has changed to "Broadcom".
>
> Signed-off-by: Scott Branden
On Fri, Jun 2, 2017 at 10:41 AM, Daniel Micay wrote:
> On Fri, 2017-06-02 at 17:53 +0200, Jason A. Donenfeld wrote:
>> (Meanwhile...)
>>
>> In my own code, I'm currently playing with a workaround that looks
>> like this:
>>
>> --- a/src/main.c
>> +++ b/src/main.c
>>
>>
On Fri, Jun 2, 2017 at 10:41 AM, Daniel Micay wrote:
> On Fri, 2017-06-02 at 17:53 +0200, Jason A. Donenfeld wrote:
>> (Meanwhile...)
>>
>> In my own code, I'm currently playing with a workaround that looks
>> like this:
>>
>> --- a/src/main.c
>> +++ b/src/main.c
>>
>> +#include
>> +#include
>>
On Fri, Jun 2, 2017 at 2:00 PM, John Stultz wrote:
> On Tue, May 23, 2017 at 8:04 PM, Xinliang Liu wrote:
>> On 24 May 2017 at 00:40, John Stultz wrote:
>>>
>>> This fixes a regression introduced by ebc944613567 ("drm:
>>>
On Fri, Jun 2, 2017 at 10:22 AM, Peter S. Housel wrote:
> An earlier change to this function (3bdae810721b) fixed a leak in the
> case of an unsuccessful call to brcmf_sdiod_buffrw(). However, the
> glob_skb buffer, used for emulating a scattering read, is never used
> or
On Fri, Jun 2, 2017 at 2:00 PM, John Stultz wrote:
> On Tue, May 23, 2017 at 8:04 PM, Xinliang Liu wrote:
>> On 24 May 2017 at 00:40, John Stultz wrote:
>>>
>>> This fixes a regression introduced by ebc944613567 ("drm:
>>> convert drivers to use drm_of_find_panel_or_bridge") that was
>>>
On Fri, Jun 2, 2017 at 10:22 AM, Peter S. Housel wrote:
> An earlier change to this function (3bdae810721b) fixed a leak in the
> case of an unsuccessful call to brcmf_sdiod_buffrw(). However, the
> glob_skb buffer, used for emulating a scattering read, is never used
> or referenced after its
Use consistent license headers for Broadcom files by
placing additional comments outside of standard legal header.
Also, update legal header to 2017 format as "Broadcom Corporation"
has changed to "Broadcom".
Signed-off-by: Scott Branden
---
Use consistent license headers for Broadcom files by
placing additional comments outside of standard legal header.
Also, update legal header to 2017 format as "Broadcom Corporation"
has changed to "Broadcom".
Signed-off-by: Scott Branden
---
drivers/pinctrl/bcm/pinctrl-bcm281xx.c | 9
Hi Friends,
I may have hit on a possible bug with remove_pagetables. However, so
far, I have only been able to reproduce it with my out-of-tree p2pmem
patchset (so I understand if you don't consider it a bug). At this time,
I have not able been able to reproduce it using device-dax.
Starting
Hi Friends,
I may have hit on a possible bug with remove_pagetables. However, so
far, I have only been able to reproduce it with my out-of-tree p2pmem
patchset (so I understand if you don't consider it a bug). At this time,
I have not able been able to reproduce it using device-dax.
Starting
On 06/02/2017 10:22 AM, Peter S. Housel wrote:
> An earlier change to this function (3bdae810721b) fixed a leak in the
> case of an unsuccessful call to brcmf_sdiod_buffrw(). However, the
> glob_skb buffer, used for emulating a scattering read, is never used
> or referenced after its contents are
On 06/02/2017 10:22 AM, Peter S. Housel wrote:
> An earlier change to this function (3bdae810721b) fixed a leak in the
> case of an unsuccessful call to brcmf_sdiod_buffrw(). However, the
> glob_skb buffer, used for emulating a scattering read, is never used
> or referenced after its contents are
On Fri, Jun 2, 2017 at 9:40 PM, Jean Delvare wrote:
> On Thu, 1 Jun 2017 19:06:36 +0300, Andy Shevchenko wrote:
>> On Thu, Jun 1, 2017 at 5:40 PM, Jean Delvare wrote:
>> > On Thu, 1 Jun 2017 16:16:05 +0300, Andy Shevchenko wrote:
>> >> On Thu, Jun 1, 2017 at
On Fri, Jun 2, 2017 at 9:40 PM, Jean Delvare wrote:
> On Thu, 1 Jun 2017 19:06:36 +0300, Andy Shevchenko wrote:
>> On Thu, Jun 1, 2017 at 5:40 PM, Jean Delvare wrote:
>> > On Thu, 1 Jun 2017 16:16:05 +0300, Andy Shevchenko wrote:
>> >> On Thu, Jun 1, 2017 at 4:08 PM, Jean Delvare wrote:
>>
>>
On Fri, 26 May 2017, Boris Ostrovsky wrote:
> On 05/19/2017 07:22 PM, Stefano Stabellini wrote:
> > Just reply with success to the other end for now. Delay the allocation
> > of the actual socket to bind and/or connect.
> >
> > Signed-off-by: Stefano Stabellini
> > CC:
On Fri, 26 May 2017, Boris Ostrovsky wrote:
> On 05/19/2017 07:22 PM, Stefano Stabellini wrote:
> > Just reply with success to the other end for now. Delay the allocation
> > of the actual socket to bind and/or connect.
> >
> > Signed-off-by: Stefano Stabellini
> > CC: boris.ostrov...@oracle.com
On Thu, 1 Jun 2017 19:06:36 +0300, Andy Shevchenko wrote:
> On Thu, Jun 1, 2017 at 5:40 PM, Jean Delvare wrote:
> > On Thu, 1 Jun 2017 16:16:05 +0300, Andy Shevchenko wrote:
> >> On Thu, Jun 1, 2017 at 4:08 PM, Jean Delvare wrote:
>
> >> > - const
On Thu, 1 Jun 2017 19:06:36 +0300, Andy Shevchenko wrote:
> On Thu, Jun 1, 2017 at 5:40 PM, Jean Delvare wrote:
> > On Thu, 1 Jun 2017 16:16:05 +0300, Andy Shevchenko wrote:
> >> On Thu, Jun 1, 2017 at 4:08 PM, Jean Delvare wrote:
>
> >> > - const u8 *d = (u8 *) dm + index;
> >> > +
On Fri, Jun 2, 2017 at 5:04 AM, Benjamin Herrenschmidt
wrote:
> On Fri, 2017-06-02 at 01:46 -0700, Brendan Higgins wrote:
>> Added slave support for Aspeed I2C controller. Supports fourteen busses
>> present in AST24XX and AST25XX BMC SoCs by Aspeed.
>
> (Not an issue
On Fri, Jun 2, 2017 at 5:04 AM, Benjamin Herrenschmidt
wrote:
> On Fri, 2017-06-02 at 01:46 -0700, Brendan Higgins wrote:
>> Added slave support for Aspeed I2C controller. Supports fourteen busses
>> present in AST24XX and AST25XX BMC SoCs by Aspeed.
>
> (Not an issue for merging)
>
> Have you
On 05/27/2017 11:52 PM, Noam Camus wrote:
From: Noam Camus
This way when we execute "ex" during trying to hold lock we can switch to
other HW thread and utilize the core intead of just spinning on a lock.
We noticed about 10% improvement of execution time with hackbench
On 05/27/2017 11:52 PM, Noam Camus wrote:
From: Noam Camus
This way when we execute "ex" during trying to hold lock we can switch to
other HW thread and utilize the core intead of just spinning on a lock.
We noticed about 10% improvement of execution time with hackbench test.
Signed-off-by:
On Fri, 26 May 2017, Boris Ostrovsky wrote:
> > static int pvcalls_back_socket(struct xenbus_device *dev,
> > struct xen_pvcalls_request *req)
> > {
> > - return 0;
> > + struct pvcalls_back_priv *priv;
> > + int ret;
> > + struct xen_pvcalls_response *rsp;
> > +
> > + priv
On Fri, 26 May 2017, Boris Ostrovsky wrote:
> > static int pvcalls_back_socket(struct xenbus_device *dev,
> > struct xen_pvcalls_request *req)
> > {
> > - return 0;
> > + struct pvcalls_back_priv *priv;
> > + int ret;
> > + struct xen_pvcalls_response *rsp;
> > +
> > + priv
From: "Michael S. Tsirkin"
Date: Fri, 2 Jun 2017 17:54:33 +0300
> commit d85b758f72b0 ("virtio_net: fix support for small rings")
> was supposed to increase the buffer size for small rings but had an
> unintentional side effect of decreasing it for large rings. This seems
> to
From: "Michael S. Tsirkin"
Date: Fri, 2 Jun 2017 17:54:33 +0300
> commit d85b758f72b0 ("virtio_net: fix support for small rings")
> was supposed to increase the buffer size for small rings but had an
> unintentional side effect of decreasing it for large rings. This seems
> to break some setups
On 06/01, kgu...@codeaurora.org wrote:
> On 2017-05-31 07:14, Stephen Boyd wrote:
> >On 05/30, Kiran Gunda wrote:
> >>diff --git a/drivers/spmi/spmi-pmic-arb.c
> >>b/drivers/spmi/spmi-pmic-arb.c
> >>index 7201611..6320f1f 100644
> >>--- a/drivers/spmi/spmi-pmic-arb.c
> >>+++
On 06/01, kgu...@codeaurora.org wrote:
> On 2017-05-31 07:14, Stephen Boyd wrote:
> >On 05/30, Kiran Gunda wrote:
> >>diff --git a/drivers/spmi/spmi-pmic-arb.c
> >>b/drivers/spmi/spmi-pmic-arb.c
> >>index 7201611..6320f1f 100644
> >>--- a/drivers/spmi/spmi-pmic-arb.c
> >>+++
On 06/01, kgu...@codeaurora.org wrote:
> >>@@ -209,23 +210,24 @@ static void pa_read_data(struct
> >>spmi_pmic_arb_dev *dev, u8 *buf, u32 reg, u8 bc)
> >> * @buf: buffer to write. length must be bc + 1.
> >> */
> >> static void
> >>-pa_write_data(struct spmi_pmic_arb_dev *dev, const u8 *buf,
On 06/01, kgu...@codeaurora.org wrote:
> >>@@ -209,23 +210,24 @@ static void pa_read_data(struct
> >>spmi_pmic_arb_dev *dev, u8 *buf, u32 reg, u8 bc)
> >> * @buf: buffer to write. length must be bc + 1.
> >> */
> >> static void
> >>-pa_write_data(struct spmi_pmic_arb_dev *dev, const u8 *buf,
>> + i2c_ic->irq_domain = irq_domain_add_linear(
>> + node, ASPEED_I2C_IC_NUM_BUS,
>> + _i2c_ic_irq_domain_ops, NULL);
>
> nit: can you have at least one argument following the function name?
> Even if checkpatch shouts out you?
Makes no difference to
>> + i2c_ic->irq_domain = irq_domain_add_linear(
>> + node, ASPEED_I2C_IC_NUM_BUS,
>> + _i2c_ic_irq_domain_ops, NULL);
>
> nit: can you have at least one argument following the function name?
> Even if checkpatch shouts out you?
Makes no difference to
Em Fri, Jun 02, 2017 at 03:45:11PM +, Liang, Kan escreveu:
> > > On Mon, May 29, 2017 at 02:52:39PM +0200, Peter Zijlstra wrote:
> > > > On Mon, May 29, 2017 at 02:46:37PM +0200, Jiri Olsa wrote:
> > > > > for some reason I can't get single SMI count generated, is there a
> > > > > setup/bench
Em Fri, Jun 02, 2017 at 03:45:11PM +, Liang, Kan escreveu:
> > > On Mon, May 29, 2017 at 02:52:39PM +0200, Peter Zijlstra wrote:
> > > > On Mon, May 29, 2017 at 02:46:37PM +0200, Jiri Olsa wrote:
> > > > > for some reason I can't get single SMI count generated, is there a
> > > > > setup/bench
On Fri, Jun 02, 2017 at 11:20:20AM -0700, Rohit Jain wrote:
>
> On 06/01/2017 05:37 AM, Peter Zijlstra wrote:
> > On Thu, Jun 01, 2017 at 02:28:27PM +0200, Peter Zijlstra wrote:
> > > On Wed, May 31, 2017 at 03:19:46PM -0700, Rohit Jain wrote:
> > >
> > > > > > 2) This scaled capacity is
On Fri, Jun 02, 2017 at 11:20:20AM -0700, Rohit Jain wrote:
>
> On 06/01/2017 05:37 AM, Peter Zijlstra wrote:
> > On Thu, Jun 01, 2017 at 02:28:27PM +0200, Peter Zijlstra wrote:
> > > On Wed, May 31, 2017 at 03:19:46PM -0700, Rohit Jain wrote:
> > >
> > > > > > 2) This scaled capacity is
On 06/02, Avaneesh Kumar Dwivedi wrote:
> Two different processors on a SOC need to switch memory ownership
> during load/unload. To enable this, level second memory map table
second level page tables instead of level second memory map table
> need to be updated, which is done by secure layer.
>
From: Jon Mason
Date: Wed, 31 May 2017 15:43:30 -0400
> use of_mdio_parse_addr() in place of an OF read of reg and a bounds
> check (which is litterally the exact same thing that
> of_mdio_parse_addr() does)
>
> Signed-off-by: Jon Mason
Applied,
On 06/02, Avaneesh Kumar Dwivedi wrote:
> Two different processors on a SOC need to switch memory ownership
> during load/unload. To enable this, level second memory map table
second level page tables instead of level second memory map table
> need to be updated, which is done by secure layer.
>
From: Jon Mason
Date: Wed, 31 May 2017 15:43:30 -0400
> use of_mdio_parse_addr() in place of an OF read of reg and a bounds
> check (which is litterally the exact same thing that
> of_mdio_parse_addr() does)
>
> Signed-off-by: Jon Mason
Applied, thanks Jon.
On Fri, 26 May 2017, Boris Ostrovsky wrote:
> On 05/19/2017 07:22 PM, Stefano Stabellini wrote:
> > +
> > static void pvcalls_back_work(struct work_struct *work)
> > {
> > + struct pvcalls_back_priv *priv = container_of(work,
> > + struct pvcalls_back_priv, register_work);
> > +
On Fri, 26 May 2017, Boris Ostrovsky wrote:
> On 05/19/2017 07:22 PM, Stefano Stabellini wrote:
> > +
> > static void pvcalls_back_work(struct work_struct *work)
> > {
> > + struct pvcalls_back_priv *priv = container_of(work,
> > + struct pvcalls_back_priv, register_work);
> > +
From: thor.tha...@linux.intel.com
Date: Wed, 31 May 2017 14:28:47 -0500
> From: Thor Thayer
>
> Fix NETDEV WATCHDOG timeout on startup by adding missing register
> writes that properly setup SGMII.
>
> Signed-off-by: Thor Thayer
From: thor.tha...@linux.intel.com
Date: Wed, 31 May 2017 14:28:47 -0500
> From: Thor Thayer
>
> Fix NETDEV WATCHDOG timeout on startup by adding missing register
> writes that properly setup SGMII.
>
> Signed-off-by: Thor Thayer
Applied, thank you.
On Mon, Apr 17, 2017 at 3:36 PM, John Stultz wrote:
> On Fri, Feb 24, 2017 at 2:46 PM, John Stultz wrote:
>> Hey John,
>> So after the USB tree landed in 4.11-rc, I've been seeing the
>> following warning at bootup.
>>
>> It seems the
On Mon, Apr 17, 2017 at 3:36 PM, John Stultz wrote:
> On Fri, Feb 24, 2017 at 2:46 PM, John Stultz wrote:
>> Hey John,
>> So after the USB tree landed in 4.11-rc, I've been seeing the
>> following warning at bootup.
>>
>> It seems the fifo_mem/total_fifo_size value on hikey is 1920, but I'm
>>
Quoting Matt Brown (m...@nmatt.com):
> On 6/2/17 12:57 PM, Serge E. Hallyn wrote:
> > I'm not quite sure what you're asking for here. Let me offer a precise
> > strawman design. I'm sure there are problems with it, it's just a starting
> > point.
> >
> > system-wide whitelist (for now
On 06/01/2017 05:37 AM, Peter Zijlstra wrote:
On Thu, Jun 01, 2017 at 02:28:27PM +0200, Peter Zijlstra wrote:
On Wed, May 31, 2017 at 03:19:46PM -0700, Rohit Jain wrote:
2) This scaled capacity is normalized and mapped into buckets.
Why?
And its not at all clear why you'd need
that to
Quoting Matt Brown (m...@nmatt.com):
> On 6/2/17 12:57 PM, Serge E. Hallyn wrote:
> > I'm not quite sure what you're asking for here. Let me offer a precise
> > strawman design. I'm sure there are problems with it, it's just a starting
> > point.
> >
> > system-wide whitelist (for now
On 06/01/2017 05:37 AM, Peter Zijlstra wrote:
On Thu, Jun 01, 2017 at 02:28:27PM +0200, Peter Zijlstra wrote:
On Wed, May 31, 2017 at 03:19:46PM -0700, Rohit Jain wrote:
2) This scaled capacity is normalized and mapped into buckets.
Why?
And its not at all clear why you'd need
that to
From: Jani Nikula
Date: Wed, 31 May 2017 18:50:43 +0300
> From: Chris Wilson
>
> An error during suspend (e100e_pm_suspend),
...
> lead to complete failure:
...
> The unwind failures stems from commit 2800209994f8 ("e1000e: Refactor PM
>
From: Jani Nikula
Date: Wed, 31 May 2017 18:50:43 +0300
> From: Chris Wilson
>
> An error during suspend (e100e_pm_suspend),
...
> lead to complete failure:
...
> The unwind failures stems from commit 2800209994f8 ("e1000e: Refactor PM
> flows"), but it may be a later patch that introduced
Hi,
Tested with comparing decompiled DTBs (dtx_diff). No differences.
Best regards,
Krzysztof
Krzysztof Kozlowski (2):
ARM: dts: exynos: Use human-friendly symbols for interrupt flags in
board sources
ARM: dts: exynos: Use human-friendly symbols for GIC interrupt
properties
Hi,
Tested with comparing decompiled DTBs (dtx_diff). No differences.
Best regards,
Krzysztof
Krzysztof Kozlowski (2):
ARM: dts: exynos: Use human-friendly symbols for interrupt flags in
board sources
ARM: dts: exynos: Use human-friendly symbols for GIC interrupt
properties
Replace hard-coded values of interrupt flags with respective macros from
header to increase code readability.
Suggested-by: Marek Szyprowski
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos3250-monk.dts | 6 +++---
Replace hard-coded values of type of GIC interrupt and its flags with
respective macros from header to increase code readability.
Suggested-by: Marek Szyprowski
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5.dtsi| 84
Replace hard-coded values of interrupt flags with respective macros from
header to increase code readability.
Suggested-by: Marek Szyprowski
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos3250-monk.dts | 6 +++---
arch/arm/boot/dts/exynos3250-rinato.dts |
Replace hard-coded values of type of GIC interrupt and its flags with
respective macros from header to increase code readability.
Suggested-by: Marek Szyprowski
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5.dtsi| 84 +++
From: Liu Xiang
Date: Wed, 31 May 2017 23:06:42 +0800
> On the DM9000B, dm9000_phy_write() is called after the main spinlock
> is held, during the dm9000_timeout() routine. Spinlock recursion
> occurs because the main spinlock is requested again in
> dm9000_phy_write(). So
From: Liu Xiang
Date: Wed, 31 May 2017 23:06:42 +0800
> On the DM9000B, dm9000_phy_write() is called after the main spinlock
> is held, during the dm9000_timeout() routine. Spinlock recursion
> occurs because the main spinlock is requested again in
> dm9000_phy_write(). So spinlock should be
Add a new USB Phy driver for Broadcom STB SoCs. This driver
supports Broadcom STB ARM and MIPS SoCs. This driver in
combination with the Broadcom STB ohci, ehci and xhci
drivers will enable USB1.1, USB2.0 and USB3.0 support.
This Phy driver also supports the Broadcom UDC gadget
driver.
Add a new USB Phy driver for Broadcom STB SoCs. This driver
supports Broadcom STB ARM and MIPS SoCs. This driver in
combination with the Broadcom STB ohci, ehci and xhci
drivers will enable USB1.1, USB2.0 and USB3.0 support.
This Phy driver also supports the Broadcom UDC gadget
driver.
Signed-off-by: Al Cooper
---
drivers/soc/bcm/brcmstb/common.c| 12
include/linux/soc/brcmstb/brcmstb.h | 10 ++
2 files changed, 22 insertions(+)
diff --git a/drivers/soc/bcm/brcmstb/common.c b/drivers/soc/bcm/brcmstb/common.c
index b6195fd..184dbf5
Signed-off-by: Al Cooper
---
drivers/soc/bcm/brcmstb/common.c| 12
include/linux/soc/brcmstb/brcmstb.h | 10 ++
2 files changed, 22 insertions(+)
diff --git a/drivers/soc/bcm/brcmstb/common.c b/drivers/soc/bcm/brcmstb/common.c
index b6195fd..184dbf5 100644
---
Add DT bindings document for Broadcom STB USB PHYs
Signed-off-by: Al Cooper
---
.../bindings/phy/brcm,brcmstb-usb-phy.txt | 37 ++
1 file changed, 37 insertions(+)
create mode 100644
Add DT bindings document for Broadcom STB USB PHYs
Signed-off-by: Al Cooper
---
.../bindings/phy/brcm,brcmstb-usb-phy.txt | 37 ++
1 file changed, 37 insertions(+)
create mode 100644
Documentation/devicetree/bindings/phy/brcm,brcmstb-usb-phy.txt
diff --git
Add a new USB Phy driver for Broadcom STB SoCs. This driver
supports Broadcom STB ARM and MIPS SoCs. This driver in
combination with the Broadcom STB ohci, ehci and xhci
drivers will enable USB1.1, USB2.0 and USB3.0 support.
This Phy driver also supports the Broadcom UDC gadget
driver.
Al Cooper
Add a new USB Phy driver for Broadcom STB SoCs. This driver
supports Broadcom STB ARM and MIPS SoCs. This driver in
combination with the Broadcom STB ohci, ehci and xhci
drivers will enable USB1.1, USB2.0 and USB3.0 support.
This Phy driver also supports the Broadcom UDC gadget
driver.
Al Cooper
Add entry for k3-dma driver and i2s/hdmi audio devices.
This enables HDMI audio output.
Cc: Zhangfei Gao
Cc: Liam Girdwood
Cc: Mark Brown
Cc: Jaroslav Kysela
Cc: Takashi Iwai
Cc: Wei Xu
Add entry for k3-dma driver and i2s/hdmi audio devices.
This enables HDMI audio output.
Cc: Zhangfei Gao
Cc: Liam Girdwood
Cc: Mark Brown
Cc: Jaroslav Kysela
Cc: Takashi Iwai
Cc: Wei Xu
Cc: Rob Herring
Cc: Andy Green
Cc: Dave Long
Cc: Guodong Xu
Cc: Antonio Borneo
Signed-off-by: John
On Tue, May 23, 2017 at 8:04 PM, Xinliang Liu wrote:
> On 24 May 2017 at 00:40, John Stultz wrote:
>>
>> This fixes a regression introduced by ebc944613567 ("drm:
>> convert drivers to use drm_of_find_panel_or_bridge") that was
>> recently merged,
On Fri, 2017-06-02 at 17:04 +0300, Mika Westerberg wrote:
> Hi,
>
> This is a third version of the patch series adding support for
> Thunderbolt
> security levels and NVM firmware upgrade. PCs running Intel Falcon
> Ridge or
> newer need these in order to connect devices if the security level is
On Fri, Jun 02, 2017 at 05:46:22AM -0700, Tahsin Erdogan wrote:
> > Hmm... normally we'd supply sbi->s_csum_seed as the second argument so
> > that the metadata checksum value also has the fs uuid stamped into it.
>
> I have thought about using sbi->s_csum_seed and was a little hesitant
> because
On Tue, May 23, 2017 at 8:04 PM, Xinliang Liu wrote:
> On 24 May 2017 at 00:40, John Stultz wrote:
>>
>> This fixes a regression introduced by ebc944613567 ("drm:
>> convert drivers to use drm_of_find_panel_or_bridge") that was
>> recently merged, causing HDMI output to not work.
>>
>> For the
On Fri, 2017-06-02 at 17:04 +0300, Mika Westerberg wrote:
> Hi,
>
> This is a third version of the patch series adding support for
> Thunderbolt
> security levels and NVM firmware upgrade. PCs running Intel Falcon
> Ridge or
> newer need these in order to connect devices if the security level is
On Fri, Jun 02, 2017 at 05:46:22AM -0700, Tahsin Erdogan wrote:
> > Hmm... normally we'd supply sbi->s_csum_seed as the second argument so
> > that the metadata checksum value also has the fs uuid stamped into it.
>
> I have thought about using sbi->s_csum_seed and was a little hesitant
> because
These can be marked as const * const.
Cc: Neil Armstrong
Cc: Jerome Brunet
Signed-off-by: Stephen Boyd
---
drivers/clk/meson/gxbb.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
These can be marked as const * const.
Cc: Neil Armstrong
Cc: Jerome Brunet
Signed-off-by: Stephen Boyd
---
drivers/clk/meson/gxbb.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/clk/meson/gxbb.c b/drivers/clk/meson/gxbb.c
index 2919a0e044a5..36c0e455437e
From: Sean Wang
By default, the relevant board with MediaTek MT7622 SoC is equipped with
MediaTek MT6380 PMIC. So the series enables related driver allows the
MT6380 can be accessed and controlled through MediaTek PMIC wrapper by
those function drivers on MT7622 SoC.
From: Sean Wang
By default, the relevant board with MediaTek MT7622 SoC is equipped with
MediaTek MT6380 PMIC. So the series enables related driver allows the
MT6380 can be accessed and controlled through MediaTek PMIC wrapper by
those function drivers on MT7622 SoC.
Patch 1-2: Update
From: Sean Wang
Signed-off-by: Chenglin Xu
Signed-off-by: Sean Wang
---
Documentation/devicetree/bindings/soc/mediatek/pwrap.txt | 4
1 file changed, 4 insertions(+)
diff --git
From: Sean Wang
Signed-off-by: Chenglin Xu
Signed-off-by: Sean Wang
---
Documentation/devicetree/bindings/soc/mediatek/pwrap.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/mediatek/pwrap.txt
From: Sean Wang
Add MediaTek MT6380 regulator becoming one of PMIC wrapper slave
and also add extra new regmap_config of 32-bit mode for MT6380
since old regmap_config of 16-bit mode can't be fit into the need.
Signed-off-by: Chenglin Xu
From: Chenglin Xu
Add the registers, callbacks and data structures required to make the
PMIC wrapper work on MT7622.
Signed-off-by: Chenglin Xu
Signed-off-by: Chen Zhong
Signed-off-by: Sean Wang
From: Sean Wang
Add MediaTek MT6380 regulator becoming one of PMIC wrapper slave
and also add extra new regmap_config of 32-bit mode for MT6380
since old regmap_config of 16-bit mode can't be fit into the need.
Signed-off-by: Chenglin Xu
Signed-off-by: Chen Zhong
Signed-off-by: Sean Wang
---
From: Chenglin Xu
Add the registers, callbacks and data structures required to make the
PMIC wrapper work on MT7622.
Signed-off-by: Chenglin Xu
Signed-off-by: Chen Zhong
Signed-off-by: Sean Wang
---
drivers/soc/mediatek/mtk-pmic-wrap.c | 180 +++
1 file
From: Chenglin Xu
The MT6380 is a regulator found those boards with MediaTek MT7622 SoC
It is connected as a slave to the SoC using MediaTek PMIC wrapper which
is the common interface connecting with Mediatek made various PMICs.
Signed-off-by: Chenglin Xu
From: Chenglin Xu
The MT6380 is a regulator found those boards with MediaTek MT7622 SoC
It is connected as a slave to the SoC using MediaTek PMIC wrapper which
is the common interface connecting with Mediatek made various PMICs.
Signed-off-by: Chenglin Xu
Signed-off-by: Sean Wang
---
From: Sean Wang
Some regulators such as MediaTek MT6380 has to be read in 32-bit mode.
So the patch adds pwrap_read32, rename old pwrap_read into pwrap_read16
and one function pointer is introduced for increasing flexibility allowing
the determination which mode is used
From: Sean Wang
Some regulators such as MediaTek MT6380 has to be read in 32-bit mode.
So the patch adds pwrap_read32, rename old pwrap_read into pwrap_read16
and one function pointer is introduced for increasing flexibility allowing
the determination which mode is used by the pwrap slave
501 - 600 of 1668 matches
Mail list logo