On Wed, Mar 17, 2021 at 06:59:59PM -0700, Shakeel Butt wrote:
> The function swap_readpage() (and other functions it call) extracts swap
> entry from page->private. However for SWP_SYNCHRONOUS_IO, the kernel
> skips the swapcache and thus we need to manually set the page->private
> with the swap
When using Clause-22 to probe for PHY devices such as the Marvell
88E2110, PHY ID with value 0 is read from the MII PHYID registers
which caused the PHY framework failed to attach the Marvell PHY
driver.
Fixed this by adding a check of PHY ID equals to all zeroes.
Fixes: ee951005e95e ("net: phy:
On Tue, 2021-03-16 at 13:48 -0600, Rob Herring wrote:
> Users of common properties shouldn't have a type definition as the
> common schemas already have one. Drop all the unnecessary type
> references in the tree.
>
> A meta-schema update to catch these is pending.
>
> Cc: Nicolas Saenz Julienne
Kindly pinging...
Best Regards,
Joakim Zhang
> -Original Message-
> From: Joakim Zhang
> Sent: 2021年3月4日 19:40
> To: robh...@kernel.org; shawn...@kernel.org; s.ha...@pengutronix.de;
> feste...@gmail.com
> Cc: ker...@pengutronix.de; dl-linux-imx ;
> devicet...@vger.kernel.org;
When a CPU is hot added, the CPU ids are taken from the available mask from
the lower possible set. If that set of values was previously used for CPU
attached to a different node, this seems to application like if these CPUs
have migrated from a node to another one which is not expected in real
Am 2021-03-18 09:34, schrieb Michael Walle:
Don't enable the optee node in the SoC include. It is an optional
component and actually, if enabled, breaks boards which doesn't have
it.
This reverts commit 48787485f8de ("arm64: dts: ls1028a: enable optee
node") and enables the node per board,
On 2021/3/17 22:57, Joe Perches wrote:
On Wed, 2021-03-17 at 17:41 +0800, Qi Liu wrote:
Use the generic sysfs_emit_at() function take place of scnprintf()
[]
diff --git a/drivers/perf/arm-ccn.c b/drivers/perf/arm-ccn.c
[]
@@ -328,41 +328,37 @@ static ssize_t arm_ccn_pmu_event_show(struct
The Qualcomm SM8350 platform has several bus fabrics that could be
controlled and tuned dynamically according to the bandwidth demand.
Signed-off-by: Vinod Koul
---
.../bindings/interconnect/qcom,rpmh.yaml | 10 +
.../dt-bindings/interconnect/qcom,sm8350.h| 172 ++
2
From: ganjisheng
Signed-off-by: ganjisheng
---
drivers/mfd/ab8500-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mfd/ab8500-core.c b/drivers/mfd/ab8500-core.c
index a903791..f5b0874 100644
--- a/drivers/mfd/ab8500-core.c
+++ b/drivers/mfd/ab8500-core.c
@@
Add driver for the Qualcomm interconnect buses found in SM8350 based
platforms. The topology consists of several NoCs that are controlled by
a remote processor that collects the aggregated bandwidth for each
master-slave pairs.
Generated from downstream interconnect driver written by David Dai
This adds support for interconnect support for SM8350 SoC
Changes since v2:
- Plug gaps in indexes
- fix typo in commit log for patch2 and kconfig depends (for real this time)
Changes since v1:
- Fix comments by Georgi, split the header
- Fix the macro for qns_llcc
Vinod Koul (2):
On Wed, Mar 17, 2021 at 06:48:50PM +0800, Huang Rui wrote:
> Series are Acked-by: Huang Rui
Thanks, series is applied for v5.12
> -Original Message-
> From: Kishon Vijay Abraham I
> Sent: Wednesday, March 10, 2021 9:25 PM
> To: Kishon Vijay Abraham I ; Vinod Koul
> ; Rob Herring ; Philipp Zabel
> ; Swapnil Kashinath Jakhade
>
> Cc: linux-kernel@vger.kernel.org; devicet...@vger.kernel.org; Lokesh Vutla
> ;
From: Leon Romanovsky
Hi,
This series from Mark fixes long standing bug in CM migration logic,
reported by Ryan [1].
Thanks
[1]
https://lore.kernel.org/linux-rdma/cafmmrnx9cg--nunzjfm8ywqfaetsmawv4eogkb3a0+hnjdt...@mail.gmail.com/
Mark Zhang (6):
Revert "IB/cm: Mark stale CM id's whenever
On Thu 18-03-21 10:59:10, Oscar Salvador wrote:
> On Thu, Mar 18, 2021 at 10:29:57AM +0100, Michal Hocko wrote:
> > On Thu 18-03-21 09:54:01, Oscar Salvador wrote:
> > [...]
> > > @@ -2287,10 +2288,12 @@ static int alloc_and_dissolve_huge_page(struct
> > > hstate *h, struct page *old_page)
> > >
On 3/18/21 7:57 AM, Christoph Hellwig wrote:
> Various malta defconfigs enable CONFIG_IDE for the tc86c001 ide driver,
> hich is a Toshiba plug in card that does not make much sense to use on
^ which is for
> bigsur platforms. For all other ATA cards libata support is already
^ Malta.
>
On Wed, Mar 17, 2021 at 08:58:34AM +0800, Lu Baolu wrote:
> The pasid_lock is used to synchronize different threads from modifying a
> same pasid directory entry at the same time. It causes below lockdep splat.
>
> [ 83.296538]
> [
s/bariers/barriers/
Signed-off-by: Bhaskar Chowdhury
---
drivers/gpu/drm/i915/gt/intel_timeline.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/gt/intel_timeline.c
b/drivers/gpu/drm/i915/gt/intel_timeline.c
index 037b0e3ccbed..25fc7f44fee0 100644
Hello!
On 3/18/21 12:26 AM, John Paul Adrian Glaubitz wrote:
>> b) do anything?
>
> It fixes the problem for me.
Here are the kernel messages with your patch applied:
[0.00] Linux version 5.12.0-rc3+ (glaubitz@epyc) (ia64-linux-gcc (GCC)
10.1.0, GNU ld (GNU Binutils) 2.34) #207 SMP
From: Xiong Zhenwu
A typo is found out by codespell tool in 383th line of smackfs.c:
$ codespell ./security/smack/
./smackfs.c:383: numer ==> number
Fix a typo found by codespell.
Signed-off-by: Xiong Zhenwu
---
security/smack/smackfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
> -Original Message-
> From: Shawn Guo
> Sent: 2021年3月18日 18:48
> To: Joakim Zhang
> Cc: robh...@kernel.org; s.ha...@pengutronix.de; feste...@gmail.com;
> ker...@pengutronix.de; dl-linux-imx ;
> devicet...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
>
On Wed, Mar 17, 2021 at 03:05:40PM +0100, Michal Hocko wrote:
> That being said, bailing out early makes sense to me. But now that
> you've made me look into the migrate_pages excellent error state reporting
> I suspect we have a bug here. Note the
> "Returns the number of pages that were not
On 17.03.21 21:03, Hans de Goede wrote:
Hi,
It just identifies the box and tells subsequent drivers which one it
is, which watchdog and LED path to take. Moving the knowledge of which
box has which LED/watchdog into the respective drivers seems to be the
better way to go.
So we would end up
On 18/03/2021 11.46, Petr Mladek wrote:
> BTW: Is the trick with int (printk)(const char *s, ...) documented
> somewhere? Is it portable?
It is completely standard and portable C, explicitly spelled out in the
C standard itself. C99:
===
6.10.3 Macro replacement
10 [...] Each subsequent
From: Valdis Kletnieks
> Sent: 18 March 2021 06:02
>
> On Wed, 17 Mar 2021 22:52:56 -0700, Kees Cook said:
> > On Mon, Mar 08, 2021 at 03:40:21AM -0500, Valdis KlDtnieks wrote:
> > > It turns out that older gcc (4.9 and 5.4) have gnu++11 support, but
> > > due to a gcc bug fixed in gcc6, throw
On Tue, Mar 16, 2021 at 08:10:47AM -0700, Yu-cheng Yu wrote:
> There was no more caller passing vm_flags to do_mmap(), and vm_flags was
> removed from the function's input by:
>
> commit 45e55300f114 ("mm: remove unnecessary wrapper function
> do_mmap_pgoff()").
>
> There is a new user now.
On Wed, Mar 17, 2021 at 08:17:52PM +0800, Jin, Yao wrote:
SNIP
> > >
> > > For example,
> > >
> > > perf stat -e '{cpu_core/cycles/,cpu_core/instructions/}' -e
> > > '{cpu_atom/cycles/,cpu_atom/instructions/}'
> > >
> > > This usage is common and reasonable. So I think we may need to support
From: Xiong Zhenwu
A typo is found out by codespell tool in 1734th line of drop_monitor.c:
$ codespell ./net/core/
./net/core/drop_monitor.c:1734: guarnateed ==> guaranteed
Fix a typo found by codespell.
Signed-off-by: Xiong Zhenwu
---
net/core/drop_monitor.c | 2 +-
1 file changed, 1
As per the current implementation, after FSC (Full Scale Current)
and brightness update the sync bits are set-then-cleared.
But, the FSC and brightness sync takes place when the sync bits are
set (e.g. on a rising edge). So the hardware team recommends a
clear-then-set approach in order to
On 3/15/21 7:02 PM, Kees Cook wrote:
> The state of CONFIG_INIT_ON_ALLOC_DEFAULT_ON (and ...ON_FREE...) did not
> change the assembly ordering of the static branches: they were always out
> of line. Use the new jump_label macros to check the CONFIG settings to
> default to the "expected" state,
The ones remove here not only fail to conform to kernel-doc, but also
provide no value, so let's remove them completely in this case.
Fixes the following W=1 kernel build warning(s):
drivers/crypto/ux500/hash/hash_core.c:368: warning: Function parameter or
member 'ctx' not described in
Fixes the following W=1 kernel build warning(s):
drivers/crypto/keembay/ocs-hcu.c:107: warning: expecting prototype for struct
ocs_hcu_dma_list. Prototype was for struct ocs_hcu_dma_entry instead
drivers/crypto/keembay/ocs-hcu.c:127: warning: expecting prototype for struct
ocs_dma_list.
Fixes the following W=1 kernel build warning(s):
drivers/crypto/atmel-ecc.c:41: warning: cannot understand function prototype:
'struct atmel_ecdh_ctx '
Cc: Tudor Ambarus
Cc: Herbert Xu
Cc: "David S. Miller"
Cc: Nicolas Ferre
Cc: Alexandre Belloni
Cc: Ludovic Desroches
Cc:
From: zuoqilin
Change 'revsion' to 'revision'.
Signed-off-by: zuoqilin
---
drivers/hwmon/ftsteutates.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwmon/ftsteutates.c b/drivers/hwmon/ftsteutates.c
index ef88a15..e87aa00 100644
--- a/drivers/hwmon/ftsteutates.c
On 17/03/2021 17:45, Ricardo Ribalda wrote:
> Use the device name for the card name instead of vdev->name.
>
> Suggested-by: Laurent Pinchart
> Signed-off-by: Ricardo Ribalda
> ---
> drivers/media/usb/uvc/uvc_v4l2.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git
On 18.03.21 05:46, Matthew Wilcox wrote:
On Wed, Mar 17, 2021 at 10:12:02AM +0100, David Hildenbrand wrote:
+ if (IS_ENABLED(CONFIG_MEMORY_FAILURE) && ret == 1) {
+ if (unlikely(PageHuge(page) &&
PageHWPoison(compound_head(page
+ ret = 0;
+
On Wed, Mar 17, 2021 at 11:38:38AM +0800, Jiapeng Chong wrote:
> Fix the following coccicheck warnings:
>
> ./net/rxrpc/rxkad.c:1140:2-5: WARNING: Use BUG_ON instead of if
> condition followed by BUG.
>
> Reported-by: Abaci Robot
> Signed-off-by: Jiapeng Chong
> ---
> net/rxrpc/rxkad.c | 5
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
branch HEAD: 77c781e43bc2f110ce8f73c4f81ca3d9f349ef72 Merge branch 'irq/core'
elapsed time: 726m
configs tested: 121
configs skipped: 2
The following configs have been built successfully.
More configs may be tested
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86/core
branch HEAD: 0705ef64d1ff52b817e278ca6e28095585ff31e1 tools/insn: Restore the
relative include paths for cross building
elapsed time: 725m
configs tested: 106
configs skipped: 2
The following configs have been
On 3/18/21 9:07 AM, Pavel Andrianov wrote:
Hi,
berlin2_adc_probe [1] registers two interrupt handlers:
berlin2_adc_irq [2]
and berlin2_adc_tsen_irq [3]. The interrupt handlers operate with the
same data, for example, modify
priv->data with different masks:
priv->data &= BERLIN2_SM_ADC_MASK;
> From: iommu On Behalf Of
> Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
>
> > 2. Consider ensuring that the problem is not somehow related to queued
> > invalidations. Try to use __iommu_flush_iotlb() instead of qi_flush_iotlb().
> >
>
> I tried to force to use
On Wed, Mar 17, 2021 at 03:35:41PM +0100, David Hildenbrand wrote:
> Just assume you have two ranges
>
> [ ZONE_DEVICE 0 ][ ZONE_DEVICE 1]
>
> If the vmemmap of ZONE_DEVICE 1 could be taken from the altmap of
> ZONE_DEVICE 0, we could be in trouble, as both parts can be
> removed/repurposed
Hi,
we've received a bug report about rfkill change that was introduced in
5.11. While the systemd-rfkill expects the same size of both read and
write, the kernel rfkill write cuts off to the old 8 bytes while read
gives 9 bytes, hence it leads the error:
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq/core
branch HEAD: 2c6b02185cc608c19a22691fadc6ca2cd114c286 irq: Simplify condition
in irq_matrix_reserve()
elapsed time: 723m
configs tested: 111
configs skipped: 2
The following configs have been built
On 3/2/21 05:47, Henry Chen wrote:
> Introduce Mediatek MT6873/MT8183/MT8192 specific provider driver
> using the interconnect framework.
>
> ICC provider ICC Nodes
>
> - |CPU | |--- |VPU |
>
On Wed, 17 Mar 2021 21:39:32 +0100,
Aditya Srivastava wrote:
>
> The opening comment mark '/**' is used for highlighting the beginning of
> kernel-doc comments.
> There are files in sound/pci/ctxfi which follow this syntax in their file
> headers, i.e. start with '/**' like comments, which causes
Hi Henry,
On 3/2/21 05:47, Henry Chen wrote:
> Add dvfsrc driver for MT6873/MT8183/MT8192
>
> Signed-off-by: Henry Chen
> ---
> drivers/soc/mediatek/Kconfig| 11 +
> drivers/soc/mediatek/Makefile | 1 +
> drivers/soc/mediatek/mtk-dvfsrc.c | 421
>
Hi,
some suggestions before diving in a new task.
The following checkpatch issue:
--
WARNING: Unnecessary ftrace-like logging - prefer using ftrace
#559: FILE: drivers/staging/rtl8723bs/core/rtw_ap.c:559:
+ DBG_871X("%s\n", __func__);
simply says to remove the line, due to the existence
From: Christophe Leroy
> Sent: 17 March 2021 17:35
>
> Le 17/03/2021 à 13:51, David Laight a écrit :
> > From: Christophe Leroy
> >> Sent: 16 March 2021 15:41
> > ...
> include/linux/types.h:typedef __kernel_ptrdiff_t ptrdiff_t;
>
> And get:
>
> CC
On 3/18/21 5:03 PM, Dong Aisheng wrote:
> Hi Chanwoo,
>
> On Sat, Mar 13, 2021 at 2:45 PM Dong Aisheng wrote:
>>
>> On Sat, Mar 13, 2021 at 12:09 AM Chanwoo Choi wrote:
>>>
>>> On 21. 3. 12. 오후 7:57, Dong Aisheng wrote:
On Thu, Mar 11, 2021 at 2:54 PM Chanwoo Choi wrote:
>
> On
On Thu, Mar 18, 2021 at 10:24 AM Rahul Tanwar wrote:
>
> Hi Randy,
>
> On 18/3/2021 11:02 am, Randy Dunlap wrote:
> > This email was sent from outside of MaxLinear.
> >
> >
> > Hi,
> >
> > For the leds/blink/Kconfig file at least, something has
> > changed all of the tabs to spaces.
> >
> >
On Fri, Mar 05, 2021 at 04:35:22PM +, Robin Murphy wrote:
> Repeating the rb_entry() boilerplate all over the place gets old fast.
> Before adding yet more instances, add a little hepler to tidy it up.
>
> Signed-off-by: Robin Murphy
> ---
> drivers/iommu/iova.c | 23 ++-
On 3/18/21 4:08 AM, Dan Williams wrote:
> Now that device-dax and filesystem-dax are guaranteed to unmap all user
> mappings of devmap / DAX pages before tearing down the 'struct page'
> array, get_user_pages_fast() can rely on its traditional synchronization
> method "validate_pte(); get_page();
On Thu, Mar 18, 2021 at 08:53:40AM +0800, Lu Baolu wrote:
> When the invalidation queue errors are encountered, dump the information
> logged by the VT-d hardware together with the pending queue invalidation
> descriptors.
>
> Signed-off-by: Ashok Raj
> Tested-by: Guo Kaijie
> Signed-off-by: Lu
[+Lorenzo]
On Tue, Mar 16, 2021 at 12:50:41PM -0600, Tom Saeger wrote:
> In commit 94bccc340710 ("iscsi_ibft: make ISCSI_IBFT dependson ACPI instead
> of ISCSI_IBFT_FIND") Kconfig was disentangled to make ISCSI_IBFT selection
> not depend on x86.
>
> Update arm64 acpi documentation, changing
18.03.2021 12:12, Michał Mirosław пишет:
> On Wed, Mar 17, 2021 at 10:30:01PM +0300, Dmitry Osipenko wrote:
>> The refcounting of the gate clocks has a bug causing the enable_refcnt
>> to underflow when unused clocks are disabled. This happens because clk
>> provider erroneously bumps the refcount
On Thu, Mar 18, 2021 at 8:25 AM Mike Rapoport wrote:
>
> On Wed, Mar 17, 2021 at 09:14:37PM +0100, Rafael J. Wysocki wrote:
> > On Monday, March 15, 2021 5:19:29 PM CET Rafael J. Wysocki wrote:
> > > On Sun, Mar 14, 2021 at 8:00 PM Mike Rapoport wrote:
> > > >
> > > > On Thu, Mar 11, 2021 at
On Wed, Mar 17, 2021 at 09:47:16PM -0400, Richard Guy Briggs wrote:
> The openat2(2) syscall was added in v5.6. Add support for openat2 to the
> audit syscall classifier and for recording openat2 parameters that cannot
> be captured in the syscall parameters of the SYSCALL record.
>
> Supporting
On Wed, Mar 17, 2021 at 10:27 PM Paul Menzel wrote:
>
> Dear Rafael,
>
>
> Am 17.03.21 um 17:49 schrieb Rafael J. Wysocki:
> > From: Rafael J. Wysocki
> >
> > It is reported that on certain platforms unused ACPI power resources
> > that have not been explicitly turned off prevent the platform
Hi Joakim,
On Thu, Mar 18, 2021 at 8:04 AM Joakim Zhang wrote:
> Hi Shawn,
>
> Seems you prefer to 2, is it possible to buildin Realtek
> PHY(CONFIG_REALTEK_PHY=y)? If not, it is going to be tricky.
Yes, we should select the driver as built-in and describe the reset
timing requirements as per
On Thu, Mar 18, 2021 at 02:03:02PM +0300, Kirill A. Shutemov wrote:
> On Thu, Mar 18, 2021 at 11:59:59AM +0100, Miklos Szeredi wrote:
> > [CC linux-mm]
> >
> > On Thu, Mar 18, 2021 at 10:25 AM Luis Henriques wrote:
> > >
> > > (I thought Vlastimil was already on CC...)
> > >
> > > On Mon, Mar
AM64 SoC has a single Octal SPI (OSPI) instance under Flash SubSystem
(FSS). Add DT entry for the same.
Signed-off-by: Vignesh Raghavendra
Reviewed-by: Pratyush Yadav
---
Rebase onto latest k3-dts-next
v1: lore.kernel.org/r/20210309130514.11740-1-vigne...@ti.com
On Thu 18-03-21 12:04:00, Oscar Salvador wrote:
> On Wed, Mar 17, 2021 at 03:05:40PM +0100, Michal Hocko wrote:
> > That being said, bailing out early makes sense to me. But now that
> > you've made me look into the migrate_pages excellent error state reporting
> > I suspect we have a bug here.
Both AM64 EVM and SK have a 512Mb S28HS512T Octal SPI NOR flash.
Add DT node for the same.
Signed-off-by: Vignesh Raghavendra
Reviewed-by: Pratyush Yadav
---
Boot logs:
https://pastebin.ubuntu.com/p/VsMmyWk5SX/
https://pastebin.ubuntu.com/p/KFcMwSGxr5/
Resend:
Rebase onto latest -next
There
Sites that match init_section_contains() get marked as INIT. For
built-in code init_sections contains both __init and __exit text. OTOH
kernel_text_address() only explicitly includes __init text (and there
are no __exit text markers).
Match what jump_label already does and ignore the warning for
The intent is to avoid writing init code after init (because the text
might have been freed). The code is needlessly different between
jump_label and static_call and not obviously correct.
The existing code relies on the fact that the module loader clears the
init layout, such that
It turns out that static_call_set_init() does not preserve the other
flags; IOW. it clears TAIL if it was set.
Fixes: 9183c3f9ed710 ("static_call: Add inline static call infrastructure")
Reported-by: Sumit Garg
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/static_call.c | 17
On 2021-03-18 11:52, Christian Brauner wrote:
> On Thu, Mar 18, 2021 at 11:48:45AM +0100, Christian Brauner wrote:
> > On Wed, Mar 17, 2021 at 09:47:17PM -0400, Richard Guy Briggs wrote:
> > > The openat2(2) syscall was added in kernel v5.6 with commit fddb5d430ad9
> > > ("open: introduce
On Wed, Mar 17, 2021 at 4:38 PM Álvaro Fernández Rojas
wrote:
>
> This is needed for properly registering GPIO regmap as a child of a regmap
> pin controller.
...
> + /* gpiolib will use of_node of the parent if chip->of_node is NULL */
> + chip->of_node =
On Tue, Mar 16, 2021 at 10:38:43PM -0700, Jyoti Bhayana wrote:
> Hi Christian,
>
> Thanks for the detailed explanation. Sounds good to me.
>
Can I get official Reviewed-by or Acked-by please if you are fine with the
change ?
I definitely need one from Jonathan to merge this and one from Jyoti
On 3/17/21 8:54 AM, Xunlei Pang wrote:
> The node list_lock in count_partial() spends long time iterating
> in case of large amount of partial page lists, which can cause
> thunder herd effect to the list_lock contention.
>
> We have HSF RT(High-speed Service Framework Response-Time) monitors,
>
United Nations Human Settlement and Compensation Programme,
Capacity Building and Improving the Performance of Humanitarian self support.
Attention Beneficiary
We wish to notify you about the release of your outstanding payment
which is truly $2.500,000.00 Million Dollars, The United Nation
Hi!
> It has been reported that RGMII is broken in fixed-link, and that is not
> surprising considering the fact that no PHY is attached to the MAC in
> that case, but a switch.
Okay, but there's something wrong in the code.
> This brings us to the topic of the patch: the enetc driver should
On Wed, Mar 17, 2021 at 02:30:47PM -0700, Kees Cook wrote:
> On Wed, Mar 17, 2021 at 04:38:57PM +0100, Greg Kroah-Hartman wrote:
> > On Wed, Mar 17, 2021 at 04:20:52PM +0100, Michal Hocko wrote:
> > > On Wed 17-03-21 15:56:44, Greg KH wrote:
> > > > On Wed, Mar 17, 2021 at 03:44:16PM +0100, Michal
Add 'nxp,imx8mq-vpu-ctrl' in the list of possible syscon.
It will used to access to the VPU control registers.
Signed-off-by: Benjamin Gaignard
---
Documentation/devicetree/bindings/mfd/syscon.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git
The IMX8MQ got two VPUs but until now only G1 has been enabled.
This series aim to add the second VPU (aka G2) and provide basic
HEVC decoding support.
To be able to decode HEVC it is needed to add/update some of the
structures in the uapi. In addition of them one HANTRO dedicated
control is
Introducing G2 hevc video decoder lead to modify the bindings to allow
to get one node per VPUs.
VPUs share one hardware control block which is provided as a phandle on
an syscon.
Each node got now one reg and one interrupt.
Add a compatible for G2 hardware block: nxp,imx8mq-vpu-g2.
To be
Hi Nadav,
> -Original Message-
> From: Nadav Amit [mailto:nadav.a...@gmail.com]
> Sent: Thursday, March 18, 2021 2:13 AM
> To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
>
> Cc: David Woodhouse ; Lu Baolu
> ; Joerg Roedel ; w...@kernel.org;
> alex.william...@redhat.com;
> -Original Message-
> From: Tian, Kevin [mailto:kevin.t...@intel.com]
> Sent: Thursday, March 18, 2021 4:27 PM
> To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
> ; Nadav Amit
> Cc: chenjiashang ; David Woodhouse
> ; io...@lists.linux-foundation.org; LKML
> ;
On 2021-03-17 17:23:39 [+0100], Johan Hovold wrote:
> > > thread(irq_A)
> > > irq_handler(A)
> > > spin_lock(>lock);
> > >
> > > interrupt(irq_B)
> > > irq_handler(B)
> > > spin_lock(>lock);
> >
> > It will not because both threads will wake_up(thread).
>
> Note that the above says
This set is part of a larger effort attempting to clean-up W=1
kernel builds, which are currently overwhelmingly riddled with
niggly little warnings.
This is set 2 out of 2 sets required.
Lee Jones (15):
ata: pata_pdc202xx_old: Fix some incorrectly named functions
ata: pata_sil680: Add some
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_sil680.c:68: warning: Function parameter or member 'adev' not
described in 'sil680_seldev'
drivers/ata/pata_sil680.c:254: warning: Function parameter or member
'try_mmio' not described in 'sil680_init_chip'
Cc: Jens Axboe
Cc:
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_triflex.c:143: warning: expecting prototype for
triflex_dma_start(). Prototype was for triflex_bmdma_start() instead
drivers/ata/pata_triflex.c:159: warning: Function parameter or member 'qc' not
described in
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_it821x.c:346: warning: expecting prototype for
it821x_passthru_dma_start(). Prototype was for it821x_passthru_bmdma_start()
instead
drivers/ata/pata_it821x.c:369: warning: expecting prototype for
it821x_passthru_dma_stop().
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_sis.c:124: warning: Excess function parameter 'deadline'
description in 'sis_133_cable_detect'
drivers/ata/pata_sis.c:529: warning: Function parameter or member 'mask' not
described in 'sis_133_mode_filter'
Cc: Jens Axboe
Cc:
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_via.c:675: warning: Function parameter or member 'pdev' not
described in 'via_reinit_one'
Cc: Jens Axboe
Cc: linux-...@vger.kernel.org
Signed-off-by: Lee Jones
---
drivers/ata/pata_via.c | 2 +-
1 file changed, 1
Fixes the following W=1 kernel build warning(s):
drivers/ata/sata_mv.c:1929: warning: expecting prototype for mv_bmdma_stop().
Prototype was for mv_bmdma_stop_ap() instead
Cc: Jens Axboe
Cc: Mark Lord
Cc: ALWAYS copy
Cc: linux-...@vger.kernel.org
Signed-off-by: Lee Jones
---
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_opti.c:82: warning: Function parameter or member 'val' not
described in 'opti_write_reg'
drivers/ata/pata_opti.c:82: warning: Excess function parameter 'value'
description in 'opti_write_reg'
Cc: Jens Axboe
Cc: Jaromir Koutek
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_pdc202xx_old.c:127: warning: expecting prototype for
pdc202xx_configure_dmamode(). Prototype was for pdc202xx_set_dmamode() instead
drivers/ata/pata_pdc202xx_old.c:228: warning: expecting prototype for
pdc2026x_bmdma_end().
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_cs5530.c:283: warning: Function parameter or member 'pdev'
not described in 'cs5530_init_one'
drivers/ata/pata_cs5530.c:283: warning: Excess function parameter 'dev'
description in 'cs5530_init_one'
Cc: Jens Axboe
Cc:
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_acpi.c:38: warning: Function parameter or member 'link' not
described in 'pacpi_pre_reset'
drivers/ata/pata_acpi.c:38: warning: Excess function parameter 'ap'
description in 'pacpi_pre_reset'
drivers/ata/pata_acpi.c:74:
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_piccolo.c:87: warning: expecting prototype for
ata_tosh_init(). Prototype was for ata_tosh_init_one() instead
Cc: Jens Axboe
Cc: Andre Hedrick
Cc: Hat Inc
Cc: linux-...@vger.kernel.org
Signed-off-by: Lee Jones
---
Fixes the following W=1 kernel build warning(s):
drivers/ata/ata_generic.c:164: warning: expecting prototype for
ata_generic_init(). Prototype was for ata_generic_init_one() instead
Cc: Jens Axboe
Cc: Andre Hedrick
Cc: Hat Inc
Cc: linux-...@vger.kernel.org
Signed-off-by: Lee Jones
---
Fixes the following W=1 kernel build warning(s):
drivers/ata/libata-acpi.c:493: warning: expecting prototype for
ata_acpi_gtm_xfermode(). Prototype was for ata_acpi_gtm_xfermask() instead
drivers/ata/libata-acpi.c:648: warning: Function parameter or member
'prev_gtf' not described in
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_sl82c105.c:191: warning: expecting prototype for
sl82c105_bmdma_end(). Prototype was for sl82c105_bmdma_stop() instead
Cc: Jens Axboe
Cc: linux-...@vger.kernel.org
Signed-off-by: Lee Jones
---
drivers/ata/pata_sl82c105.c | 2
Fixes the following W=1 kernel build warning(s):
drivers/ata/pata_legacy.c:606: warning: expecting prototype for
opt82c465mv_qc_issue(). Prototype was for opti82c46x_qc_issue() instead
drivers/ata/pata_legacy.c:933: warning: Function parameter or member 'probe'
not described in
> From: Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
>
>
> > -Original Message-
> > From: Tian, Kevin [mailto:kevin.t...@intel.com]
> > Sent: Thursday, March 18, 2021 4:27 PM
> > To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
> > ; Nadav Amit
> > Cc:
On 17/03/2021 17:44, Ricardo Ribalda wrote:
> v4l2-compliance -m /dev/media0 -a -f
> Total for uvcvideo device /dev/media0: 8, Succeeded: 6, Failed: 2, Warnings: 0
> Total for uvcvideo device /dev/video0: 54, Succeeded: 50, Failed: 4,
> Warnings: 2
> Total for uvcvideo device /dev/video1: 46,
On Thu, Mar 18, 2021 at 10:14:15AM +0100, Fabio Aiuto wrote:
> Hi,
>
> some suggestions before diving in a new task.
> The following checkpatch issue:
>
> --
> WARNING: Unnecessary ftrace-like logging - prefer using ftrace
> #559: FILE: drivers/staging/rtl8723bs/core/rtw_ap.c:559:
> +
On Tue, Mar 16, 2021 at 08:10:42AM -0700, Yu-cheng Yu wrote:
> When serving a page fault, maybe_mkwrite() makes a PTE writable if it is in
> a writable vma. A shadow stack vma is writable, but its PTEs need
> _PAGE_DIRTY to be set to become writable. For this reason, maybe_mkwrite()
> has been
501 - 600 of 1455 matches
Mail list logo
