On Mon, Oct 26, 2020 at 10:12:30PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> gcc points out a suspicious mixing of enum types in a function that
> converts from MTHCA_OPCODE_* values to IB_WC_* values:
>
> drivers/infiniband/hw/mthca/mthca_cq.c: In function 'mthca_poll_one':
> driver
Hi Catalin,
On Tue, 2020-11-10 at 18:17 +, Catalin Marinas wrote:
> On Fri, Nov 06, 2020 at 07:46:29PM +0100, Nicolas Saenz Julienne wrote:
> > On Thu, 2020-11-05 at 16:11 +, James Morse wrote:
> > > On 03/11/2020 17:31, Nicolas Saenz Julienne wrote:
> > > > crashkernel might reserve memor
On Thu, Nov 12, 2020 at 03:02:17PM +, Lucas Tanure wrote:
> _regmap_write can trigger a _regmap_select_page, which will call
> another _regmap_write that will be executed first, but the log shows
> the inverse order
>
> Also, keep consistency with _regmap_read which only logs in case of
> succ
Wei Liu writes:
> They are used to deposit pages into Microsoft Hypervisor and bring up
> logical and virtual processors.
>
> Signed-off-by: Lillian Grassin-Drake
> Signed-off-by: Sunil Muthuswamy
> Signed-off-by: Nuno Das Neves
> Co-Developed-by: Lillian Grassin-Drake
> Co-Developed-by: Suni
> >
> > Again, if anything in this flow doesn't happen HW mic mute is still
> activated,
> > just will take longer (for duration of timeout) and have popping noise.
>
> Thank you, can we put this in a comment in the driver please ?
Yes, I agree. I suggested to Perry that his next submission of t
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-5.10-rc4
with top-most commit fcb3a1ab79904d54499db77017793ccca665eb7e
cpufreq: intel_pstate: Take CPUFREQ_GOV_STRICT_TARGET into account
on top of commit f8394f232b1eab649ce2df5c5f15b0
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
On 11/9/20 10:34 PM, Kishon Vijay Abraham I wrote:
> Add sub-nodes to SERDES0 DT node to represent SERDES0 is connected
> to PCIe and QSGMII (multi-link SERDES).
>
> Signed-off-by: Kishon Vijay Abraham I
> ---
> .../dts/ti/k3-j7200-common-proc-board.dts | 23 +++
> 1 file
On Mon, Nov 02, 2020 at 15:10 Hedi Berriche wrote:
Commit 6d2c89441571 ("PCI/ERR: Update error status after reset_link()")
broke pcie_do_recovery(): updating status after reset_link() has the ill
side effect of causing recovery to fail if the error status is
PCI_ERS_RESULT_CAN_RECOVER or PCI_ERS_
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
On Tue, Nov 10, 2020 at 11:12 PM Andrey Konovalov wrote:
>
> From: Vincenzo Frascino
>
> This test is specific to MTE and verifies that the GCR_EL1 register
> is context switched correctly.
>
> It spawn 1024 processes and each process spawns 5 threads. Each thread
Nit: "spawns"
> + srand
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
acpi-5.10-rc4
with top-most commit 7222a8a52c9ec59affc4d6c4e2632b3e4a44cd27
Merge branches 'acpi-scan', 'acpi-misc', 'acpi-button' and 'acpi-dptf'
on top of commit f8394f232b1eab649ce2df5c
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
On 12/11/2020 15:41, Qais Yousef wrote:
> On 11/11/20 18:41, Dietmar Eggemann wrote:
>> On 10/11/2020 13:21, Peter Zijlstra wrote:
>>> On Tue, Nov 03, 2020 at 10:37:56AM +0800, Yun Hsiang wrote:
[...]
> I assume we agree then that we don't want to explicitly document this quirky
> feature and kee
From: Ioana Ciornei
This patch set aims to actually add support for shared interrupts in
phylib and not only for multi-PHY devices. While we are at it,
streamline the interrupt handling in phylib.
For a bit of context, at the moment, there are multiple phy_driver ops
that deal with this subject:
On Tue, 10 Nov 2020 10:00:47 +0800 Po-Hsu Lin wrote:
> The pmtu.sh test script treats all non-zero return code as a failure,
> thus it will be marked as FAILED when some sub-test got skipped.
>
> This patchset will:
> 1. Use the kselftest framework skip code $ksft_skip to replace the
> hard
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
On 05/11/2020 14:38, Mark Rutland wrote:
Hi,
> On Thu, Nov 05, 2020 at 02:29:49PM +, Mark Brown wrote:
>> On Thu, Nov 05, 2020 at 02:03:22PM +, Mark Rutland wrote:
>>> On Thu, Nov 05, 2020 at 01:41:42PM +, Mark Brown wrote:
>>
It isn't obvious to me why we don't fall through to t
Convert device tree bindings for Microsemi Ocelot SoC ICPU Interrupt
Controller to YAML format
Signed-off-by: Gregory CLEMENT
---
.../mscc,ocelot-icpu-intr.txt | 21 ---
.../mscc,ocelot-icpu-intr.yaml| 59 +++
2 files changed, 59 insertions(+),
Add the Device Tree binding documentation for the Microsemi Jaguar2,
Luton and Serval interrupt controller that is part of the ICPU. It is
connected directly to the MIPS core interrupt controller.
Signed-off-by: Gregory CLEMENT
---
.../bindings/interrupt-controller/mscc,ocelot-icpu-intr.yaml |
Hello,
Ocelot SoC belongs to a larger family of SoCs which use the same
interrupt controller with a few variation.
This series of patches add support for Luton, Serval and Jaguar2, they
are all MIPS based.
The first patches of the series also updates the binding documentation
with the new compat
This patch extends irqchip driver for oceleot to be used with an other
vcoreiii base platform: Luton.
Based on a larger patch from Lars Povlsen
Signed-off-by: Gregory CLEMENT
---
drivers/irqchip/irq-mscc-ocelot.c | 145 +-
1 file changed, 123 insertions(+), 22 deleti
This patch extends irqchip driver for ocelot to be used with an other
vcoreiii base platform: Jaguar2.
Based on a larger patch from Lars Povlsen
Signed-off-by: Gregory CLEMENT
---
drivers/irqchip/irq-mscc-ocelot.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers
On 11/9/20 10:34 PM, Kishon Vijay Abraham I wrote:
> Add PCIe device tree node (both RC and EP) for the single PCIe
> instance present in j7200.
>
nit: s/j7200/J7200
> Signed-off-by: Kishon Vijay Abraham I
> ---
Reviewed-by: Vignesh Raghavendra
[...]
On Wed, Nov 11, 2020 at 02:39:34PM +, Ben Hutchings wrote:
On Wed, 2020-11-11 at 13:44 +0100, Pavel Machek wrote:
Hi!
> Thankfully it's handled by the only caller, btree_write_cache_pages(),
> as later write_one_eb() call will trigger submit_one_bio(). So there
> shouldn't be any problem.
On Wed, Nov 11, 2020 at 05:56:52PM +0530, Sameer Pujar wrote:
> There can be customized sound cards which are based on generic audio
> graph. In such cases most of the stuff is reused from generic audio
> graph. To facilitate this, refactor audio graph schema into multiple
> files and the base sche
On 12.11.20 15:37, Vlastimil Babka wrote:
On 11/11/20 4:38 PM, David Hildenbrand wrote:
On 03.11.20 16:22, Vlastimil Babka wrote:
Commit 11c9c7edae06 ("mm/page_poison.c: replace bool variable with static key")
changed page_poisoning_enabled() to a static key check. However, the function
is not
On 12.11.20 15:39, Vlastimil Babka wrote:
On 11/11/20 4:42 PM, David Hildenbrand wrote:
...
@@ -1152,12 +1152,18 @@ void clear_free_pages(void)
if (WARN_ON(!(free_pages_map)))
return;
- if (IS_ENABLED(CONFIG_PAGE_POISONING_ZERO) || want_init_on_free()) {
+ if (
On Wed, Nov 11, 2020 at 05:56:53PM +0530, Sameer Pujar wrote:
> Since audio graph schema is refactored now update the related
> references here.
>
> Signed-off-by: Sameer Pujar
> Cc: Kuninori Morimoto
> ---
> Documentation/devicetree/bindings/sound/renesas,rsnd.yaml | 6 ++
> 1 file changed
On Thu, Nov 12, 2020 at 04:10:46PM +0100, Jan Kara wrote:
> On Thu 12-11-20 12:12:17, Michal Suchánek wrote:
> > On Thu, Nov 12, 2020 at 12:49:52PM +1100, Dave Chinner wrote:
> > > On Wed, Nov 11, 2020 at 11:28:48AM +0100, Michal Suchánek wrote:
> > > > On Tue, Nov 10, 2020 at 08:08:23AM +1100, Dav
On 12.11.20 16:18, Vlastimil Babka wrote:
On 11/11/20 6:58 PM, David Hildenbrand wrote:
On 11.11.20 10:28, Vlastimil Babka wrote:
- /*
-* per-cpu pages are drained after start_isolate_page_range, but
-* if there are still pages that are not free, ma
On Thu, 12 Nov 2020 at 16:59, Alexander Potapenko wrote:
>
> On Tue, Nov 10, 2020 at 11:12 PM Andrey Konovalov
> wrote:
> >
> > From: Vincenzo Frascino
> >
> > This test is specific to MTE and verifies that the GCR_EL1 register
> > is context switched correctly.
> >
> > It spawn 1024 processes
On Tue, Nov 10, 2020 at 11:12 PM Andrey Konovalov wrote:
>
> Kernel allocator code accesses metadata for slab objects, that may lie
> out-of-bounds of the object itself, or be accessed when an object is freed.
> Such accesses trigger tag faults and lead to false-positive reports with
> hardware ta
On Thu, Nov 12, 2020 at 04:43:01PM +0100, Miquel Raynal wrote:
> Hi Serge,
>
> Serge Semin wrote on Thu, 12 Nov
> 2020 18:27:39 +0300:
>
> > Hello Vignesh
> >
> > On Thu, Nov 12, 2020 at 08:30:42PM +0530, Vignesh Raghavendra wrote:
> > >
> > >
> > > On 11/12/20 1:57 PM, Miquel Raynal wrote:
On Mon, Oct 19, 2020 at 08:36:25PM -0700, Randy Dunlap wrote:
> Hi Joel,
>
> On 10/19/20 6:43 PM, Joel Fernandes (Google) wrote:
> > Document the usecases, design and interfaces for core scheduling.
> >
> > Co-developed-by: Vineeth Pillai
> > Tested-by: Julien Desfossez
> > Signed-off-by: Joel
Commit a1f9b1c0439db ("integrity/ima: switch to using __kernel_read")
replaced the __vfs_read() call in integrity_kernel_read() with
__kernel_read(), a new helper introduced by commit 61a707c543e2a ("fs: add
a __kernel_read helper").
Since the new helper requires that also the FMODE_CAN_READ flag
This patch extends irqchip driver for ocelot to be used with an other
vcoreiii base platform: Serval.
Based on a larger patch from Lars Povlsen
Signed-off-by: Gregory CLEMENT
---
drivers/irqchip/irq-mscc-ocelot.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/
On Thu, Nov 12, 2020 at 01:49PM +0100, Marco Elver wrote:
> On Thu, 12 Nov 2020 at 01:11, Paul E. McKenney wrote:
[...]
> > > This assert didn't fire yet, I just get more of the below. I'll keep
> > > rerunning, but am not too hopeful...
> >
> > Is bisection a possibility?
>
> I've been running a
Hello Thierry,
On Sun, Dec 29, 2019 at 08:05:39AM +, Yangtao Li wrote:
> Use devm_platform_ioremap_resource() to simplify code.
>
> Signed-off-by: Yangtao Li
> ---
> drivers/pwm/pwm-sun4i.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/pwm/pwm-sun4i.c
Hi Serge,
Serge Semin wrote on Thu, 12 Nov
2020 19:10:43 +0300:
> On Thu, Nov 12, 2020 at 04:43:01PM +0100, Miquel Raynal wrote:
> > Hi Serge,
> >
> > Serge Semin wrote on Thu, 12 Nov
> > 2020 18:27:39 +0300:
> >
> > > Hello Vignesh
> > >
> > > On Thu, Nov 12, 2020 at 08:30:42PM +0530, Vig
On Thu, Nov 12, 2020 at 10:07 AM Rob Herring wrote:
>
> On Wed, Nov 11, 2020 at 05:56:53PM +0530, Sameer Pujar wrote:
> > Since audio graph schema is refactored now update the related
> > references here.
> >
> > Signed-off-by: Sameer Pujar
> > Cc: Kuninori Morimoto
> > ---
> > Documentation/de
On 11/12/20 5:36 AM, Matthew Wilcox wrote:
On Wed, Nov 11, 2020 at 12:23:03PM -0700, Shuah Khan wrote:
Agreed: this is a clear wrapping sequence counter. It's only abuse would
be using it in a place where wrapping actually is _not_ safe. (bikeshed:
can we call it wrap_u32 and wrap_u64?)
Still
On Thu, Nov 12, 2020 at 03:36:35PM +0100, Sylwester Nawrocki wrote:
> On 11/10/20 20:37, Krzysztof Kozlowski wrote:
> > The Exynos clock output driver can be built as module (it does not have
> > to be part of core init process) for better customization. Adding a
> > KConfig entry allows also comp
On 11/12/20 2:32 AM, Paolo Bonzini wrote:
> On 12/11/20 01:28, Babu Moger wrote:
>> Add support to the mask_cr3_rsvd_bits() callback to mask the
>> encryption bit from the CR3 value when SEV is enabled.
>>
>> Additionally, cache the encryption mask for quick access during
>> the check.
>>
>> Fix
Add initial support for the OnePlus 6 (enchilada) and 6T (fajita) based
on the sdm845-mtp DT. Support includes:
* Display panels and Adreno 630
* Touch screen support with synaptics rmi4
* All remoteprocs start correctly
* WLAN / Bluetooth
* Volume / power buttons and OnePlus Tri-State switch are
On Thu, Nov 12, 2020 at 05:15:10PM +0100, Miquel Raynal wrote:
> Hi Serge,
>
> Serge Semin wrote on Thu, 12 Nov
> 2020 19:10:43 +0300:
>
> > On Thu, Nov 12, 2020 at 04:43:01PM +0100, Miquel Raynal wrote:
> > > Hi Serge,
> > >
> > > Serge Semin wrote on Thu, 12 Nov
> > > 2020 18:27:39 +0300:
>
The OnePlus 6/T devices use different panels however they are
functionally identical with the only differences being the resolution.
The panels also don't seem to be used by any other devices, just combine
them into one driver.
The panels are: samsung,sofef00
and samsung,s6e3fc2x01
Si
Used by the OnePlus 6/T device trees
Signed-off-by: Caleb Connolly
---
.../bindings/arm/oneplus/oneplus-boards.yaml | 25 +++
.../devicetree/bindings/vendor-prefixes.yaml | 2 ++
2 files changed, 27 insertions(+)
create mode 100644
Documentation/devicetree/bindings/arm/onepl
Add compatibles for the samsung,sofef00 and samsung,s6e3fc2x01 panels
used in the OnePlus 6 & 6T respectively.
Signed-off-by: Caleb Connolly
---
.../devicetree/bindings/display/panel/panel-simple-dsi.yaml | 4
1 file changed, 4 insertions(+)
diff --git
a/Documentation/devicetree/binding
On Thu, Nov 12, 2020 at 03:09:29PM +0100, Sylwester Nawrocki wrote:
> Add maintainers entry for the Samsung SoC interconnect drivers, this
> currently includes the Exynos generic interconnect driver.
>
> Reviewed-by: Chanwoo Choi
> Signed-off-by: Sylwester Nawrocki
> ---
> Changes for v9:
> - a
The OnePlus 6/T has the same issue as the Yoga c630 causing a crash when DMA
is used for i2c, so disable it.
https://patchwork.kernel.org/patch/11133827/
Signed-off-by: Caleb Connolly
---
drivers/i2c/busses/i2c-qcom-geni.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
On 10.11.20 19:06, Mike Rapoport wrote:
On Tue, Nov 10, 2020 at 06:17:26PM +0100, David Hildenbrand wrote:
On 10.11.20 16:14, Mike Rapoport wrote:
From: Mike Rapoport
It will be used by the upcoming secret memory implementation.
Signed-off-by: Mike Rapoport
---
mm/internal.h | 3 +++
m
On Tue, Nov 10, 2020 at 11:57:53AM -0800, Roman Gushchin wrote:
> In general it's unknown in advance if a slab page will contain
> accounted objects or not. In order to avoid memory waste, an
> obj_cgroup vector is allocated dynamically when a need to account
> of a new object arises. Such approach
On 11.11.20 10:28, Vlastimil Babka wrote:
All per-cpu pagesets for a zone use the same high and batch values, that are
duplicated there just for performance (locality) reasons. This patch adds the
same variables also to struct zone as a shared copy.
This will be useful later for making possible
On Fri, Sep 25, 2020 at 5:46 AM liush wrote:
>
> This patch adds a simple cpuidle driver for RISC-V systems using
> the WFI state. Other states will be supported in the future.
>
> Reported-by: kernel test robot
This isn't needed in a patch adding a new driver.
> Signed-off-by: liush
> ---
> C
Adding other vsprintf maintainers and reviewes into CC.
On Thu 2020-11-12 11:17:59, Richard Fitzgerald wrote:
> Number conversion in vsscanf converts a whole string of digits and then
> extracts the field width part from the converted value. The maximum run
> of digits is limited by overflow. Conv
On Thu, 12 Nov 2020 00:14:55 -0800 Xie He wrote:
> On Wed, Nov 11, 2020 at 11:06 PM Martin Schiller wrote:
> > But I still think it is important that we either repair or delete the
> > linux-x25 mailing list. The current state that the messages are going
> > into nirvana is very unpleasant.
>
>
On Tue, Nov 10, 2020 at 02:07:58PM -0800, Roman Gushchin wrote:
> The non-hierarchical cgroup v1 mode is a legacy of early days
> of the memory controller and doesn't bring any value today.
> However, it complicates the code and creates many edge cases
> all over the memory controller code.
>
> It
On Tue, Nov 10, 2020 at 02:07:59PM -0800, Roman Gushchin wrote:
> Update cgroup v1 docs after the deprecation of the non-hierarchical
> mode of the memory controller.
>
> Signed-off-by: Roman Gushchin
> Reviewed-by: Shakeel Butt
> Acked-by: Michal Hocko
> Acked-by: David Rientjes
Acked-by: Jo
On Thu, 2020-11-12 at 15:23 +, Luis Henriques wrote:
> This reverts commit dffdcd71458e699e839f0bf47c3d42d64210b939.
>
> When doing a rename across quota realms, there's a corner case that isn't
> handled correctly. Here's a testcase:
>
> mkdir files limit
> truncate files/file -s 10G
>
On Tue, Nov 10, 2020 at 02:08:00PM -0800, Roman Gushchin wrote:
> With the deprecation of the non-hierarchical mode of the memory
> controller there are no more examples of broken hierarchies left.
>
> Let's remove the cgroup core code which was supposed to print
> warnings about creating of broke
On Thu, Nov 12, 2020 at 09:19:04PM +0530, Akhil P Oommen wrote:
> So far a530v2 gpu has support for detecting its supported opps
> based on a fuse value called speed-bin. This patch makes this
> support generic across gpu families. This is in preparation to
> extend speed-bin support to a6x family.
Hello, this v4 follows discussion on how to better handle the initial
reverse channel amplitude and incorporate Geert's and Kieran suggestion
to use the value in millivolts instead of relying on a boolean property.
v4:
- Replace 'maxim-high-threshold' with 'maxim,initial-reverse-channel-mV'
- Incr
On Thu, Nov 12, 2020 at 7:49 AM Akhil P Oommen wrote:
>
> So far a530v2 gpu has support for detecting its supported opps
> based on a fuse value called speed-bin. This patch makes this
> support generic across gpu families. This is in preparation to
> extend speed-bin support to a6x family.
>
> Si
Use the newly introduced 'maxim,maxim,initial-reverse-channel-mV'
property to specify the initial reverse channel amplitude when the
remote serializers are not pre-programmed with noise immunity threshold
enabled.
Signed-off-by: Jacopo Mondi
---
arch/arm64/boot/dts/renesas/r8a77970-eagle.dts | 1
Instrument the function that configures the reverse channel with a
programmable amplitude value.
This change serves to prepare to adjust the reverse channel amplitude
depending on the remote end high-threshold configuration.
Reviewed-by: Kieran Bingham
Signed-off-by: Jacopo Mondi
---
drivers/m
The RDACM21 is a GMSL camera supporting 1280x1080 resolution images
developed by IMI based on an Omnivision OV10640 sensor, an Omnivision
OV490 ISP and a Maxim MAX9271 GMSL serializer.
The driver uses the max9271 library module, to maximize code reuse with
other camera module drivers using the sam
Break out the reverse channel setup configuration procedure to its own
function.
This change prepares for configuring the reverse channel conditionally
to the remote side high threshold configuration.
No functional changes intended.
Reviewed-by: Kieran Bingham
Signed-off-by: Jacopo Mondi
---
Document the 'initial-reverse-channel-mV' vendor property in the
bindings document of the max9286 driver.
The newly introduced property allows to specify the initial
configuration of the GMSL reverse control channel to accommodate
remote serializers pre-programmed with the high threshold power
sup
From: Laurent Pinchart
Add a .dtsi fragment to describe the MAX9286-based expansion board for
the Renesas Salvator-X board.
The MAX9286 expansion board has eight RDACM20 cameras connected to it.
They can be individually controlled by enabling or disabling the macro
defines.
Signed-off-by: Laure
Use devm_rpi_firmware_get() so as to make sure we release RPi's firmware
interface when unbinding the device.
Signed-off-by: Nicolas Saenz Julienne
---
Changes since v3:
- Release firmware handle in probe function
Changes since v2:
- Use devm_rpi_firmware_get(), instead of remove function
d
The aim of this series is to add support to the fan found on RPi's PoE
HAT. Some commentary on the design can be found below. But the imporant
part to the people CC'd here not involved with PWM is that, in order to
achieve this properly, we also have to fix the firmware interface the
driver uses to
On Thu, Nov 12, 2020 at 8:22 AM Geert Uytterhoeven wrote:
>
> Hi Dejin,
>
> On Thu, May 28, 2020 at 6:18 PM Dejin Zheng wrote:
> > Use devm_platform_ioremap_resource_byname() to simplify codes.
> > it contains platform_get_resource_byname() and devm_ioremap_resource().
> >
> > Signed-off-by: Deji
Adjust the initial reverse channel amplitude parsing from
firmware interface the 'maxim,initial-reverse-channel-mV'
property.
This change is required for both rdacm20 and rdacm21 camera
modules to be correctly probed when used in combination with
the max9286 deserializer.
Signed-off-by: Jacopo Mo
Use the newly introduced 'maxim,maxim,initial-reverse-channel-mV'
property to specify the initial reverse channel amplitude when
the remote serializers are pre-programmed with noise immunity threshold
enabled.
Signed-off-by: Jacopo Mondi
---
arch/arm64/boot/dts/renesas/salvator-x-max9286.dtsi |
On Wed, Nov 04, 2020 at 04:45:54PM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky
>
> v1: Added Jason's variant of first patch
> v0: https://lore.kernel.org/lkml/20201012045600.418271-1-l...@kernel.org
>
> Leon Romanovsky (2):
> RDMA/core: Postpone uobject cleanup on failure till FD clo
On Tue, 10 Nov 2020 at 13:11, Naresh Kamboju wrote:
>
> While running CPU hotplug testing on arm64 db410c device the following
> kernel warning
> noticed on linux stable-rc 4.19 branch. I did not bisect this problem yet.
As per the available data the reported issue started happening from 4.19.134
On Tue, Nov 03, 2020 at 07:57:54PM +0800, Zou Wei wrote:
> Fix below warning reported by coccicheck:
>
> ./ib_isert.c:1104:12-24: WARNING: Comparison to bool
>
> Reported-by: Hulk Robot
> Signed-off-by: Zou Wei
> Reviewed-by: Sagi Grimberg
> ---
> drivers/infiniband/ulp/isert/ib_isert.c | 2 +
first appeared in the linux-next today. Does it ring any
bells?
[12065.065837][ T1310] INFO: task trinity-c30:91730 blocked for more than 368
seconds.
[12065.073524][ T1310] Tainted: G L
5.10.0-rc3-next-20201112 #2
[12065.081076][ T1310] "echo 0 > /proc/sys/kerne
The pca9685 driver supports a new staggered-outputs property for reduced
current surges and EMI. This adds documentation for the new DT property.
Signed-off-by: Clemens Gruber
---
Documentation/devicetree/bindings/pwm/nxp,pca9685-pwm.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Docu
On 00:41-20201103, Faiz Abbas wrote:
> There are 4 instances of gpio modules in main domain:
> gpio0, gpio2, gpio4 and gpio6
>
> Groups are created to provide protection between different processor virtual
> worlds. Each of these modules I/O pins are muxed within the group. Exactly
> one mod
When unbinding the firmware device we need to make sure it has no
consumers left. Otherwise we'd leave them with a firmware handle
pointing at freed memory.
Keep a reference count of all consumers and introduce rpi_firmware_put()
which will permit automatically decrease the reference count upon
un
On Thu, Nov 12, 2020 at 5:09 PM Marco Elver wrote:
>
> On Thu, 12 Nov 2020 at 16:59, Alexander Potapenko wrote:
> >
> > On Tue, Nov 10, 2020 at 11:12 PM Andrey Konovalov
> > wrote:
> > >
> > > From: Vincenzo Frascino
> > >
> > > This test is specific to MTE and verifies that the GCR_EL1 regist
Use devm_rpi_firmware_get() so as to make sure we release RPi's firmware
interface when unbinding the device.
Signed-off-by: Nicolas Saenz Julienne
---
Changes since v2:
- Use devm_rpi_firmware_get(), instead of remove function
drivers/clk/bcm/clk-raspberrypi.c | 2 +-
1 file changed, 1 inser
On Fri, Oct 23, 2020 at 02:12:19PM +0200, Ulf Hansson wrote:
> SD spec mentions the write-protect switch on SD cards, while uSD cards
> doesn't have one. In general, host drivers implement support for it
> via a dedicated GPIO line routed to one of the pins in the SD slot.
>
> In this SD controlle
On 00:41-20201103, Faiz Abbas wrote:
> The following patches add gpio support for TI's J7200 platform.
>
> These patches were posted as a part of an older series but have now
> been split into three parts. The 3 parts add configs, gpios and MMC/SD
> related dts patches respectively.
>
> Older ser
601 - 700 of 1451 matches
Mail list logo
