On Fri, Jan 22, 2021 at 5:57 PM Alexandru Ardelean
wrote:
>
> The scan_elements attributes are solely located inside
> 'industrialio-buffer-sysfs.c'. In order to support more than one buffer per
> IIO device, we need to expand scan_elements attributes directly to IIO
> buffer object, and not the I
Move the complicated condition and the calculations out of
filemap_update_page() into its own function.
Signed-off-by: Matthew Wilcox (Oracle)
Reviewed-by: Kent Overstreet
Reviewed-by: Christoph Hellwig
---
mm/filemap.c | 68 ++--
1 file changed,
Remove the got_pages label, remove indentation, rename find_page to retry,
simplify error handling.
Signed-off-by: Matthew Wilcox (Oracle)
Reviewed-by: Kent Overstreet
Reviewed-by: Christoph Hellwig
---
mm/filemap.c | 71 +---
1 file changed, 28
On Thu, Jan 21, 2021 at 12:45 AM Dmitry Osipenko wrote:
>
> Hi,
>
> This series is a prerequisite for the power domain driver of NVIDIA Tegra
> SoCs [1]. It extends the GENPD core with a better support of performance
> states and eases linking of child/parent PDs for the PD drivers.
>
> [1] https:
From: Christoph Hellwig
Avoid the pointless goto out just for returning retval.
Signed-off-by: Christoph Hellwig
Signed-off-by: Matthew Wilcox (Oracle)
Reviewed-by: Kent Overstreet
---
mm/filemap.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/mm/filemap.c b/
On Tue, Jan 12, 2021 at 2:57 AM Xin Ji wrote:
>
> Hi Rob Herring, thanks for the comments.
>
> On Mon, Jan 11, 2021 at 04:14:35PM -0600, Rob Herring wrote:
> > On Thu, Dec 31, 2020 at 10:21:12AM +0800, Xin Ji wrote:
> > > Add DPI flag for distinguish MIPI input signal type, DSI or DPI. Add
> > > s
On 22/01/2021 at 16:25, Arnd Bergmann wrote:
On Fri, Jan 22, 2021 at 3:35 PM wrote:
From: Nicolas Ferre
Arnd, Olof,
I'm taking back the lead on sending the pull-requests for AT91 and hope that I
didn't loose the knowledge in the meantime. Tell me if there's something I'm
missing. Thanks a l
From: Christoph Hellwig
Rename generic_file_buffered_read to match the naming of filemap_fault,
also update the written parameter to a more descriptive name and
improve the kerneldoc comment.
Signed-off-by: Christoph Hellwig
Signed-off-by: Matthew Wilcox (Oracle)
Reviewed-by: Kent Overstreet
On Fri, 2021-01-22 at 11:13 -0300, Marcelo Tosatti wrote:
> On Thu, Oct 01, 2020 at 04:47:31PM +0200, Frederic Weisbecker wrote:
> > On Wed, Jul 22, 2020 at 02:58:24PM +, Alex Belits wrote:
> > > From: Yuri Norov
> > >
> > > so we don't need to flush it.
> >
> > What guarantees that we have
On arm64, enable dwarf_callchain_users which will be needed
to do a dwarf unwind in order to get the caller of the leaf frame.
Signed-off-by: Alexandre Truong
Cc: John Garry
Cc: Will Deacon
Cc: Mathieu Poirier
Cc: Leo Yan
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Arnaldo Carvalho de Melo
Cc:
On Fri 2021-01-22 16:13:11, kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: b031a684bfd01d633c79d281bd0cf11c2f834ada ("printk: remove logbuf_lock
> writer-protection of ringbuffer")
> https://git.kernel.org/cgit/linux/kernel/git/to
Continuing from:
https://lore.kernel.org/linux-iio/20201117162340.43924-1-alexandru.ardel...@analog.com/
Changelog v1 -> v2:
* 'iio: buffer: rework buffer & scan_elements dir creation'
add more doc-strings detailing the reasoning for this change
* 'iio: buffer: re-route scan_elements via it's
We only need a chardev if we need to support buffers and/or events.
With this change, a chardev will be created only if an IIO buffer is
attached OR an event_interface is configured.
Otherwise, no chardev will be created, and the IIO device will get
registered with the 'device_add()' call.
Quite
The __iio_device_attr_init() function initializes a device_attribute
object, but mostly it just does a lot of name creation logic.
We will want to re-use this logic for name-creation, so this change
re-purposes the __iio_device_attr_init() to be a __iio_attr_init() function
which just handles the
This change makes it so that the first buffer directory is named 'buffer0'
and moves the 'scan_elements' under it.
For backwards compatibility these folders are symlinked back to the
original folders.
Signed-off-by: Alexandru Ardelean
---
drivers/iio/industrialio-buffer.c | 66 +
When adding more than one IIO buffer per IIO device, we will need to create
a buffer & scan_elements directory for each buffer.
We also want to move the 'scan_elements' to be a sub-directory of the
'buffer' folder.
The format we want to reach is, for a iio:device0 folder, for 2 buffers
[for exampl
The scan_elements attributes are solely located inside
'industrialio-buffer-sysfs.c'. In order to support more than one buffer per
IIO device, we need to expand scan_elements attributes directly to IIO
buffer object, and not the IIO device.
This also requires that a new 'iio_buffer_attr' type be a
On Fri, Jan 22, 2021 at 09:12:54PM +0530, Calvin Johnson wrote:
> Using fwnode_get_id(), get the reg property value for DT node
> or get the _ADR object value for ACPI node.
...
> +/**
> + * fwnode_get_id - Get the id of a fwnode.
> + * @fwnode: firmware node
> + * @id: id of the fwnode
> + *
> +
With this change, an ioctl() call is added to open a character device for a
buffer.
The ioctl() will return a 0 FD for the first buffer, as that FD for buffer0
is the same FD as the one used for this ioctl().
For any other extra buffer, this ioctl() will return an anon inode FD that
would access a
From: Xuan Zhuo
Date: Fri, 22 Jan 2021 23:36:29 +0800
> On Fri, 22 Jan 2021 12:08:00 +, Alexander Lobakin wrote:
> > From: Alexander Lobakin
> > Date: Fri, 22 Jan 2021 11:55:35 +
> >
> > > From: Alexander Lobakin
> > > Date: Fri, 22 Jan 2021 11:47:45 +
> > >
> > > > From: Eric Duma
HS200 and HS400 modes at 1.8 V card voltage, are now supported in MMCSD0
subsystem of J7200 SoC[1].
Set respective tags to indicate it.
[1] - https://www.ti.com/lit/ug/spruiu1a/spruiu1a.pdf
Signed-off-by: Aswath Govindraju
---
arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 2 ++
1 file changed, 2
On Thu, Jan 21, 2021 at 08:01:37PM -0800, Wesley Cheng wrote:
> Some UDCs may have constraints on how many high bandwidth endpoints it can
> support in a certain configuration. This API allows for the composite
> driver to pass down the total number of endpoints to the UDC so it can verify
> it ha
On Fri, Jan 22, 2021 at 07:55:35AM -0800, Wesley Zhao wrote:
> I was trying to reserve some memory to save logs incase that Android panic or
> hang and then
> I can read the logs from QNX side from the memory reserved before on the
> Qualcomm 8155 hypervisor platform,
> and I find the "reserve="
On Fri, Jan 22, 2021 at 07:55:36AM -0800, Wesley Zhao wrote:
> In the future we would pass the unsigned long long parameter
> like(0x123456781234) in cmdline on the 64bit platform, so add a new
> option parse function get_option_ull()
You missed period at the end of phrase.
Overall this patch is
On Fri, Jan 22, 2021 at 07:55:37AM -0800, Wesley Zhao wrote:
> For now "reserve=" is limitied to 32bit,not available on 64bit
> platform,so we change the get_option() to get_option_ull(added in
> patch: commit 4b6bfe96265e ("lib/cmdline: add new function
> get_option_ull()"))
Do better grammar and
An IIO device will have multiple buffers, but it shouldn't be allowed that
an IIO buffer should belong to more than 1 IIO device.
Once things get moved more from IIO device to the IIO buffer, and an IIO
device will be able to have more than 1 buffer attached, there will be a
need for a back-ref to
Remove no-1-8-v tag in sdhci1 device tree node as UHS-I speed modes are now
supported in MMCSD1 subsystem of J7200 SoC[1].
[1] - https://www.ti.com/lit/ug/spruiu1a/spruiu1a.pdf
Signed-off-by: Aswath Govindraju
---
arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 1 -
1 file changed, 1 deletion(-)
d
On Wed, Jan 20, 2021 at 02:43:49PM +0100, Robert Foss wrote:
> Add bindings for qcom,msm8996-camss in order to support the camera
> subsystem on MSM8996.
>
> Signed-off-by: Robert Foss
> ---
>
> Changes since v1:
> - Laurent: Reworked driver to use dtschema
>
>
> .../bindings/media/qcom,msm8
On Wed, Jan 20, 2021 at 9:01 PM Saravana Kannan wrote:
>
> On Wed, Jan 20, 2021 at 11:15 AM Rafael J. Wysocki wrote:
> >
> > On Wed, Jan 20, 2021 at 7:51 PM Andy Shevchenko
> > wrote:
> > >
> > > On Wed, Jan 20, 2021 at 8:18 PM Rafael J. Wysocki
> > > wrote:
> > > > On Tue, Jan 12, 2021 at 7:0
On Wed, Jan 20, 2021 at 02:43:50PM +0100, Robert Foss wrote:
> Add bindings for qcom,sdm660-camss in order to support the camera
> subsystem on SDM630/660 and SDA variants.
>
> Signed-off-by: Robert Foss
> ---
>
> Changes since v1:
> - Laurent: Reworked driver to use dtschema
Same comments on
Move all the jack-detect variables from struct arizona_extcon_info to
struct arizona_priv.
This is part of a patch series converting the arizona extcon driver into
a helper library for letting the arizona codec-drivers directly report jack
state through the standard sound/soc/soc-jack.c functions.
Add jack detect support by creating a jack and calling
snd_soc_component_set_jack to register the created jack
with the codec.
Reviewed-by: Andy Shevchenko
Signed-off-by: Hans de Goede
---
sound/soc/intel/boards/bytcr_wm5102.c | 28 ++-
1 file changed, 27 insertions(+),
Cleanup the use of dev_foo functions used for logging:
1. Many of these are unnecessarily split over multiple lines
2. Use dev_err_probe() in cases where we might get a -EPROBE_DEFERRED
return value
Suggested-by: Andy Shevchenko
Signed-off-by: Hans de Goede
---
Changes in v3:
- This is a new
Drivers for MFD child-devices such as the arizona codec drivers
and the arizona-extcon driver can choose to either make
runtime_pm_get/_put calls on their own child-device, which will
then be propagated to their parent; or they can make them directly
on their MFD parent-device.
The arizona-extcon
Make all arizona codec drivers for which drivers/mfd/arizona-core.c used
to instantiate a "arizona-extcon" child-device use the new arizona-jack.c
library for jack-detection.
This has been tested on a Lenovo Yoga Tablet 2 1051L with a WM5102 codec.
Signed-off-by: Hans de Goede
---
sound/soc/cod
Convert the arizona extcon driver into a helper library for direct use
from the arizona codec-drivers, rather then being bound to a separate
MFD cell.
Note the probe (and remove) sequence is split into 2 parts:
1. The arizona_jack_codec_dev_probe() function inits a bunch of
jack-detect specific v
Before this commit the extcon-arizona code was mixing pm_runtime_get()
and pm_runtime_get_sync() in different places.
In all places where pm_runtime_get[_sync]() is called, the code
makes use of the device immediately after the call.
This means that we should always use pm_runtime_get_sync().
Sig
Hi all,
Here is v3 om my series to rework the arizona codec jack-detect support
to use the snd_soc_jack helpers instead of direct extcon reporting.
This is done by reworking the extcon driver into an arizona-jackdet
library and then modifying the codec drivers to use that directly,
replacing the
The jack handling for arizona codecs is being refactored so that it is
done directly by the codec drivers, instead of having an extcon-driver
bind to a separate "arizona-extcon" child-device for this.
drivers/mfd/arizona-core.c has already been updated to no longer
instantiate an "arizona-extcon"
When the jack is partially inserted and then removed again it may be
removed while the hpdet code is running. In this case the following
may happen:
1. The "JACKDET rise" or ""JACKDET fall" IRQ triggers
2. arizona_jackdet runs and takes info->lock
3. The "HPDET" IRQ triggers
4. arizona_hpdet_irq r
We must free/disable all interrupts and cancel all pending works
before doing further cleanup.
Before this commit arizona_extcon_remove() was doing several
register writes to shut things down before disabling the IRQs
and it was cancelling only 1 of the 3 different works used.
Move all the regist
The initial value of the GPIO should match the info->micd_modes[0].gpio
value. arizona_extcon_probe() already stores the necessary flag in a
mode variable, but instead of passing mode as flags to the gpiod_get()
it was using a hardcoded GPIOD_OUT_LOW.
Reviewed-by: Andy Shevchenko
Acked-by: Charle
No, what I was saying is that you need to define multiple streams e.g.
- headset capture (configured with or without click suppression)
- mic capture (configured with AMICs or DMICs)
- playback (or possibly different endpoint specific streams depending
on whether concurrency between endpoint i
On Fri, Jan 22, 2021 at 4:46 PM Calvin Johnson
wrote:
>
> Using fwnode_get_id(), get the reg property value for DT node
> or get the _ADR object value for ACPI node.
So I'm not really sure if this is going to be generically useful.
First of all, the meaning of the _ADR return value is specific t
On Fri, 22 Jan 2021 17:23:36 +0100 "Rafael J. Wysocki"
wrote:
> On Thu, Jan 14, 2021 at 7:35 PM Rafael J. Wysocki wrote:
>>
>> From: Rafael J. Wysocki
>>
>> Calling acpi_thermal_check() from acpi_thermal_notify() directly
>> is problematic if _TMP triggers Notify () on the thermal zone for
>>
On Thu, Jan 21, 2021 at 10:47:46PM +0530, Vinod Koul wrote:
> Add device tree binding Documentation details for Qualcomm SM8350
> pinctrl driver.
>
> Signed-off-by: Vinod Koul
> ---
> .../bindings/pinctrl/qcom,sm8350-pinctrl.yaml | 146 ++
> 1 file changed, 146 insertions(+)
> c
On Thu, Jan 21, 2021 at 11:09:50AM +0800, peng@nxp.com wrote:
> From: Peng Fan
>
> Add pinctrl bindings for fsl-imx-esdhc yaml
>
> Signed-off-by: Peng Fan
> ---
> .../bindings/mmc/fsl-imx-esdhc.yaml | 25 +++
> 1 file changed, 25 insertions(+)
>
> diff --git a/Do
On Mon, Jan 4, 2021 at 10:58 AM Rob Herring wrote:
>
> Convert video-interfaces.txt to DT schema. As it contains a mixture of
> device level and endpoint properties, split it up into 2 schemas.
Ping!
Can this please be applied to the media tree so I can tell folks to
use it in reviews of media b
The following series of patches
- adds support for HS200 and HS400 speed modes in MMCSD0 subsystem
- adds support for UHS-I speed modes in MMCSD1 subsystem
Aswath Govindraju (2):
arm64: dts: ti: k3-j7200-main: Add support for HS200 and HS400 modes
in MMCSD0 subsystem
arm64: dts: ti: k3-j7
On Thu, Jan 14, 2021 at 7:35 PM Rafael J. Wysocki wrote:
>
> From: Rafael J. Wysocki
>
> Calling acpi_thermal_check() from acpi_thermal_notify() directly
> is problematic if _TMP triggers Notify () on the thermal zone for
> which it has been evaluated (which happens on some systems), because
> it
In order to keep backwards compatibility with the current chardev
mechanism, and in order to add support for multiple buffers per IIO device,
we need to pass both the IIO device & IIO buffer to the chardev.
This is particularly needed for the iio_buffer_read_outer() function, where
we need to pass
This is useful for drivers that may have a reference to an IIO buffer, to
be able to get a reference back to the IIO device.
Signed-off-by: Alexandru Ardelean
---
drivers/iio/industrialio-buffer.c | 14 ++
include/linux/iio/buffer.h| 2 ++
2 files changed, 16 insertions(+)
For the buffer attributes that are present inside the IIO core buffer logic
we can re-route them to expand the attribute into iio_buffer objects.
The rest, will still expand to device_attributes.
Signed-off-by: Alexandru Ardelean
---
drivers/iio/industrialio-buffer.c | 113 +
With this change, calling iio_device_attach_buffer() will actually attach
more buffers.
Right now this doesn't do any validation of whether a buffer is attached
twice; maybe that can be added later (if needed). Attaching a buffer more
than once should yield noticeably bad results.
The first buffer
On arm64 and frame pointer mode (e.g: perf record --callgraph fp),
use dwarf unwind info to check if the link register is the return
address in order to inject it to the frame pointer stack.
Write the following application:
int a = 10;
void f2(void)
{
for
Now that the iio_buffer_set_attrs() has been removed, we can be sure that
no accidents can happen with drivers that try to provide extra buffer
attributes that expand to iio_dev objects.
So, we can convert all remaining buffer attributes to expand to iio_buffer
objects.
These will look a bit weird
On arm64, automatically record all the registers if the frame pointer
mode is on. They will be used to do a dwarf unwind to find the caller
of the leaf frame if the frame pointer was omitted.
Signed-off-by: Alexandre Truong
Cc: John Garry
Cc: Will Deacon
Cc: Mathieu Poirier
Cc: Leo Yan
Cc: Pe
Add a mechanism for platforms to inject stack frames for the leaf
frame caller if there is enough information to determine a frame
is missing from dwarf or other post processing mechanisms.
Signed-off-by: Alexandre Truong
Cc: John Garry
Cc: Will Deacon
Cc: Mathieu Poirier
Cc: Leo Yan
Cc: Pete
Hi Alistair,
thanks for the patches. Before getting into the series please check all
your commit subjects. Also please check that you do only one logical
change per patch: e.g. adding DT-Support means: Add the dt-table and not
more.
I looking forward to your v2 :)
Regards,
Marco
On 21-01-20 2
On Fri, 22 Jan 2021 at 17:53, Peter Zijlstra wrote:
>
> On Mon, Jan 18, 2021 at 03:12:21PM +0100, Frederic Weisbecker wrote:
> > +#ifdef CONFIG_PREEMPT_DYNAMIC
> > +DEFINE_STATIC_CALL(preempt_schedule, __preempt_schedule_func());
> > +EXPORT_STATIC_CALL(preempt_schedule);
> > +#endif
>
> > +#ifdef
We don't need to get the page lock again; we just need to wait for
the I/O to finish, so use wait_on_page_locked_killable() like the
other callers of ->readpage.
Signed-off-by: Matthew Wilcox (Oracle)
Reviewed-by: Kent Overstreet
Reviewed-by: Christoph Hellwig
---
mm/filemap.c | 21 +++
A netdev xmit function should return NETDEV_TX_OK or NETDEV_TX_BUSY.
Signed-off-by: Martin Kaiser
---
drivers/staging/rtl8188eu/os_dep/xmit_linux.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8188eu/os_dep/xmit_linux.c
b/drivers/staging/rtl8188eu/os_de
On Tue, Jan 19, 2021 at 06:44:18PM +0100, AngeloGioacchino Del Regno wrote:
> Document properties to configure soft start and discharge resistor
> for LAB and IBB respectively.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> Reviewed-by: Bjorn Andersson
> ---
> .../bindings/regulator/qcom-la
On Thu, Jan 21, 2021 at 8:54 AM wrote:
>
> From 72f3ecde58edb03d76cb359607fef98c1663d481 Mon Sep 17 00:00:00 2001
> From: Yang Yang
> Date: Thu, 21 Jan 2021 21:05:04 +0800
> Subject: [PATCH] [RFC,v2,1/1] speed up syscall rule match while exiting
> syscall
> audit_filter_syscall() traverses stru
On 21-01-22 11:43:57, Jonathan Cameron wrote:
> On Thu, 21 Jan 2021 10:15:46 -0800
> Ben Widawsky wrote:
>
> > On 21-01-14 17:10:38, Jonathan Cameron wrote:
> > > On Mon, 11 Jan 2021 14:51:14 -0800
> > > Ben Widawsky wrote:
> > >
> > > > The send command allows userspace to issue mailbox comm
On Fri, Jan 22, 2021 at 03:12:45PM +0100, Greg Kroah-Hartman wrote:
> From: Daniel Borkmann
>
> [ no upstream commit ]
>
> Fix a potential kernel address leakage for the prerequisite where there is
> a BPF program attached to the cgroup/setsockopt hook. The latter can only
> be attached under ro
On Tue, Jan 19, 2021 at 06:44:20PM +0100, AngeloGioacchino Del Regno wrote:
> Short-Circuit Protection (SCP) and Over-Current Protection (OCP) are
> now implemented in the driver: document the interrupts.
> This also fixes wrong documentation about the SCP interrupt for LAB.
>
> Signed-off-by: Ang
On Fri, Jan 22, 2021 at 05:57:53PM +0100, Ard Biesheuvel wrote:
> On Fri, 22 Jan 2021 at 17:53, Peter Zijlstra wrote:
> >
> > On Mon, Jan 18, 2021 at 03:12:21PM +0100, Frederic Weisbecker wrote:
> > > +#ifdef CONFIG_PREEMPT_DYNAMIC
> > > +DEFINE_STATIC_CALL(preempt_schedule, __preempt_schedule_fun
Define acpi_mdiobus_register() to Register mii_bus and create PHYs for
each ACPI child node.
Signed-off-by: Calvin Johnson
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
MAINTAINERS | 1 +
drivers/net/mdio/Kconfig | 7 ++
drivers/net/mdio/Makefile
On Fri, Jan 22, 2021 at 4:57 PM Vincenzo Frascino
wrote:
>
> With the introduction of KASAN_HW_TAGS, kasan_report() accesses the
> metadata only when addr_has_metadata() succeeds.
>
> Add a comment to make sure that the preconditions to the function are
> explicitly clarified.
>
> Cc: Andrey Ryabi
The arizona jack-dection handling is being reworked so that the
codec-child-device drivers directly handle jack-detect themselves,
so it is no longer necessary to instantiate "arizona-extcon"
child-devices.
Signed-off-by: Hans de Goede
---
drivers/mfd/arizona-core.c | 20
1
Use the snd_soc_jack code to report jack events, instead of using extcon
for reporting the cable-type + an input_dev for reporting the button
presses.
The snd_soc_jack code will report the cable-type through both input_dev
events and through ALSA controls and the button-presses through input_dev
e
On Fri, Jan 22, 2021 at 5:39 PM Stephen Berman wrote:
>
> On Fri, 22 Jan 2021 17:23:36 +0100 "Rafael J. Wysocki"
> wrote:
>
> > On Thu, Jan 14, 2021 at 7:35 PM Rafael J. Wysocki
> > wrote:
> >>
> >> From: Rafael J. Wysocki
> >>
> >> Calling acpi_thermal_check() from acpi_thermal_notify() dire
On Wed, 20 Jan 2021 16:07:29 +0100, Arnd Bergmann wrote:
> The tango platform is getting removed, so the driver is no
> longer needed.
Applied to pci/tango, thanks!
[1/1] PCI: Remove tango host controller driver
https://git.kernel.org/lpieralisi/pci/c/de9427ca87
Thanks,
Lorenzo
On 2021-01-22 17:23:36 [+0100], Rafael J. Wysocki wrote:
>
> Well, it's been over a week since this was posted.
Thank you for this ;)
> Does anyone have any comments?
I looked over it and it makes sense, so
Reviewed-by: Sebastian Andrzej Siewior
I didn't comment on it since a testing-by wou
On Fri, Jan 22, 2021 at 05:40:41PM +0100, Rafael J. Wysocki wrote:
> On Fri, Jan 22, 2021 at 4:46 PM Calvin Johnson
> wrote:
> >
> > Using fwnode_get_id(), get the reg property value for DT node
> > or get the _ADR object value for ACPI node.
>
> So I'm not really sure if this is going to be gene
Hi Rob,
On Fri, Jan 22, 2021 at 10:23:44AM -0600, Rob Herring wrote:
> On Mon, Jan 4, 2021 at 10:58 AM Rob Herring wrote:
> >
> > Convert video-interfaces.txt to DT schema. As it contains a mixture of
> > device level and endpoint properties, split it up into 2 schemas.
>
> Ping!
>
> Can this p
On Mon, Jan 18, 2021 at 03:12:21PM +0100, Frederic Weisbecker wrote:
> +#ifdef CONFIG_PREEMPT_DYNAMIC
> +DEFINE_STATIC_CALL(preempt_schedule, __preempt_schedule_func());
> +EXPORT_STATIC_CALL(preempt_schedule);
> +#endif
> +#ifdef CONFIG_PREEMPT_DYNAMIC
> +DEFINE_STATIC_CALL(preempt_schedule_notra
Hi Linus,
The following changes since commit 9791581c049c10929e97098374dd1716a81fefcc:
Merge tag 'for-5.11-rc4-tag' of
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux (2021-01-20 14:15:33
-0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/
On 2021-01-21 6:18 p.m., Joe Perches wrote:
> On Fri, 2021-01-22 at 05:25 +0900, Masahiro Yamada wrote:
>> On Fri, Jan 22, 2021 at 2:17 AM Scott Branden
>> wrote:
>>> Use python3 instead of python in diffconfig Shebang line.
>>> python2 was sunset January 1, 2000 and environments do not need
>>
On 22/01/2021 16:25:47+0100, Arnd Bergmann wrote:
> On Fri, Jan 22, 2021 at 3:35 PM wrote:
> >
> > From: Nicolas Ferre
> >
> > Arnd, Olof,
> >
> > I'm taking back the lead on sending the pull-requests for AT91 and hope
> > that I
> > didn't loose the knowledge in the meantime. Tell me if there's
This simplifies the error handling.
Signed-off-by: Matthew Wilcox (Oracle)
Reviewed-by: Kent Overstreet
Reviewed-by: Christoph Hellwig
---
mm/filemap.c | 19 ++-
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/mm/filemap.c b/mm/filemap.c
index a3ebc6082022e..ba20
Make this function more generic by passing the file instead of the iocb.
Check in the callers whether we should call readpage or not. Also make
it return an errno / 0 / AOP_TRUNCATED_PAGE, and make calling put_page()
the caller's responsibility.
Signed-off-by: Matthew Wilcox (Oracle)
Reviewed-by
With the introduction of KASAN_HW_TAGS, kasan_report() accesses the
metadata only when addr_has_metadata() succeeds.
Add a comment to make sure that the preconditions to the function are
explicitly clarified.
Cc: Andrey Ryabinin
Cc: Alexander Potapenko
Cc: Dmitry Vyukov
Cc: Leon Romanovsky
Cc
Currently, the __is_lm_address() check just masks out the top 12 bits
of the address, but if they are 0, it still yields a true result.
This has as a side effect that virt_addr_valid() returns true even for
invalid virtual addresses (e.g. 0x0).
Improve the detection checking that it's actually a k
Using a pagevec lets us keep the pages and the number of pages together
which simplifies a lot of the calling conventions.
Signed-off-by: Matthew Wilcox (Oracle)
Reviewed-by: Christoph Hellwig
---
mm/filemap.c | 82
1 file changed, 38 inserti
On Fri, Jan 22, 2021 at 11:09:09AM +, Qais Yousef wrote:
> I was hitting the below panic continuously when attaching kprobes to
> scheduler functions
[...]
> diff --git a/arch/arm64/kernel/probes/kprobes.c
> b/arch/arm64/kernel/probes/kprobes.c
> index 89c64ada8732..66aac2881ba8 100644
> ---
Currently, addr_has_metadata() returns true for every address.
An invalid address (e.g. NULL) passed to the function when,
KASAN_HW_TAGS is enabled, leads to a kernel panic.
Make addr_has_metadata() return true for valid addresses only.
Note: KASAN_HW_TAGS support for vmalloc will be added with a
In the future we would pass the unsigned long long parameter
like(0x123456781234) in cmdline on the 64bit platform, so add a new
option parse function get_option_ull()
Signed-off-by: Wesley Zhao
---
include/linux/kernel.h | 2 ++
lib/cmdline.c | 94 +
An IIO device will have multiple buffers, but it shouldn't be allowed that
an IIO buffer should belong to more than 1 IIO device.
Once things get moved more from IIO device to the IIO buffer, and an IIO
device will be able to have more than 1 buffer attached, there will be a
need for a back-ref to
We only need a chardev if we need to support buffers and/or events.
With this change, a chardev will be created only if an IIO buffer is
attached OR an event_interface is configured.
Otherwise, no chardev will be created, and the IIO device will get
registered with the 'device_add()' call.
Quite
Continuing from:
https://lore.kernel.org/linux-iio/20201117162340.43924-1-alexandru.ardel...@analog.com/
Changelog v1 -> v2:
* 'iio: buffer: rework buffer & scan_elements dir creation'
add more doc-strings detailing the reasoning for this change
* 'iio: buffer: re-route scan_elements via it's
Hey Takashi,
This patch is generating a checkpatch warning, but I think it is
spurious and can be ignored.
Other than that, this looks good to me.
Reviewed-by: Robert Foss
On Wed, 20 Jan 2021 at 12:51, Takashi Iwai wrote:
>
> dvb_usb_device_init() copies the properties to the own data, so that
On Fri, 22 Jan 2021 at 21:07, Paul E. McKenney wrote:
>
> On Fri, Jan 22, 2021 at 03:21:07PM +0530, Naresh Kamboju wrote:
> > On Fri, 22 Jan 2021 at 03:13, Paul E. McKenney wrote:
> > >
> > > On Thu, Jan 21, 2021 at 09:31:10PM +, Will Deacon wrote:
> > > > On Thu, Jan 21, 2021 at 10:55:21AM -
Refactor of_mdiobus_register_phy() to use fwnode_mdiobus_register_phy().
Signed-off-by: Calvin Johnson
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/net/mdio/of_mdio.c | 40 +-
1 file changed, 1 insertion(+), 39 deletions(-)
diff -
On 22/01/2021 15:32, Pierre-Louis Bossart wrote:
Are you suggesting that we have dailink for each usecase like:
"headset capture"
"Analog MIC1 capture"
"Analog MIC2 Capture"
...
"Analog MIC4 Capture"
...
"DMIC0 capture"
"DMIC1 Capture"
"DMIC2 Capture"
...
"DMIC7 Capture"
..
"Headset Pl
On an octacore ARM64 device running ChromeOS Linux kernel v5.4, I found
that there are a lot of calls to update_blocked_averages(). This causes
the schedule loop to slow down to taking upto 500 micro seconds at
times (due to newidle load balance). I have also seen this manifest in
the periodic bala
Introduce fwnode_mdiobus_register() to register PHYs on the mdiobus.
If the fwnode is DT node, then call of_mdiobus_register().
If it is an ACPI node, then call acpi_mdiobus_register().
Signed-off-by: Calvin Johnson
---
Changes in v4:
- Remove redundant else from fwnode_mdiobus_register()
Chan
fwnode_mdiobus_register() internally takes care of both DT
and ACPI cases to register mdiobus. Replace existing
of_mdiobus_register() with fwnode_mdiobus_register().
Note: For both ACPI and DT cases, endianness of MDIO controller
need to be specified using "little-endian" property.
Signed-off-by:
On Fri, 22 Jan 2021 at 20:39, Rafael J. Wysocki wrote:
>
> On Thu, Jan 21, 2021 at 8:01 PM Rafael J. Wysocki wrote:
> >
> > On Thu, Jan 21, 2021 at 6:23 PM Nicolas Pitre wrote:
> > >
> > > The clock API splits its interface into sleepable ant atomic contexts:
> > >
> > > - clk_prepare/clk_unprep
701 - 800 of 1467 matches
Mail list logo
