From: Colin Ian King
The pointer l2_hdr is being assigned to itself, this is redundant
and can be removed.
Addresses-Coverity: ("Evaluation order violation")
Signed-off-by: Colin Ian King
---
drivers/net/ethernet/hisilicon/hns3/hns3_enet.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
* Yan Zhao (yan.y.z...@intel.com) wrote:
> This feature implements the version attribute for Intel's vGPU mdev
> devices.
>
> version attribute is rw.
> It's used to check device compatibility for two mdev devices.
> version string format and length are private for vendor driver. vendor
> driver
On Wed, May 08, 2019 at 07:58:26AM +0200, hotwater...@tutanota.com wrote:
> Hello guys, any updates on suspend issue?
Please, do not top-post.
The patch you mentioned is in a queue to be submitted after merge window closes.
Be patient.
--
With Best Regards,
Andy Shevchenko
On Wed, 24 Apr 2019, Gwendal Grignou wrote:
> Add a IIO driver that reports the angle between the lid and the base for
> ChromeOS convertible device.
>
> Tested on eve with ToT EC firmware.
> Check driver is loaded and lid angle is correct.
>
> Signed-off-by: Gwendal Grignou
> ---
> Changes in
Hi Jose,
> -Original Message-
> From: Jose Abreu
> Sent: Wednesday, May 8, 2019 10:29 AM
> To: Eugeniy Paltsev ; jose.ab...@synopsys.com;
> linux-kernel@vger.kernel.org;
> Vineet Gupta ; devicet...@vger.kernel.org;
> linux-snps-...@lists.infradead.org
> Cc: joao.pi...@synopsys.com;
Hi Stephan,
We think the cast is fine, and it cannot guarantee the buf is
word-align.
I reference multiple rng driver's implementation and found it's common
usage for this. So it might be general usage for community. Is there any
suggestion that is more appropriate?
Thanks
A bug was introduced by commit b3b576461864 ("tty: serial_core: convert
uart_open to use tty_port_open"). It caused a constant warning printed
into the system log regarding the tty and port counter mismatch:
[ 21.644197] ttyS ttySx: tty_port_close_start: tty->count = 1 port count = 2
in case
This patch add HDP PHY Controller related nodes on the LS1028ARDB.
Now LS1028ARDB on DP has following features:
- Supports 4 dp lane channel and lane mapping is 1-0-3-2.
- By default, the pixel link rate value's 27Mhz.
- By default, support the resoluions are 4k@60,1080p@60,720p@60,
480p@60. also
Add DT bindings documentmation for the HDP-TX PHY controller. The describes
which could be found on NXP Layerscape ls1028a platform.
Signed-off-by: Wen He
---
.../devicetree/bindings/display/fsl,hdp.txt | 56 +++
1 file changed, 56 insertions(+)
create mode 100644
This patch enables the HDP controller driver on the LS1028A.
Signed-off-by: Alison Wang
Signed-off-by: Wen He
---
.../arm64/boot/dts/freescale/fsl-ls1028a.dtsi | 25 +++
1 file changed, 25 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
This patch add HDP PHY Controller related nodes on the LS1028AQDS.
Now LS1028AQDS on DP has following features:
- Supports 4 dp lane channel and lane mapping is 1-0-3-2.
- By default, the pixel link rate value's 27Mhz.
- By default, support the resoluions are 4k@60,1080p@60,720p@60,
480p@60. also
Commit 01fdf179f4b0 ("usb: core: skip interfaces disabled in devicetree")
add support for disabling given USB device interface by adding nodes to
the USB host controller device. The mentioned commit however identifies
the given USB interface node only by the 'reg' property in the host
controller
The LS1028A has a LCD controller and Displayport interface that
connects to eDP and Displayport connectors on the LS1028A board.
This patch enables the LCD controller driver on the LS1028A.
Signed-off-by: Alison Wang
Signed-off-by: Wen He
Reviewed-by: Liviu Dudau
Reviewed-by: Rob Herring
---
On Thu, May 02, 2019 at 01:50:20PM +0300, Alexander Shishkin wrote:
> Hi Peter,
>
> New PEBS feature: output to Intel PT stream instead of the DS area. It's
> theoretically useful in virtualized environments, where DS area can't be
> used. It's also good for those who are interested in
The patch
spi: rockchip: turn down tx dma bursts
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus
The following changes since commit 37624b58542fb9f2d9a70e6ea006ef8a5f66c30b:
Linux 5.1-rc7 (2019-04-28 17:04:13 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git tags/usb-5.2-rc1
for you to fetch changes up to
Hello.
We are again getting corrupted reports where message from WARN() is missing.
For example, https://syzkaller.appspot.com/text?tag=CrashLog=1720cac8a0
was
titled as "WARNING in cgroup_exit" because the
"WARNING: CPU: 0 PID: 7870 at kernel/cgroup/cgroup.c:6008
cgroup_exit+0x51a/0x5d0"
On Fri, 19 Apr 2019, Chen-Yu Tsai wrote:
> From: Chen-Yu Tsai
>
> The AXP803 has a VBUS power input. Its functionality is the same as the
> one found in the AXP813. Now that the axp20x_usb_power driver supports
> this variant, we can add an mfd cell for it to use it.
>
> Signed-off-by: Chen-Yu
On Wed, May 08, 2019 at 12:13:01PM +0200, Sebastian Reichel wrote:
> On Wed, May 08, 2019 at 03:09:36PM +0900, Mark Brown wrote:
> > I'd have to send all mail out via kernel.org to do that, or persuade a
> > MTA to route mail differently based on contents which seems interesting
> > - I inject
On Fri, 26 Apr 2019, Steve Twiss wrote:
> Mismatch between what is found in the Datasheets for DA9063 and DA9063L
> provided by Dialog Semiconductor, and the register names provided in the
> MFD registers file. The changes are for the OTP (one-time-programming)
> control registers. The two naming
The following changes since commit 085b7755808aa11f78ab9377257e1dad2e6fa4bb:
Linux 5.1-rc6 (2019-04-21 10:45:57 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tags/tty-5.2-rc1
for you to fetch changes up to
On Thu, 18 Apr 2019, Jan Kiszka wrote:
> From: Su Bao Cheng
>
> Since there are more IOT2040 variants with identical hardware but
> different asset tags, the asset tag matching should be adjusted to
> support them.
>
> For the board name "SIMATIC IOT2000", currently there are 2 types of
>
> -Original Message-
> From: Wen He
> Sent: 2019年5月8日 17:42
> To: dri-de...@lists.freedesktop.org; p.za...@pengutronix.de
> Cc: Leo Li ; Wen He
> Subject: [v1] gpu: ipu-v3: allow to build with ARCH_LAYERSCAPE
>
> The new LS1028A DP driver code causes a link failure when DRM_IMX
On Tue, 23 Apr 2019, Kefeng Wang wrote:
> Using dev_get_drvdata directly.
>
> Cc: Andy Gross
> Cc: David Brown
> Cc: Lee Jones
> Cc: linux-arm-...@vger.kernel.org
> Signed-off-by: Kefeng Wang
> ---
> drivers/mfd/ssbi.c | 2 +-
> drivers/mfd/t7l66xb.c | 12
>
The subject line is not correct. This is an MFD driver.
When submitting you should follow the convention for the subsystem you
are patching against. The following command is helpful:
`git log --oneline -- `
I will fix it for you this time (and for the other patch I see).
On Mon, 22 Apr
On Wed, May 08, 2019 at 03:09:36PM +0900, Mark Brown wrote:
> On Tue, May 07, 2019 at 02:07:30PM +0200, Sebastian Reichel wrote:
>
> > FWIW, I send out kernel.org mails via mail.kernel.org. Konstantin
> > added that service in 2014. You can get a password with
>
> > ssh g...@gitolite.kernel.org
On Wed, 8 May 2019 at 11:45, Lukasz Luba wrote:
>
>
> On 5/8/19 9:19 AM, Krzysztof Kozlowski wrote:
> > On Tue, 7 May 2019 at 19:04, Rob Herring wrote:
> >>> +- devfreq-events : phandles of the PPMU events used by the controller.
> >>> +- samsung,syscon-chipid : phandle of the ChipID used by the
On Wed, 8 May 2019 at 11:50, Lukasz Luba wrote:
>
>
> On 5/8/19 9:22 AM, Krzysztof Kozlowski wrote:
> > On Mon, 6 May 2019 at 17:12, Lukasz Luba wrote:
> >>
> >> In order get the clock by phandle and use it with regmap it needs to be
> >> compatible with syscon. The DMC driver uses two registers
Add a mailing list for patch reviews and discussions related to TEE
subsystem.
Signed-off-by: Sumit Garg
---
MAINTAINERS | 3 +++
1 file changed, 3 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 920a0a1..c05dff7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11556,11 +11556,13 @@
On Mon, May 06, 2019 at 08:50:45AM +0200, Johannes Thumshirn wrote:
> Acked-by: Johannes Thumshirn
Queued, thanks.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Hi
On 2019-05-07 15:24, Måns Rullgård wrote:
> Marek Szyprowski writes:
>> Commit 01fdf179f4b0 ("usb: core: skip interfaces disabled in devicetree")
>> add support for disabling given USB device interface by adding nodes to
>> the USB host controller device. The mentioned commit however
Hi,
On Wed, May 08, 2019 at 03:09:36PM +0900, Mark Brown wrote:
> On Tue, May 07, 2019 at 02:07:30PM +0200, Sebastian Reichel wrote:
> > FWIW, I send out kernel.org mails via mail.kernel.org. Konstantin
> > added that service in 2014. You can get a password with
>
> > ssh
This patch changes the order of checks when initializing the device CPU.
We want first to check if we need to load the F/W, and only if we need to,
then we want to check the status of the CPU boot program.
Signed-off-by: Oded Gabbay
---
drivers/misc/habanalabs/goya/goya.c | 6 +++---
1 file
On 5/8/19 9:25 AM, Krzysztof Kozlowski wrote:
> On Mon, 6 May 2019 at 17:12, Lukasz Luba wrote:
>>
>> Add description of Dynamic Memory Controller and PPMU counters.
>> They are used by exynos5422-dmc driver.
>> There is a definition of the memory chip, which is then used during
>> calculation
On 5/8/19 9:22 AM, Krzysztof Kozlowski wrote:
> On Mon, 6 May 2019 at 17:12, Lukasz Luba wrote:
>>
>> In order get the clock by phandle and use it with regmap it needs to be
>> compatible with syscon. The DMC driver uses two registers from clock
>> register set and needs the regmap of them.
>>
On Tue, May 07, 2019 at 01:33:06PM -0700, Linus Torvalds wrote:
> On Tue, May 7, 2019 at 10:59 AM Greg KH wrote:
> >
> > All of these have been in linux-next for a while with no reported
> > issues, other than an odd gcc warning for one of the new drivers that
> > should be fixed up soon.
>
>
On Tue, Apr 23, 2019 at 04:26:36PM +0200, Sebastian Andrzej Siewior wrote:
> In commit 4b53a3412d66 ("sched/core: Remove the tsk_nr_cpus_allowed()
> wrapper") the tsk_nr_cpus_allowed() wrapper was removed. There was not
> much difference in !RT but in RT we used this to implement
>
> On Wed, 8 May 2019 09:16:38 +, Rob Herring wrote:
> On Tue, 7 May 2019 09:16:38 +, Robin Gong wrote:
> > Add i.mx6ul and i.mx6sx compatible name.
> >
> > Signed-off-by: Robin Gong
> > ---
> > Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt | 2 ++
> > 1 file changed, 2
On 5/8/19 9:19 AM, Krzysztof Kozlowski wrote:
> On Tue, 7 May 2019 at 19:04, Rob Herring wrote:
>>> +- devfreq-events : phandles of the PPMU events used by the controller.
>>> +- samsung,syscon-chipid : phandle of the ChipID used by the controller.
>>> +- samsung,syscon-clk : phandle of the
Le 04/05/2019 à 18:48, Colin King a écrit :
From: Colin Ian King
Currently an int is being shifted and the result is being cast to a u64
which leads to undefined behaviour if the shift is more than 31 bits. Fix
this by casting the integer value 1 to u64 before the shift operation.
Steven Rostedt writes:
> [
> This is the non-RFC version.
>
> It went through and passed all my tests. If there's no objections
> I'm going to include this in my pull request. I still have patches
> in my INBOX that may still be included, so I need to run those through
> my tests as
On 18/04/2019 14:57, Zhen Lei wrote:
First, add build option IOMMU_DEFAULT_{LAZY|STRICT}, so that we have the
opportunity to set {lazy|strict} mode as default at build time. Then put
the three config options in an choice, make people can only choose one of
the three at a time.
The default IOMMU
On 05/08/19 at 11:04am, Borislav Petkov wrote:
> On Wed, May 08, 2019 at 04:24:18PM +0800, Baoquan He wrote:
> > I think this's worth noticing stable tree:
> >
> > Cc: sta...@vger.kernel.org
>
> Fixes: ?
Not sure which commit validated 5-level.
Hi Kirill,
Is this commit OK?
Fiexes:
On Thu, May 02, 2019 at 01:50:22PM +0300, Alexander Shishkin wrote:
> The output setting is per-CPU, so all PEBS events must be either writing
> to PT or to the DS area, so in order to not mess up the event scheduling,
> we fall back to the latter in case both types of events are scheduled in.
>
Hi Krzysztof,
On 5/8/19 9:11 AM, Krzysztof Kozlowski wrote:
> ())On Mon, 6 May 2019 at 17:12, Lukasz Luba
> wrote:
>>
>> This patch adds driver for Exynos5422 Dynamic Memory Controller.
>> The driver provides support for dynamic frequency and voltage scaling for
>> DMC and DRAM. It supports
On 05/05/2019 19:12, Dmitry Osipenko wrote:
> The DMA_PREP_INTERRUPT flag means that descriptor's callback should be
> invoked upon transfer completion and that's it. For some reason driver
> completely disables the hardware interrupt handling, leaving channel in
> unusable state if transfer is
On Wed, 8 May 2019 11:08:55 +0200
Juri Lelli wrote:
> On 06/05/19 06:48, Luca Abeni wrote:
> > From: luca abeni
> >
> > Instead of considering the "static CPU bandwidth" allocated to
> > a SCHED_DEADLINE task (ratio between its maximum runtime and
> > reservation period), try to use the
I'm announcing the release of the 4.19.41 kernel.
All users of the 4.19 kernel series must upgrade.
The updated 4.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.19.y
and can be browsed at the normal kernel.org git web
I'm announcing the release of the 5.0.14 kernel.
All users of the 5.0 kernel series must upgrade.
The updated 5.0.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.0.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/driver-api/usb/power-management.rst
b/Documentation/driver-api/usb/power-management.rst
index 79beb807996b..4a74cf6f2797 100644
--- a/Documentation/driver-api/usb/power-management.rst
+++ b/Documentation/driver-api/usb/power-management.rst
@@ -370,11 +370,15 @@
diff --git a/Documentation/driver-api/usb/power-management.rst
b/Documentation/driver-api/usb/power-management.rst
index 79beb807996b..4a74cf6f2797 100644
--- a/Documentation/driver-api/usb/power-management.rst
+++ b/Documentation/driver-api/usb/power-management.rst
@@ -370,11 +370,15 @@
diff --git a/Documentation/driver-api/usb/power-management.rst
b/Documentation/driver-api/usb/power-management.rst
index 79beb807996b..4a74cf6f2797 100644
--- a/Documentation/driver-api/usb/power-management.rst
+++ b/Documentation/driver-api/usb/power-management.rst
@@ -370,11 +370,15 @@
On 08/05/19 10:14, luca abeni wrote:
> Hi Juri,
>
> On Wed, 8 May 2019 10:01:16 +0200
> Juri Lelli wrote:
>
> > Hi Luca,
> >
> > On 06/05/19 06:48, Luca Abeni wrote:
> > > From: luca abeni
> > >
> > > Currently, the scheduler tries to find a proper placement for
> > > SCHED_DEADLINE tasks
I'm announcing the release of the 4.14.117 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web
diff --git a/Documentation/usb/power-management.txt
b/Documentation/usb/power-management.txt
index 0a94ffe17ab6..b13e031beaa6 100644
--- a/Documentation/usb/power-management.txt
+++ b/Documentation/usb/power-management.txt
@@ -365,11 +365,15 @@ autosuspend the interface's device. When the usage
I'm announcing the release of the 4.9.174 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
Hi,
On 08-05-19 10:42, Andy Shevchenko wrote:
On Wed, May 8, 2019 at 10:48 AM Hans de Goede wrote:
On 07-05-19 22:17, Stephen Boyd wrote:
Quoting Hans de Goede (2019-05-06 08:05:42)
I guess this is urgent?
Somewhat, getting this into e.g. rc2 would be fine too, waiting till 5.3
would be
From: Alastair D'Silva
> Sent: 08 May 2019 08:02
> To: alast...@d-silva.org
...
> --- a/include/linux/printk.h
> +++ b/include/linux/printk.h
> @@ -480,13 +480,13 @@ enum {
> DUMP_PREFIX_OFFSET
> };
>
> -extern int hex_dump_to_buffer(const void *buf, size_t len, int rowsize,
> -
Hi Lee,
Sorry for the delay, this is a new version rebased on top of
for-mfd-next tree solvind the conflicts with due the already applied
patches.
The first version depends on:
- mfd: cros: Update EC protocol to match current EC code
- https://lore.kernel.org/patchwork/patch/1046363
But
Support Touchpad MCU as a special of CrOS EC devices. The current
Touchpad MCU is used on Eve Chromebook and used the same protocol as
other CrOS EC devices.
When a MCU has touchpad support (aka EC_FEATURE_TOUCHPAD), it is
instantiated as a special CrOS EC device with device name 'cros_tp'. So
Update the feature enum for the Chromebook Embedded Controller to the
latest version. Some of these enums are still not used in the kernel but
we might be also interested on have these enums up to date. Userspace
can use them to query the features to the EC via the cros-ec character
device.
While
Support Fingerprint MCU as a special of CrOS EC devices. The current FP
MCU uses the same EC SPI protocol v3 as other CrOS EC devices on a SPI
bus.
When a MCU has fingerprint support (aka EC_FEATURE_FINGERPRINT), it is
instantiated as a special CrOS EC device with device name 'cros_fp'. So
On Wed, May 08, 2019 at 05:01:44PM +1000, Alastair D'Silva wrote:
> From: Alastair D'Silva
>
> In order to support additional features in hex_dump_to_buffer, replace
> the ascii bool parameter with flags.
>
> Signed-off-by: Alastair D'Silva
> ---
> drivers/gpu/drm/i915/intel_engine_cs.c
On Thu, May 02, 2019 at 01:50:22PM +0300, Alexander Shishkin wrote:
> The output setting is per-CPU, so all PEBS events must be either writing
> to PT or to the DS area, so in order to not mess up the event scheduling,
> we fall back to the latter in case both types of events are scheduled in.
On Thu, May 02, 2019 at 01:50:22PM +0300, Alexander Shishkin wrote:
> If PEBS declares ability to output its data to Intel PT stream, use the
> aux_source attribute bit to enable PEBS data output to PT. This requires
> a PT event to be present and scheduled in the same context. Unlike the
> DS
Add a property usb-role-switch to tell the driver that use
USB Role Switch framework to handle the role switch,
it's useful when the driver has already supported other ways,
such as extcon framework etc.
Cc: Biju Das
Cc: Yu Chen
Signed-off-by: Chunfeng Yun
---
v3:
add property type, modify
On Wed, May 08, 2019 at 01:16:06PM +0530, Vinod Koul wrote:
> On 07-05-19, 17:49, Pierre-Louis Bossart wrote:
> >
> > > > The model here is that Master device is PCI or Platform device and then
> > > > creates a bus instance which has soundwire slave devices.
> > > >
> > > > So for any attribute
The patch
ASoC: hdmi-codec: remove ops dependency on the dai id
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
Hi Rob,
On 5/7/19 7:04 PM, Rob Herring wrote:
> On Mon, May 06, 2019 at 05:11:55PM +0200, Lukasz Luba wrote:
>> The patch adds description for DT binding for a new Exynos5422 Dynamic
>> Memory Controller device.
>>
>> Signed-off-by: Lukasz Luba
>> ---
>>
On Tue, May 7, 2019 at 3:53 PM Anders Roxell wrote:
> When building and CONFIG_X86 isn't set the compiler rightly complains
> about an unused varable 'i', see the warning below:
>
> ../drivers/hwtracing/intel_th/msu.c: In function ‘msc_buffer_win_alloc’:
>
The patch
dt-bindings: mfd: atmel-usart: add DMA bindings for USART in SPI mode
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in
The patch
spi: at91-usart: add DMA support
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus
The following changes since commit 085b7755808aa11f78ab9377257e1dad2e6fa4bb:
Linux 5.1-rc6 (2019-04-21 10:45:57 -0700)
are available in the git repository at:
https://github.com/c-sky/csky-linux.git tags/csky-for-linus-5.2-rc1
for you to fetch changes up to
On 06/05/19 06:48, Luca Abeni wrote:
> From: luca abeni
>
> Instead of considering the "static CPU bandwidth" allocated to
> a SCHED_DEADLINE task (ratio between its maximum runtime and
> reservation period), try to use the remaining runtime and time
> to scheduling deadline.
>
> Signed-off-by:
The patch
regulator: core: Slightly improve readability of _regulator_get_enable_time
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.3
All being well this means that it will be integrated into the linux-next
tree
The patch
regulator: max77650: Convert MAX77651 SBB1 to pickable linear range
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually
On Sat, Apr 13, 2019 at 11:15:18AM -0400, Paul Gortmaker wrote:
> This file is implicitly relying on an instance of including
> module.h from .
Please use subject lines matching the style for the subsystem. This
makes it easier for people to identify relevant patches.
signature.asc
On Wed, May 08, 2019 at 04:24:18PM +0800, Baoquan He wrote:
> I think this's worth noticing stable tree:
>
> Cc: sta...@vger.kernel.org
Fixes: ?
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
On Tue, May 07, 2019 at 04:01:15PM -0600, Fletcher Woodruff wrote:
> The rt5677 driver uses ACPI-style property names to read from the
> device API. However, these do not match the property names in _DSD
> used on the Chromebook Pixel 2015, which are closer to the Device Tree
> style. Unify the
The patch
ASoC: stm32: i2s: update pcm hardware constraints
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
Rob Herring [2019-05-07 11:06:43]:
Hi,
> > Honestly I don't know if it's necessary to have it, but so far address,
> > mac-address and local-mac-address properties provide this DT nodes, so I've
> > simply thought, that it would be good to have it for MAC address from NVMEM
> > as
> > well in
The patch
ASoC: stm32: i2s: manage identification registers
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
ASoC: hdmi-codec: remove reference to the current substream
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
The patch
ASoC: hdmi-codec: remove function name debug traces
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
ASoC: hdmi-codec: remove reference to the dai drivers in the private data
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually
The patch
sound: soc-acpi: fix implicit header use of module.h/export.h
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
On Wed, May 08, 2019 at 10:08:44AM +0200, Jerome Brunet wrote:
> On Wed, 2019-05-08 at 16:00 +0900, Mark Brown wrote:
> > The advantage of mutexes is that they are very simple and clear to
> > reason about. It is therefore unclear that this conversion to use
> > atomic variables is an
On Mon, May 06, 2019 at 04:19:16PM +0800, Yuyang Du wrote:
> Hi Peter,
>
> Let me post these small bits first while waiting for Frederic's patches
> to be merged.
>
They apply nicely and should show up in tip after the merge window
closes or thereabout.
Thanks!
> From: Peng Fan
> Sent: Wednesday, May 8, 2019 10:56 AM
>
> NXP i.MX8QXP is an ARMv8 SoC with a Cortex-M4 core inside as system
> controller(SCU), the ocotp controller is being controlled by the SCU, so Linux
> need use RPC to SCU for ocotp handling. This patch adds binding doc for i.MX8
> SCU
On May 8, 2019, at 2:34 AM, Sahitya Tummala wrote:
>
> The buffer_head (frames[0].bh) and it's corresping page can be
> potentially free'd once brelse() is done inside the for loop
> but before the for loop exits in dx_release(). It can be free'd
> in another context, when the page cache is
On Tue, Apr 30, 2019 at 06:06:36PM -0700, Yury Norov wrote:
> New design of inner bitmap_parse() allows to avoid
> calculating the size of a null-terminated string.
>
FWIW,
Reviewed-by: Andy Shevchenko
> Signed-off-by: Yury Norov
> ---
> include/linux/cpumask.h | 4 +---
> 1 file changed, 1
On Tue, Apr 30, 2019 at 06:06:31PM -0700, Yury Norov wrote:
> Introduce BITS_TO_U64, BITS_TO_U32 and BITS_TO_BYTES as they are handy
> in the following patches (BITS_TO_U32 specifically). Reimplement tools/
> version of the macros according to the kernel implementation.
>
> Also fix indentation
On Tue, Apr 30, 2019 at 06:06:35PM -0700, Yury Norov wrote:
> New version of bitmap_parse() is unified with bitmap_parse_list(),
> and therefore:
> - weakens rules on whitespaces and commas between hex chunks;
> - in addition to \0 allows using \n as the line ending symbol;
> - allows passing
On Tue, Apr 30, 2019 at 06:06:32PM -0700, Yury Norov wrote:
> The test is derived from bitmap_parselist()
> NO_LEN is reserved for use in following patches.
>
Reviewed-by: Andy Shevchenko
> Signed-off-by: Yury Norov
> ---
> lib/test_bitmap.c | 94
On Tue, Apr 30, 2019 at 06:06:33PM -0700, Yury Norov wrote:
> Currently we parse user data byte after byte which leads to
> overcomplicating of parsing algorithm. There are no performance
> critical users of bitmap_parse_user(), and so we can duplicate
> user data to kernel buffer and simply call
On Tue, Apr 30, 2019 at 06:06:30PM -0700, Yury Norov wrote:
> New function works like strchrnul() with a length limited strings.
>
Reviewed-by: Andy Shevchenko
> Signed-off-by: Yury Norov
> ---
> include/linux/string.h | 1 +
> lib/string.c | 17 +
> 2 files
On Tue, Apr 30, 2019 at 06:06:34PM -0700, Yury Norov wrote:
> bitmap_parse() is ineffective and full of opaque variables and opencoded
> parts. It leads to hard understanding and usage of it. This rework
> includes:
> - remove bitmap_shift_left() call from the cycle. Now it makes the
>
This patch removes some dead code that performs checks about variables
with hard-coded values.
The patch also moves the initialization of those variables to a separate
function, that will possibly have different values per ASIC.
Signed-off-by: Oded Gabbay
---
On Wed, May 8, 2019 at 10:48 AM Hans de Goede wrote:
> On 07-05-19 22:17, Stephen Boyd wrote:
> > Quoting Hans de Goede (2019-05-06 08:05:42)
> > I guess this is urgent?
>
> Somewhat, getting this into e.g. rc2 would be fine too, waiting till 5.3
> would be bad.
So, I can do it as a fixes for
Rob Herring [2019-05-07 11:44:57]:
Hi,
> > -- local-mac-address: the driver is designed to use the
> > of_get_mac_address api
> > - only if efuse-mac is 0. When efuse-mac is 0, the MAC
> > - address is obtained from local-mac-address. If this
> > -
601 - 700 of 811 matches
Mail list logo
