From: Rafael J. Wysocki
Currently, it is not valid to add a device link from a consumer
driver ->probe callback to a supplier that is still probing too, but
generally this is a valid use case. For example, if the consumer has
just acquired a resource that can only be available if the supplier
From: Rafael J. Wysocki
Calling rpm_put_suppliers() from pm_runtime_drop_link() is excessive
as it affects all suppliers of the consumer device and not just the
one pointed to by the device link being dropped. Worst case it may
cause the consumer device to stop working unexpectedly. Moreover,
From: Rafael J. Wysocki
Even though stateful device links are managed by the driver core in
principle, their creators are allowed and sometimes even expected
to drop references to them via device_link_del() or
device_link_remove(), but that doesn't really play well with the
"persistent" link
From: Rafael J. Wysocki
It is incorrect to call pm_runtime_get_sync() under
device_links_write_lock(), because it may end up trying to take
device_links_read_lock() while resuming the target device and that
will deadlock in the non-SRCU case, so avoid that by resuming the
supplier device in
From: Rafael J. Wysocki
After commit ead18c23c263 ("driver core: Introduce device links
reference counting"), if there is a link between the given supplier
and the given consumer already, device_link_add() will refcount it
and return it unconditionally without updating its flags. It is
From: Rafael J. Wysocki
After commit ead18c23c263 ("driver core: Introduce device links
reference counting"), if there is a link between the given supplier
and the given consumer already, device_link_add() will refcount it
and return it unconditionally. However, if the flags passed to
it on the
From: Rafael J. Wysocki
The device links used by rockchip-iommu and exynos-iommu are
completely managed by these drivers within the IOMMU framework,
so there is no reason to involve the driver core in the management
of these links.
For this reason, make rockchip-iommu and exynos-iommu pass
On Fri, Feb 01, 2019 at 11:42:42AM +1100, Tobin C. Harding wrote:
[snip]
This applies on top of Linus' tree
commit e74c98ca2d6a ('gfs2: Revert "Fix loop in gfs2_rbm_find"')
For this patch I doubt very much that it matters but for the record I
can't find mention in MAINTAINERS which tree
В Thu, 31 Jan 2019 21:46:48 +
Sowjanya Komatineni пишет:
> > It works with this change:
> >
> > diff --git a/drivers/i2c/busses/i2c-tegra.c
> > b/drivers/i2c/busses/i2c-tegra.c index fe5b89abc576..8e059e94b94e
> > 100644 --- a/drivers/i2c/busses/i2c-tegra.c +++
> >
Enable coresight support by adding device nodes for the
available source, sinks and channel blocks on MSM8998.
Signed-off-by: Sai Prakash Ranjan
---
For testing, all dependent patches are in below tree:
* https://github.com/saiprakash-ranjan/linux/tree/coresight-next
This depends on MSM8998
Add coresight components found on Qualcomm SDM845 SoC.
Signed-off-by: Sai Prakash Ranjan
---
For testing, all dependent patches are in below tree:
* https://github.com/saiprakash-ranjan/linux/tree/coresight-next
- Depends on AOSS QMP side channel patches by Bjorn Andersson [1] - [4].
- AMBA
В Thu, 31 Jan 2019 13:44:23 +0100
Thierry Reding пишет:
> On Wed, Jan 30, 2019 at 10:16:25PM -0800, Sowjanya Komatineni wrote:
> > This patch adds DMA support for Tegra I2C.
> >
> > Tegra I2C TX and RX FIFO depth is 8 words. PIO mode is used for
> > transfer size of the max FIFO depth and DMA
SDM845 has ETMv4.2 and can use the existing etm4x driver.
But the current etm driver checks only for ETMv4.0 and
errors out for other etm4x versions. This patch adds this
missing support to enable SoC's with ETMv4x to use same
driver by checking only the ETM architecture major version
number.
Instead of overriding the peripheral id(PID) check in AMBA
by hardcoding them in DT, add the PIDs to the ETM4x driver.
Here we use Unique Component Identifier(UCI) for MSM8996
since the ETM and CPU debug module shares the same PIDs.
SDM845 does not support CPU debug module.
Signed-off-by: Sai
Hi,
On Wed, Jan 30, 2019 at 02:42:29AM +0100, Andreas Färber wrote:
> Hi Alex,
>
> Am 29.01.19 um 13:57 schrieb Alexander Aring:
> > On Tue, Jan 29, 2019 at 06:01:27AM +0100, Andreas Färber wrote:
> >> EnOcean wireless technology is based on ASK (ERP1) and FSK (ERP2)
> >> modulations
> >> for
Add support for coresight CPU debug module on Qualcomm
Kryo CPUs. This patch adds the UCI entries for Kryo CPUs
found on MSM8996 which shares the same PIDs as ETMs.
Without this, below error is observed on MSM8996:
[5.429867] OF: graph: no port node found in /soc/debug@381
[5.429938]
From: Vivek Gautam
Enable coresight support by adding device nodes for the
available source, sinks and channel blocks on msm8996.
This also adds coresight cpu debug nodes.
Signed-off-by: Vivek Gautam
Signed-off-by: Sai Prakash Ranjan
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 434
This patch series adds support for coresight on SDM845, MSM8998, and MSM8996.
* Patch 1 adds device tree nodes for SDM845 coresight components.
* Patch 2 adds device tree nodes for MSM8998 coresight components.
* Patch 3 adds device tree nodes for MSM8996 coresight components.
* Patch 4
Hi all,
After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
drivers/gpu/drm/amd/amdgpu/../display/modules/power/power_helpers.c:160:9:
warning: #pragma pack (pop) encountered without matching #pragma pack (push)
[-Wpragmas]
#pragma pack(pop)
On 2/1/2019 6:17 AM, Sai Prakash Ranjan wrote:
On 1/31/2019 11:31 PM, Suzuki K Poulose wrote:
On 31/01/2019 14:22, Sai Prakash Ranjan wrote:
Add UCI table for coresight CPU debug module. This patch adds
the UCI entries for Kryo CPUs found on MSM8996 which shares
the same PIDs as ETMs.
On 1/31/2019 11:31 PM, Suzuki K Poulose wrote:
On 31/01/2019 14:22, Sai Prakash Ranjan wrote:
Add UCI table for coresight CPU debug module. This patch adds
the UCI entries for Kryo CPUs found on MSM8996 which shares
the same PIDs as ETMs.
Without this, below error is observed on MSM8996:
Hi Hans,
On 1/30/19 12:42 AM, Hans Verkuil wrote:
On 1/30/19 2:50 AM, shuah wrote:
On 1/29/19 2:43 AM, Hans Verkuil wrote:
On 1/29/19 12:48 AM, shuah wrote:
Hi Hans,
On 1/28/19 5:03 AM, Hans Verkuil wrote:
Hi Shuah,
On 1/24/19 9:32 PM, Shuah Khan wrote:
Media Device Allocator API to
On 1/31/2019 10:01 PM, Stephen Boyd wrote:
Quoting Sai Prakash Ranjan (2019-01-31 06:22:24)
diff --git a/drivers/hwtracing/coresight/coresight-cpu-debug.c
b/drivers/hwtracing/coresight/coresight-cpu-debug.c
index e8819d750938..915d86a39cee 100644
---
Currently when displaying /proc/slabinfo if any cache names are too long
then the output columns are not aligned. We could do something fancy to
get the maximum length of any cache name in the system or we could just
increase the hardcoded width. Currently it is 17 characters. Monitors
are wide
Quoting Joe Perches :
On Thu, 2019-01-31 at 12:40 +1100, tom burkart wrote:
Quoting Rodolfo Giometti :
Subject Re: [PATCH v14 2/3] dt-bindings: pps: pps-gpio PPS ECHO
implementation
I think this patch it's OK but I'm asking to myself if it should be
merged with
next one...
Internal injection testing crashed with a console log that said:
mce: [Hardware Error]: CPU 7: Machine Check Exception: f Bank 0:
bd8000100134
This caused a lot of head scratching because the MCACOD (bits 15:0) of that
status is a signature from an L1 data cache error. But Linux says that
> On Jan 31, 2019, at 4:08 PM, Borislav Petkov wrote:
>
> On Thu, Jan 31, 2019 at 10:19:54PM +, Nadav Amit wrote:
>> Meta-question: could you please review the entire patch-set? This is
>> actually v9 of this particular patch - it was part of a separate patch-set
>> before. I don’t think
On Friday, February 1, 2019 1:12:31 AM CET Greg Kroah-Hartman wrote:
> On Fri, Feb 01, 2019 at 12:50:58AM +0100, Rafael J. Wysocki wrote:
> > On Thursday, January 31, 2019 7:24:07 PM CET Greg Kroah-Hartman wrote:
> > > On Thu, Jan 31, 2019 at 05:02:05PM +0100, Rafael J. Wysocki wrote:
> > > > On
On Thu, Jan 31, 2019 at 02:57:34PM -0800, Andrew Morton wrote:
> On Thu, 31 Jan 2019 22:51:52 + Liviu Dudau wrote:
>
> > On Wed, Jan 30, 2019 at 08:51:42PM -0500, Qian Cai wrote:
> > >
> > >
> > > On 1/30/19 7:05 PM, Stephen Rothwell wrote:
> > > > In commit
> > > >
> > > > 6e9ed490d190
On Thu, Jan 31, 2019 at 04:23:59PM -0700, Shuah Khan wrote:
> tty_set_termios() has the following WARN_ON which can be triggered with a
> syscall to invoke TIOCSETD __NR_ioctl.
>
> WARN_ON(tty->driver->type == TTY_DRIVER_TYPE_PTY &&
> tty->driver->subtype == PTY_TYPE_MASTER);
>
The FAT32 File System Specification[1] states that:
If DIR_Name[0] == 0x00, then the directory entry is free, and there
are no allocated directory entries after this one.
The special 0 value, indicates to FAT file system driver code that
the rest of the entries in this directory
On Thu, Jan 31, 2019 at 1:47 PM Fabio Estevam wrote:
>
> Hi Andrey
>
> On Thu, Jan 31, 2019 at 7:11 PM Andrey Smirnov
> wrote:
> >
> > Now that the GPCv2 driver supports i.MX8MQ, make GPC default interrupt
> > parent.
> >
> > Signed-off-by: Andrey Smirnov
>
> Lucas has already submitted this
On Fri, Feb 01, 2019 at 12:50:58AM +0100, Rafael J. Wysocki wrote:
> On Thursday, January 31, 2019 7:24:07 PM CET Greg Kroah-Hartman wrote:
> > On Thu, Jan 31, 2019 at 05:02:05PM +0100, Rafael J. Wysocki wrote:
> > > On Thu, Jan 31, 2019 at 2:24 PM Greg Kroah-Hartman
> > > wrote:
> > > >
> > > >
On Thu, Jan 31, 2019 at 10:19:54PM +, Nadav Amit wrote:
> Meta-question: could you please review the entire patch-set? This is
> actually v9 of this particular patch - it was part of a separate patch-set
> before. I don’t think that the patch has changed since (the real) v1.
>
> These
On Fri, Feb 01, 2019 at 12:34:32AM +0100, Rafael J. Wysocki wrote:
> On Thursday, January 31, 2019 7:37:30 PM CET Matthias Kaehlcke wrote:
> > On Thu, Jan 31, 2019 at 11:14:03AM +0100, Rafael J. Wysocki wrote:
> > > On Thu, Jan 31, 2019 at 11:07 AM Viresh Kumar
> > > wrote:
> > > >
> > > > On
Hi all,
In commit
a93587b31e34 ("drm/amd/display: Only get the connector state for VRR when
toggled")
Fixes tag
Fixes: 3cc22f281318 ("drm/amdgpu: Set FreeSync state using drm VRR
properties")
has these problem(s):
- Target SHA1 does not exist
Maybe instead:
FIxes: bb47de736661
On Thu, Jan 31, 2019 at 03:27:32PM -0700, Jerry Hoemann wrote:
> So even if a system administrator is diligent and tests
> that a chosen kdump configuration works, that configuration
> might not work on some random reboot 7 months in the future.
Jerry, did you read the rest of the thread where
On 1/31/19 4:55 AM, Cornelia Huck wrote:
On Wed, 30 Jan 2019 12:48:46 -0500
Tony Krowiak wrote:
The current AP bus implementation periodically polls the AP configuration
to detect changes. When the AP configuration is dynamically changed via the
SE or an SCLP instruction, the changes will not
On 1/31/2019 4:41 PM, Logan Gunthorpe wrote:
On 2019-01-31 3:46 p.m., Dave Jiang wrote:
I believe irqbalance writes to the file /proc/irq/N/smp_affinity. So
maybe take a look at the code that starts from there and see if it would
have any impact on your stuff.
Ok, well on my system I can
On 2019-01-31 4:48 p.m., Dave Jiang wrote:
>
> On 1/31/2019 4:41 PM, Logan Gunthorpe wrote:
>>
>> On 2019-01-31 3:46 p.m., Dave Jiang wrote:
>>> I believe irqbalance writes to the file /proc/irq/N/smp_affinity. So
>>> maybe take a look at the code that starts from there and see if it would
>>>
On Thursday, January 31, 2019 7:24:07 PM CET Greg Kroah-Hartman wrote:
> On Thu, Jan 31, 2019 at 05:02:05PM +0100, Rafael J. Wysocki wrote:
> > On Thu, Jan 31, 2019 at 2:24 PM Greg Kroah-Hartman
> > wrote:
> > >
> > > On Thu, Jan 31, 2019 at 02:22:47PM +0100, Greg Kroah-Hartman wrote:
> > > > On
Hi Lukas,
Thinh Nguyen wrote:
> Bjorn Helgaas wrote:
>> [+cc linux-pci, linux-kernel]
>>
>> On Thu, Jan 31, 2019 at 11:21 AM Lukas F. Hartmann wrote:
>>> Hi Thinh,
>>>
>>> I'm writing you because you're the author in this commit:
>>>
On 2019-01-31 3:46 p.m., Dave Jiang wrote:
> I believe irqbalance writes to the file /proc/irq/N/smp_affinity. So
> maybe take a look at the code that starts from there and see if it would
> have any impact on your stuff.
Ok, well on my system I can write to the smp_affinity all day and the
On Thursday, January 31, 2019 7:37:30 PM CET Matthias Kaehlcke wrote:
> On Thu, Jan 31, 2019 at 11:14:03AM +0100, Rafael J. Wysocki wrote:
> > On Thu, Jan 31, 2019 at 11:07 AM Viresh Kumar
> > wrote:
> > >
> > > On 31-01-19, 11:03, Rafael J. Wysocki wrote:
> > > > On Thu, Jan 31, 2019 at 9:30 AM
Hi!
> > And without the n_gsm serdev support, it's a mess of some app
> > similar to [5] initializing n_gsm, trying to deal with the USB
> > PHY PM, dealing with Motorola custom packet numbering, kicking
> > GNSS device, feeding data to /dev/ugnss. Hmm I think I've already
> > been there just to
On 1/31/19 4:09 AM, Pierre Morel wrote:
On 30/01/2019 18:48, Tony Krowiak wrote:
The current AP bus implementation periodically polls the AP configuration
to detect changes. When the AP configuration is dynamically changed
via the
SE or an SCLP instruction, the changes will not be reflected to
On Thu, 2019-01-31 at 14:13 -0800, Evan Green wrote:
> diff --git a/drivers/block/loop.c b/drivers/block/loop.c
> index cf5538942834..a1ba555e3b92 100644
> --- a/drivers/block/loop.c
> +++ b/drivers/block/loop.c
> @@ -458,8 +458,13 @@ static void lo_complete_rq(struct request *rq)
>
> if
On Thu Jan 31 19, Linus Torvalds wrote:
On Thu, Jan 31, 2019 at 12:47 PM Jarkko Sakkinen
wrote:
I'll try it first thing when I wake up tomorrow (11PM in Finland ATM).
Thanks.
Appreciate for taking time on this.
Hey, it was my commit that broke it for you. Even if it happened to
work
On 1/31/19 2:25 PM, Thierry Reding wrote:
On Thu, Jan 31, 2019 at 10:35:54AM -0800, Bo Yan wrote:
The xavier CPU architecture includes 8 CPU cores organized in
4 clusters. Add cpu-map data for topology initialization, add
cache data for cache node creation in sysfs.
Signed-off-by: Bo Yan
On 1/30/19 1:32 PM, Sebastian Ott wrote:
On Wed, 30 Jan 2019, Tony Krowiak wrote:
+#if IS_ENABLED(CONFIG_ZCRYPT)
+void ap_bus_cfg_chg(void);
+#else
+#error "no CONFIG_ZCRYPT"
^
I don't think that's the right thing to do here.
I'd like to leave it. If somebody edits .config
and sets
Hi all,
On Fri, 1 Feb 2019 10:22:33 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the v4l-dvb tree got a conflict in:
>
> drivers/media/platform/vim2m.c
>
> between commit:
>
> 240809ef6630 ("media: vim2m: only cancel work if it is for right context")
>
> from Linus'
Hi all,
After merging the v4l-dvb tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/media/common/videobuf2/videobuf2-core.c: In function '__vb2_dqbuf':
drivers/media/common/videobuf2/videobuf2-core.c:1772:15: warning: unused
variable 'i' [-Wunused-variable]
On Thursday, January 31, 2019 3:30:24 PM CET Thierry Reding wrote:
>
> --Pk/CTwBz1VvfPIDp
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Thu, Jan 31, 2019 at 01:10:01PM +0100, Rafael J. Wysocki wrote:
> > On Thu,
tty_set_termios() has the following WARN_ON which can be triggered with a
syscall to invoke TIOCSETD __NR_ioctl.
WARN_ON(tty->driver->type == TTY_DRIVER_TYPE_PTY &&
tty->driver->subtype == PTY_TYPE_MASTER);
Reference:
On Thu, Jan 17, 2019 at 03:02:17PM +0800, YueHaibing wrote:
> Remove duplicated include.
>
> Signed-off-by: YueHaibing
Looks fine to me,
Reviewed-by: Darrick J. Wong
--D
> ---
> fs/xfs/xfs_trans_bmap.c | 1 -
> fs/xfs/xfs_trans_extfree.c | 1 -
> fs/xfs/xfs_trans_refcount.c | 1 -
>
Hi all,
Today's linux-next merge of the v4l-dvb tree got a conflict in:
drivers/media/platform/vim2m.c
between commit:
240809ef6630 ("media: vim2m: only cancel work if it is for right context")
from Linus' tree and commit:
b3e64e5b0778 ("media: vim2m: use per-file handler work queue")
On 1/31/19 8:33 AM, Johan Hovold wrote:
On Thu, Jan 31, 2019 at 04:18:33PM +0100, Marcel Holtmann wrote:
I agree with Al that this change doesn't make much sense. The WARN_ON
is there to catch any bugs leading to the termios being changed for a
master side pty. Those should bugs should be
On Thu, Jan 31, 2019 at 2:15 PM Andrew Morton wrote:
> On Tue, 29 Jan 2019 21:02:16 -0800 Dan Williams
> wrote:
[..]
> > Introduce shuffle_free_memory(), and its helper shuffle_zone(), to
> > perform a Fisher-Yates shuffle of the page allocator 'free_area' lists
> > when they are initially
On Thu, 31 Jan 2019 22:51:52 + Liviu Dudau wrote:
> On Wed, Jan 30, 2019 at 08:51:42PM -0500, Qian Cai wrote:
> >
> >
> > On 1/30/19 7:05 PM, Stephen Rothwell wrote:
> > > In commit
> > >
> > > 6e9ed490d190 ("mm/page_owner: fix for deferred struct page init")
> > >
> > > Fixes tag
> >
On 2019-01-31 3:39 p.m., Bjorn Helgaas wrote:
> I assume you'll merge this along with the rest of the series, so:
>
> Acked-by: Bjorn Helgaas
Thanks!
>> diff --git a/include/linux/msi.h b/include/linux/msi.h
>> index 784fb52b9900..6458ab049852 100644
>> --- a/include/linux/msi.h
>> +++
Hi Lukas,
Bjorn Helgaas wrote:
> [+cc linux-pci, linux-kernel]
>
> On Thu, Jan 31, 2019 at 11:21 AM Lukas F. Hartmann wrote:
>> Hi Thinh,
>>
>> I'm writing you because you're the author in this commit:
>>
On 1/31/2019 3:39 PM, Logan Gunthorpe wrote:
On 2019-01-31 1:58 p.m., Dave Jiang wrote:
On 1/31/2019 1:48 PM, Logan Gunthorpe wrote:
On 2019-01-31 1:20 p.m., Dave Jiang wrote:
Does this work when the system moves the MSI vector either via software
(irqbalance) or BIOS APIC programming
On Wed, Jan 30, 2019 at 08:51:42PM -0500, Qian Cai wrote:
>
>
> On 1/30/19 7:05 PM, Stephen Rothwell wrote:
> > In commit
> >
> > 6e9ed490d190 ("mm/page_owner: fix for deferred struct page init")
> >
> > Fixes tag
> >
> > Fixes: fe53ca54270 ("mm: use early_pfn_to_nid in page_ext_init")
>
On 31/01/19 04:26, Yu Zhang wrote:
> Previously, 'commit f99e3daf94ff ("KVM: x86: Add Intel PT
> virtualization work mode")' work mode' offered framework
> to support Intel PT virtualization. However, the patch has
> some typos in vmx_vmentry_ctrl() and vmx_vmexit_ctrl(), e.g.
> used wrong flags
On Thu, Jan 31, 2019 at 12:57 PM Christopher Lameter wrote:
>
> On Thu, 31 Jan 2019, Thomas Garnier wrote:
>
> > Perpcu uses a clever design where the .percu ELF section has a virtual
> > address of zero and the custom linux relocation code avoid relocating
> > specific symbols. It makes the code
On 2019-01-31 1:58 p.m., Dave Jiang wrote:
>
> On 1/31/2019 1:48 PM, Logan Gunthorpe wrote:
>>
>> On 2019-01-31 1:20 p.m., Dave Jiang wrote:
>>> Does this work when the system moves the MSI vector either via software
>>> (irqbalance) or BIOS APIC programming (some modes cause round robin
>>>
[+cc Thomas, Marc]
On Thu, Jan 31, 2019 at 11:56:49AM -0700, Logan Gunthorpe wrote:
> For NTB devices, we want to be able to trigger MSI interrupts
> through a memory window. In these cases we may want to use
> more interrupts than the NTB PCI device has available in its MSI-X
> table.
>
> We
On Thu, Jan 31, 2019 at 11:57:32AM +0100, Borislav Petkov wrote:
> On Thu, Jan 31, 2019 at 03:59:07PM +0800, Dave Young wrote:
> > As Pingfan/me mentioned in another reply, there are two reasons:
> > 1. old kexec-tools can not load kernel to high memory
> > 2. ,high will not work on some systems
On Thu, Jan 31, 2019 at 10:35:54AM -0800, Bo Yan wrote:
> The xavier CPU architecture includes 8 CPU cores organized in
> 4 clusters. Add cpu-map data for topology initialization, add
> cache data for cache node creation in sysfs.
>
> Signed-off-by: Bo Yan
> ---
>
> On Jan 31, 2019, at 3:29 AM, Borislav Petkov wrote:
>
>> Subject: Re: [PATCH v2 03/20] x86/mm: temporary mm struct
>
> Subject needs a verb: "Add a temporary... "
>
> On Mon, Jan 28, 2019 at 04:34:05PM -0800, Rick Edgecombe wrote:
>> From: Andy Lutomirski
>>
>> Sometimes we want to set a
On Thu, Jan 31, 2019 at 06:57:10PM +, Roman Gushchin wrote:
> On Thu, Jan 31, 2019 at 10:10:11AM +0100, Michal Hocko wrote:
> > On Thu 31-01-19 12:34:03, Dave Chinner wrote:
> > > On Wed, Jan 30, 2019 at 12:21:07PM +, Chris Mason wrote:
> > > >
> > > >
> > > > On 29 Jan 2019, at 23:17,
On Tue, 29 Jan 2019 21:02:16 -0800 Dan Williams
wrote:
> Randomization of the page allocator improves the average utilization of
> a direct-mapped memory-side-cache. Memory side caching is a platform
> capability that Linux has been previously exposed to in HPC
> (high-performance computing)
On Tue, 29 Jan 2019 21:02:26 -0800 Dan Williams
wrote:
> When freeing a page with an order >= shuffle_page_order randomly select
> the front or back of the list for insertion.
>
> While the mm tries to defragment physical pages into huge pages this can
> tend to make the page allocator more
If the backing device for a loop device is a block device,
then mirror the discard properties of the underlying block
device into the loop device. While in there, differentiate
between REQ_OP_DISCARD and REQ_OP_WRITE_ZEROES, which are
different for block devices, but which the loop device had
just
Properly plumb out EOPNOTSUPP from loop driver operations, which may
get returned when for instance a discard operation is attempted but not
supported by the underlying block device. Before this change, everything
was reported in the log as an I/O error, which is scary and not
helpful in
This series addresses some errors seen when using the loop
device directly backed by a block device. The first change plumbs
out the correct error message, and the second change prevents the
error from occurring in many cases.
The errors look like this:
[ 90.880875] print_req_error: I/O error,
Add HCI_QUIRK_USE_BDADDR_PROPERTY to allow controllers to retrieve
the public Bluetooth address from the firmware node property
'local-bd-address'. If quirk is set and the property does not exist
or is invalid the controller is marked as unconfigured.
Signed-off-by: Matthias Kaehlcke
Set quirk for wcn3990 to read BD_ADDR from a firmware node property.
Signed-off-by: Matthias Kaehlcke
Tested-by: Balakrishna Godavarthi
---
Changes in v3:
- none
Changes in v2:
- patch added to the series
---
drivers/bluetooth/hci_qca.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Use the HCI_QUIRK_USE_BDADDR_PROPERTY quirk to let the HCI
core handle the reading of 'local-bd-address'. With this there
is no need to set HCI_QUIRK_INVALID_BDADDR, the case of a
non-existing or invalid fwnode property is handled by the core
code.
Signed-off-by: Matthias Kaehlcke
Reviewed-by:
[initial post: https://lore.kernel.org/patchwork/cover/1028184/]
On some systems the Bluetooth Device Address (BD_ADDR) isn't stored
on the Bluetooth chip itself. One way to configure the address is
through the device tree (patched in by the bootloader). The btqcomsmd
driver is an example, it can
On 1/31/19 5:49 AM, David Sterba wrote:
> On Wed, Jan 30, 2019 at 08:30:16PM -0600, Gustavo A. R. Silva wrote:
>> Fix inconsistent IS_ERR and PTR_ERR in btrfs_qgroup_trace_subtree_after_cow
>>
>> The proper pointer to be passed as argument is reloc_eb.
>>
>> This bug was detected with the help
Hi Jan,
On Thu, 31 Jan 2019 11:11:22 +0100 Jan Kara wrote:
>
> Yeah, I've fixed that already in my tree. Thanks for letting me know and
> sorry for the breakage.
Thanks.
--
Cheers,
Stephen Rothwell
pgpt2NonR7HoC.pgp
Description: OpenPGP digital signature
It has been supported as a generic lm85 for quite some time.
Signed-off-by: Jeremy Gebben
---
Documentation/hwmon/lm85 | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/Documentation/hwmon/lm85 b/Documentation/hwmon/lm85
index 7c49feaa7..9f3a945d1 100644
---
Hi,
This patch adds support for the PWM frequencies from 22.5 to 30 kHz
available on the LM96000.
It looks like this chip has been supported for a long time, but wasn't
mentioned in the docs (which I have updated).
Also, it has been using the generic 'lm85' prefix, which I have not
changed to
Allow support for chips that support more than 8 frequencies.
Signed-off-by: Jeremy Gebben
---
drivers/hwmon/lm85.c | 25 +++--
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git a/drivers/hwmon/lm85.c b/drivers/hwmon/lm85.c
index 0a325878e..4b15193d1 100644
---
This chip expands the freqency field from 3 to 4 bits, to
add more frequencies in the 22.5 to 30 kHz ranges.
Signed-off-by: Jeremy Gebben
---
Documentation/hwmon/lm85 | 3 +++
drivers/hwmon/lm85.c | 9 +
2 files changed, 12 insertions(+)
diff --git a/Documentation/hwmon/lm85
PCI fixes:
- Revert armada8k GPIO reset change that broke Macchiatobin booting
(Baruch Siach)
- Use actual size config reads on ARM cns3xxx (Koen Vandeputte)
- Fix ARM cns3xxx config write alignment issue (Koen Vandeputte)
- Fix imx6 PHY device link error checking (Leonard Crestez)
On Thu, Jan 31, 2019 at 12:47 PM Jarkko Sakkinen
wrote:
>
> I'll try it first thing when I wake up tomorrow (11PM in Finland ATM).
Thanks.
> Appreciate for taking time on this.
Hey, it was my commit that broke it for you. Even if it happened to
work before, and only did so by pure luck, it was
On Thu, Jan 31, 2019 at 10:03:12PM +0100, Sam Ravnborg wrote:
> Hi Sean.
>
> > Hey Sam,
> > Thanks for the patchset, this will make dmesg grepping easier! One comment,
> > and
> > you're going to hate me for it: Why use DRM_DEV* instead of DRM_*?
> >
> > When I introduced DRM_DEV, it was to
Quoting Stephen Boyd (2019-01-23 12:52:09)
> Quoting Stephen Boyd (2019-01-11 15:20:48)
> > Quoting Rob Herring (2019-01-09 11:36:56)
> > >
> > > > >However, my main concern is documenting something genericish in a
> > > > >device specific binding. It looks like Tegra is trying to add the same
>
Hi,
On 01/31/2019 11:54 AM, Andre Przywara wrote:
On Fri, 25 Jan 2019 12:07:06 -0600
Jeremy Linton wrote:
Hi,
Display the mitigation status if active, otherwise
assume the cpu is safe unless it doesn't have CSV3
and isn't in our whitelist.
Signed-off-by: Jeremy Linton
---
[+cc linux-pci, linux-kernel]
On Thu, Jan 31, 2019 at 11:21 AM Lukas F. Hartmann wrote:
>
> Hi Thinh,
>
> I'm writing you because you're the author in this commit:
> https://github.com/torvalds/linux/commit/03e6742584af8866ba014874669d0440bed3a623
>
> This quirk workaround breaks the PCIe on
> On Jan 31, 2019, at 9:24 AM, Uladzislau Rezki (Sony) wrote:
>
> vmap_lazy_nr variable has atomic_t type that is 4 bytes integer
> value on both 32 and 64 bit systems. lazy_max_pages() deals with
> "unsigned long" that is 8 bytes on 64 bit system, thus vmap_lazy_nr
> should be 8 bytes on 64
On Thu, 31 Jan 2019, Oleksandr Andrushchenko wrote:
> Hello,
>
> I am working on porting an out-of-tree kernel driver to the kernel
> 5.0 and that driver uses functionality provided by
> drivers/xen/mem-reservation.c
> module. Since commit [1] it is not possible to build a kernel module
> which
> It works with this change:
>
> diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
> index fe5b89abc576..8e059e94b94e 100644
> --- a/drivers/i2c/busses/i2c-tegra.c
> +++ b/drivers/i2c/busses/i2c-tegra.c
> @@ -1170,10 +1170,11 @@ static int tegra_i2c_xfer_msg(struct
From: Alex Williams
Under certain conditions, Cadence's I2C controller's transfer_size
register will roll over and generate invalid read transactions. Before
this change, the ISR relied solely on the RXDV bit to determine when to
write more data to the user's buffer. The invalid read data would
Hi,
On 01/31/2019 03:28 AM, Julien Thierry wrote:
Hi Jeremy,
On 25/01/2019 18:07, Jeremy Linton wrote:
Display the mitigation status if active, otherwise
assume the cpu is safe unless it doesn't have CSV3
and isn't in our whitelist.
Signed-off-by: Jeremy Linton
---
Hi Andrey
On Thu, Jan 31, 2019 at 7:11 PM Andrey Smirnov wrote:
>
> Now that the GPCv2 driver supports i.MX8MQ, make GPC default interrupt
> parent.
>
> Signed-off-by: Andrey Smirnov
Lucas has already submitted this same change and another one that
selects the GPC driver as part of a series.
Use kvzalloc() instead of kvmalloc() and memset().
Also, make use of the struct_size() helper instead of
the open-coded version in order to avoid any potential
type mistakes.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
ipc/sem.c | 6 +-
1
Hi Stefan,
Thank you for the patch.
On 1/31/19 9:23 AM, Stefan Mavrodiev wrote:
Most of AXP20x PMIC chips have built-in battery charger with LED indicator.
The LED can be controlled ether by the charger or manually by a register.
The default is (except for AXP209) manual control, which makes
201 - 300 of 1208 matches
Mail list logo
