Use only one and exactly one space around '=' in DTS example.
Signed-off-by: Krzysztof Kozlowski
---
Merging idea: Rob's DT.
Should apply cleanly on Rob's for-next.
---
.../devicetree/bindings/auxdisplay/hit,hd44780.yaml | 2 +-
.../devicetree/bindings/clock/baikal,bt1-ccu-pll.yaml |
On Fri, Nov 24, 2023 at 10:21:21AM +0100, Krzysztof Kozlowski wrote:
> Use only one and exactly one space around '=' in DTS example.
>
> Signed-off-by: Krzysztof Kozlowski
>
> ---
>
> Merging idea: Rob's DT.
> Should apply cleanly on Rob's for-next.
> ---
> .../devicetree/bindings/auxdisplay/h
On Fri Nov 24, 2023 at 7:38 AM CET, Vikash Garodia wrote:
>
> On 11/22/2023 7:50 PM, Luca Weiss wrote:
> > On Wed Nov 22, 2023 at 2:17 PM CET, Vikash Garodia wrote:
> >>
> >> On 10/2/2023 7:50 PM, Luca Weiss wrote:
> >>> If the video-firmware node is present, the venus driver assumes we're on
> >>>
On 11/24/2023 5:05 PM, Luca Weiss wrote:
> On Fri Nov 24, 2023 at 7:38 AM CET, Vikash Garodia wrote:
>>
>> On 11/22/2023 7:50 PM, Luca Weiss wrote:
>>> On Wed Nov 22, 2023 at 2:17 PM CET, Vikash Garodia wrote:
On 10/2/2023 7:50 PM, Luca Weiss wrote:
> If the video-firmware node is pre
On Fri, 24 Nov 2023 at 14:30, Vikash Garodia wrote:
>
> On 11/24/2023 5:05 PM, Luca Weiss wrote:
> > On Fri Nov 24, 2023 at 7:38 AM CET, Vikash Garodia wrote:
> >>
> >> On 11/22/2023 7:50 PM, Luca Weiss wrote:
> >>> On Wed Nov 22, 2023 at 2:17 PM CET, Vikash Garodia wrote:
>
> On 10/2/20
+Cc workflows
On 11/24/23 12:43, Greg Kroah-Hartman wrote:
> On Thu, Nov 23, 2023 at 07:20:46PM +0100, Oleksandr Natalenko wrote:
>> Hello.
>>
>> Since v6.6.2 kernel release I'm experiencing a regression with regard
>> to USB ports behaviour after a suspend/resume cycle.
>>
>> If a USB port is e
On Fri, Nov 24, 2023 at 01:59:24PM +0100, Vlastimil Babka wrote:
> +Cc workflows
>
> On 11/24/23 12:43, Greg Kroah-Hartman wrote:
> > On Thu, Nov 23, 2023 at 07:20:46PM +0100, Oleksandr Natalenko wrote:
> >> Hello.
> >>
> >> Since v6.6.2 kernel release I'm experiencing a regression with regard
>
On 11/24/2023 6:23 PM, Dmitry Baryshkov wrote:
> On Fri, 24 Nov 2023 at 14:30, Vikash Garodia
> wrote:
>>
>> On 11/24/2023 5:05 PM, Luca Weiss wrote:
>>> On Fri Nov 24, 2023 at 7:38 AM CET, Vikash Garodia wrote:
On 11/22/2023 7:50 PM, Luca Weiss wrote:
> On Wed Nov 22, 2023 at 2:
There are two typos in this dtsi, so fix it.
classis -> chassis.
8070 -> 8060
Signed-off-by: Jianhua Lu
---
arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-common.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-co
ufs node isn't in a right place, 'f' is front of 's', so move it to
above usb node.
Signed-off-by: Jianhua Lu
---
.../dts/qcom/sm8250-xiaomi-elish-common.dtsi | 32 +--
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-c
Add type-c node to feature otg function.
Signed-off-by: Jianhua Lu
---
.../dts/qcom/sm8250-xiaomi-elish-common.dtsi | 36 +++
1 file changed, 36 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-common.dtsi
b/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-c
Hi Masami,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.7-rc2 next-20231124]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--bas
On 24/11/2023 14:57, Jianhua Lu wrote:
> ufs node isn't in a right place, 'f' is front of 's', so move it to
> above usb node.
Please not.
If we change the order to match DTSI, then this patch would be wrong.
Best regards,
Krzysztof
On Fri Nov 24, 2023 at 2:35 PM CET, Vikash Garodia wrote:
>
>
> On 11/24/2023 6:23 PM, Dmitry Baryshkov wrote:
> > On Fri, 24 Nov 2023 at 14:30, Vikash Garodia
> > wrote:
> >>
> >> On 11/24/2023 5:05 PM, Luca Weiss wrote:
> >>> On Fri Nov 24, 2023 at 7:38 AM CET, Vikash Garodia wrote:
>
> >>
On Wed, Nov 22, 2023 at 10:36:23AM -0300, Luis Claudio R. Goncalves wrote:
> On Tue, Nov 21, 2023 at 10:01:25PM -0300, Luis Claudio R. Goncalves wrote:
> > Hello RT-list!
> >
> > I'm pleased to announce the 5.10.201-rt98 stable release.
> >
> > This release is just an update to the new stable 5.1
q6v5 fatal and watchdog IRQ handlers always retrieves the crash reason
information from SMEM global partition (QCOM_SMEM_HOST_ANY).
For some targets like IPQ9574 and IPQ5332, crash reason information is
present in target specific partition due to which the crash reason is
not printed in the curren
On 9/4/2023 10:23 PM, Vignesh Viswanathan wrote:
On 7/16/2023 1:50 AM, Bjorn Andersson wrote:
On Wed, May 03, 2023 at 11:51:46AM +0530, Vignesh Viswanathan wrote:
Currently the SSR subdevice notifies the client driver on crash of the
rproc from the recovery workqueue using the BEFORE_SHUTD
On 19.11.23 17:56, Alexandru Elisei wrote:
Introduce arch_prep_new_page(), which will be used by arm64 to reserve tag
storage for an allocated page. Reserving tag storage can fail, for example,
if the tag storage page has a short pin on it, so allow prep_new_page() ->
arch_prep_new_page() to simi
On 19.11.23 17:57, Alexandru Elisei wrote:
Add arch_free_pages_prepare() hook that is called before that page flags
are cleared. This will be used by arm64 when explicit management of tag
storage pages is enabled.
Can you elaborate a bit what exactly will be done by that code with that
informa
On 19.11.23 17:57, Alexandru Elisei wrote:
Add the MTE tag storage pages to the MIGRATE_CMA migratetype, which allows
the page allocator to manage them like regular pages.
Ths migratype lends the pages some very desirable properties:
* They cannot be longterm pinned, meaning they will always be
On 19.11.23 17:57, Alexandru Elisei wrote:
Tag storage memory requires that the tag storage pages used for data are
always migratable when they need to be repurposed to store tags.
If ARCH_KEEP_MEMBLOCK is enabled, kexec will scan all non-reserved
memblocks to find a suitable location for copyin
On 19.11.23 17:57, Alexandru Elisei wrote:
To be able to reserve the tag storage associated with a page requires that
the tag storage page can be migrated.
When HW KASAN is enabled, the kernel allocates pages, which are now tagged,
in non-preemptible contexts, which can make reserving the associ
On 19.11.23 17:57, Alexandru Elisei wrote:
alloc_contig_range() requires that the requested pages are in the same
zone. Check that this is indeed the case before initializing the tag
storage blocks.
Signed-off-by: Alexandru Elisei
---
arch/arm64/kernel/mte_tag_storage.c | 33 +
ls to reproduce are available at:
https://download.01.org/0day-ci/archive/20231124/202311241731.d1159c9f-oliver.s...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
On Fri, Nov 24, 2023 at 04:54:20PM +0100, Krzysztof Kozlowski wrote:
> On 24/11/2023 14:57, Jianhua Lu wrote:
> > ufs node isn't in a right place, 'f' is front of 's', so move it to
> > above usb node.
>
> Please not.
>
> If we change the order to match DTSI, then this patch would be wrong.
>
Ac
There are two typos in this dtsi, so fix it.
classis -> chassis.
8070 -> 8060
Signed-off-by: Jianhua Lu
---
No changes in v2.
arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-common.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/sm8
Add type-c node to feature otg function.
Signed-off-by: Jianhua Lu
---
No changes in v2.
.../dts/qcom/sm8250-xiaomi-elish-common.dtsi | 36 +++
1 file changed, 36 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-common.dtsi
b/arch/arm64/boot/dts/qcom/sm
Change dr_mode to otg and set usb_role_swith property to enable
usb otg.
Signed-off-by: Jianhua Lu
---
Changes in v2:
1. a new patch that I missed to generate.
arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-common.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/a
28 matches
Mail list logo
