|
Direct Pushes for cip-kernel-sec
Hi,
After today's CIP weekly meeting, Pavel proposed the idea of skipping
merge requests for the cip-kernel-sec repository:
17:25 < pave1> wens: I see that currently merges to cip-kernel-sec are
Hi,
After today's CIP weekly meeting, Pavel proposed the idea of skipping
merge requests for the cip-kernel-sec repository:
17:25 < pave1> wens: I see that currently merges to cip-kernel-sec are
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#5639
·
|
|
CIP IRC weekly meeting today
Hi all,
Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.
*Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 starting
Hi all,
Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.
*Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 starting
|
By
masashi.kudo@cybertrust.co.jp <masashi.kudo@...>
·
#5638
·
|
|
Re: [RFC PATCH 4.19.y-cip 38/50] PCI: rcar: Move shareable code to a common file
Hi Pavel,
Thank you for the review.
Hi Pavel,
Thank you for the review.
|
By
Lad Prabhakar
·
#5637
·
|
|
Re: [RFC PATCH 4.19.y-cip 28/50] PCI: endpoint: Add notification for core init completion
Hi Pavel,
Thank you for the review.
Hi Pavel,
Thank you for the review.
|
By
Lad Prabhakar
·
#5636
·
|
|
Re: [RFC PATCH 4.19.y-cip 38/50] PCI: rcar: Move shareable code to a common file
Hi!
Whoa.
So... original patch _moved_ shared code to new place.
This version creates another copy of shared code, probably subtly
different from the other one.
Is that good idea? Won't two copies
Hi!
Whoa.
So... original patch _moved_ shared code to new place.
This version creates another copy of shared code, probably subtly
different from the other one.
Is that good idea? Won't two copies
|
By
Pavel Machek
·
#5635
·
|
|
Re: [RFC PATCH 4.19.y-cip 28/50] PCI: endpoint: Add notification for core init completion
Hi!
Is this used somewhere? This adds symbol but noone calls this, and
AFAICT it is not used in the rest of the series, either.
We can merge it, anyway, I guess, but... explanation would be
Hi!
Is this used somewhere? This adds symbol but noone calls this, and
AFAICT it is not used in the rest of the series, either.
We can merge it, anyway, I guess, but... explanation would be
|
By
Pavel Machek
·
#5634
·
|
|
Re: [RFC PATCH 4.19.y-cip 24/50] PCI: endpoint: Replace spinlock with mutex
Hi!
Okay, we can't really protect sleeping code with a mutex.
But this one is not sleeping. It is mdelay(), not msleep().
And same here.
If there's a place which does sleep with the spinlock held,
Hi!
Okay, we can't really protect sleeping code with a mutex.
But this one is not sleeping. It is mdelay(), not msleep().
And same here.
If there's a place which does sleep with the spinlock held,
|
By
Pavel Machek
·
#5633
·
|
|
Re: Request for Camera CSI support for IMX
Hello Jan,
Thanks for the details. This gives us an idea on what we could do next.
Thanks for your immediate support. We will get in touch with NXP for this.
Regards,
Lakshmi
CONFIDENTIALITY
This
Hello Jan,
Thanks for the details. This gives us an idea on what we could do next.
Thanks for your immediate support. We will get in touch with NXP for this.
Regards,
Lakshmi
CONFIDENTIALITY
This
|
By
Lakshmi Natarajan <lakshmi.natarajan@...>
·
#5632
·
|
|
Re: Request for Camera CSI support for IMX
Hi Lakshmi,
That's unfortunate.
Yes, please reach out to NXP and ask what their answer for upstream is, today or at least for the future. It's their issue in the first place. Also for that, you
Hi Lakshmi,
That's unfortunate.
Yes, please reach out to NXP and ask what their answer for upstream is, today or at least for the future. It's their issue in the first place. Also for that, you
|
By
Jan Kiszka
·
#5631
·
|
|
Re: Request for Camera CSI support for IMX
Hello Jan,
This is regarding requests for CSI support in the IMX processor.
We were using Yocto + NXP provided kernel to use the CSI peripheral of the IMX6 processor. We have complete support from NXP
Hello Jan,
This is regarding requests for CSI support in the IMX processor.
We were using Yocto + NXP provided kernel to use the CSI peripheral of the IMX6 processor. We have complete support from NXP
|
By
Lakshmi Natarajan <lakshmi.natarajan@...>
·
#5630
·
|
|
Re: If you are using PCIe EP, speak up was Re: [RFC PATCH 4.19.y-cip 00/50] Add PCIe EP support for Renesas R-Car Gen3 and RZ/G2x
Hi Pavel,
By
Lad Prabhakar
·
#5629
·
|
|
Re: [RFC PATCH 4.19.y-cip 24/50] PCI: endpoint: Replace spinlock with mutex
Hi Pavel,
By
Lad Prabhakar
·
#5628
·
|
|
Re: [PATCH 4.19.y-cip 00/26] Fixes and extension to PCIe EPF
Hi Pavel,
By
Lad Prabhakar
·
#5627
·
|
|
Re: If you are using PCIe EP, speak up was Re: [RFC PATCH 4.19.y-cip 00/50] Add PCIe EP support for Renesas R-Car Gen3 and RZ/G2x
Hi!
Well... I applied this batch. If someone can explain the mutex
vs. spinlock thing, then I guess we can do next batch up to 35...
OTOH I did not go through those patches in detail, and RFC is
Hi!
Well... I applied this batch. If someone can explain the mutex
vs. spinlock thing, then I guess we can do next batch up to 35...
OTOH I did not go through those patches in detail, and RFC is
|
By
Pavel Machek
·
#5626
·
|
|
Re: [RFC PATCH 4.19.y-cip 24/50] PCI: endpoint: Replace spinlock with mutex
Hi!
Could I get some kind of explanation why this is good idea?
As long as code protected by the locks does not sleep, spinlocks are
okay... (but they should not need "_irqsave" variants).
They are
Hi!
Could I get some kind of explanation why this is good idea?
As long as code protected by the locks does not sleep, spinlocks are
okay... (but they should not need "_irqsave" variants).
They are
|
By
Pavel Machek
·
#5625
·
|
|
Re: [PATCH 4.19.y-cip 00/26] Fixes and extension to PCIe EPF
Hi!
Thanks, applied and pushed out.
Our automated testing did not find anything wrong (but I don't think
that means much).
Best regards,
Pavel
--
DENX Software Engineering GmbH,
Hi!
Thanks, applied and pushed out.
Our automated testing did not find anything wrong (but I don't think
that means much).
Best regards,
Pavel
--
DENX Software Engineering GmbH,
|
By
Pavel Machek
·
#5624
·
|
|
[PATCH 4.19.y-cip 26/26] tools: PCI: Fix fd leakage
From: Hewenliang <hewenliang4@...>
commit 3c379a59b4795d7279d38c623e74b9790345a32b upstream.
We should close fd before the return of run_test.
Fixes: 3f2ed8134834 ("tools: PCI: Add a
From: Hewenliang <hewenliang4@...>
commit 3c379a59b4795d7279d38c623e74b9790345a32b upstream.
We should close fd before the return of run_test.
Fixes: 3f2ed8134834 ("tools: PCI: Add a
|
By
Lad Prabhakar
·
#5623
·
|
|
[PATCH 4.19.y-cip 25/26] tools: PCI: Exit with error code when test fails
From: Jean-Jacques Hiblot <jjhiblot@...>
commit b71f0a0b1e3fea212a6a5042ced8b48a81738ac9 upstream.
This makes it easier to use pcitest in automated setups.
Signed-off-by: Jean-Jacques Hiblot
From: Jean-Jacques Hiblot <jjhiblot@...>
commit b71f0a0b1e3fea212a6a5042ced8b48a81738ac9 upstream.
This makes it easier to use pcitest in automated setups.
Signed-off-by: Jean-Jacques Hiblot
|
By
Lad Prabhakar
·
#5622
·
|
|
[PATCH 4.19.y-cip 24/26] PCI: dwc: Fix dw_pcie_ep_raise_msix_irq() to get correct MSI-X table address
From: Kishon Vijay Abraham I <kishon@...>
commit 6f5e193bfb55963ce5f4f68cc927f371ddb0913b upstream.
commit beb4641a787d ("PCI: dwc: Add MSI-X callbacks handler"),
in order to raise MSI-X
From: Kishon Vijay Abraham I <kishon@...>
commit 6f5e193bfb55963ce5f4f68cc927f371ddb0913b upstream.
commit beb4641a787d ("PCI: dwc: Add MSI-X callbacks handler"),
in order to raise MSI-X
|
By
Lad Prabhakar
·
#5621
·
|
|
[PATCH 4.19.y-cip 23/26] PCI: endpoint: Fix clearing start entry in configfs
From: Kunihiko Hayashi <hayashi.kunihiko@...>
commit f58d5f53c89479c12ad719c1960176442add5aaa upstream.
After an endpoint is started through configfs, if 0 is written to the
configfs entry
From: Kunihiko Hayashi <hayashi.kunihiko@...>
commit f58d5f53c89479c12ad719c1960176442add5aaa upstream.
After an endpoint is started through configfs, if 0 is written to the
configfs entry
|
By
Lad Prabhakar
·
#5620
·
|