-pcie-ctrl']
from schema $id: http://devicetree.org/schemas/mfd/syscon.yaml#
Signed-off-by: Luca Weiss
---
arch/arm/boot/dts/qcom/qcom-msm8974.dtsi | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/qcom/qcom-msm8974.dtsi
b/arch/arm/boot/dts/qcom
Add compatible for the Qualcomm MSM8974 APCS block.
Signed-off-by: Luca Weiss
---
Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git
a/Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.yaml
b/Documentation
Finally fix a warning about the apcs-global syscon used on msm8974 that
has been around forever.
Signed-off-by: Luca Weiss
---
Luca Weiss (2):
dt-bindings: mailbox: qcom: Add MSM8974 APCS compatible
ARM: dts: qcom: msm8974: Use proper compatible for APCS syscon
.../devicetree
On Montag, 8. April 2024 19:26:49 CEST Konrad Dybcio wrote:
>
> On 4/8/24 18:39, Luca Weiss wrote:
> > Allow specifying a GPIO hog, as already used on
> > qcom-msm8974-lge-nexus5-hammerhead.dts.
> >
> > Signed-off-by: Luca Weiss
> > ---
> > .../devic
Follow the gpio-hog bindings and use otg-hog as node name.
Signed-off-by: Luca Weiss
---
arch/arm/boot/dts/qcom/qcom-msm8974-lge-nexus5-hammerhead.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/qcom/qcom-msm8974-lge-nexus5-hammerhead.dts
b/arch/arm
Resolve the dt validation failure on Nexus 5.
Signed-off-by: Luca Weiss
---
Luca Weiss (2):
dt-bindings: pinctrl: qcom,pmic-gpio: Allow gpio-hog nodes
ARM: dts: qcom: msm8974-hammerhead: Update gpio hog node name
.../devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml | 12
Allow specifying a GPIO hog, as already used on
qcom-msm8974-lge-nexus5-hammerhead.dts.
Signed-off-by: Luca Weiss
---
.../devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml | 12
1 file changed, 12 insertions(+)
diff --git a/Documentation/devicetree/bindings/pinctrl/qcom
bus ("inv_mpu_i2c_aux_bus"). Since
the driver is also based on "default: return true" this should scale
better into the future.
Signed-off-by: Luca Weiss
---
This fixes dt validation error on qcom-msm8974-lge-nexus5-hammerhead
which uses mpu6515
arch/arm/boot/dts/qcom/qco
Public bug reported:
Environment: Thunderbird 124.0 64bits installed as SNAP on Ubuntu 22.04 LTS
3 gmail imap account
This (monday) morning Ubuntu notify me that I was running out of disk
space, and while I was checking where the problem was, the disk analyzer
told me the answer
Public bug reported:
Environment: Thunderbird 124.0 64bits installed as SNAP on Ubuntu 22.04 LTS
3 gmail imap account
This (monday) morning Ubuntu notify me that I was running out of disk
space, and while I was checking where the problem was, the disk analyzer
told me the answer
Branch: refs/changes/01/557001/meta
Home: https://github.com/jenkinsci/gerrit-code-review-plugin
Commit: 5a001659e1ed2469f9b8d06368dc7dd4a337802d
https://github.com/jenkinsci/gerrit-code-review-plugin/commit/5a001659e1ed2469f9b8d06368dc7dd4a337802d
Author: Gerrit User 1021713
Set the 'items' correctly for the qcom,halt-regs property and update the
description to match what it should be.
Signed-off-by: Luca Weiss
---
.../devicetree/bindings/remoteproc/qcom,sdm845-adsp-pil.yaml| 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
Set the 'items' correctly for the qcom,halt-regs property and update the
description to match what it should be.
Signed-off-by: Luca Weiss
---
.../devicetree/bindings/remoteproc/qcom,sc7280-wpss-pil.yaml| 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
Set the 'items' correctly for the qcom,halt-regs property and update the
description to match what it should be.
Signed-off-by: Luca Weiss
---
.../devicetree/bindings/remoteproc/qcom,qcs404-cdsp-pil.yaml| 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
to validate qcom,halt-regs in the
schemas I'm touching.
Signed-off-by: Luca Weiss
---
Luca Weiss (3):
dt-bindings: remoteproc: qcom,qcs404-cdsp-pil: Fix qcom,halt-regs
definition
dt-bindings: remoteproc: qcom,sc7280-wpss-pil: Fix qcom,halt-regs
definition
dt-bindings: remoteproc: qcom
Ciao a tutti,
Oggi pomeriggio Domenica alle 16 Richard Stallman sarà ospite presso l' aula
magna dell' università di Reggio Emilia.
"Le basi della società nell' era digitale"
Aula Magna Manodori, Palazzo Dossetti, via Allegri 9, Reggio Emilia.
Per info Francesco Reyes, DSV,
On Samstag, 6. April 2024 18:45:21 CEST Jonathan Cameron wrote:
> On Sat, 06 Apr 2024 17:31:04 +0200
> Luca Weiss wrote:
>
> > For example the BMP280 barometric pressure sensor on Qualcomm
> > MSM8974-based Nexus 5 smartphone exposes such file in sysfs.
> > Docum
Enable the vibrator connected to PM8941 found on the Sony shinano
platform.
Signed-off-by: Luca Weiss
---
.../arm/boot/dts/qcom/qcom-msm8974pro-sony-xperia-shinano-common.dtsi | 4
1 file changed, 4 insertions(+)
diff --git
a/arch/arm/boot/dts/qcom/qcom-msm8974pro-sony-xperia-shinano
For example the BMP280 barometric pressure sensor on Qualcomm
MSM8974-based Nexus 5 smartphone exposes such file in sysfs.
Document it.
Signed-off-by: Luca Weiss
---
Documentation/ABI/testing/sysfs-bus-iio | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/ABI
On Fri, 5 Apr 2024 at 16:18, Colin Watson wrote:
>
> On Fri, Apr 05, 2024 at 03:19:23PM +0100, Simon McVittie wrote:
> > I find that having the upstream source code in git (in the same form that
> > we use for the .orig.tar.*, so including Autotools noise, etc. if present,
> > but excluding any
On Fri, 5 Apr 2024 at 11:18, Andreas Tille wrote:
>
> Am Thu, Apr 04, 2024 at 02:41:00PM +0100 schrieb Luca Boccassi:
> > > Please don't get me wrong: I do not consider Fedora a commercial
> > > entity. I simply subscribe the statement that we are facing some
> >
On Thu, 4 Apr 2024 at 21:30, Salvo Tomaselli wrote:
>
> > In practical terms, it would probably be made easier if it was
> > mandatory for all packages to be on Salsa, either in the 'debian'
> > namespace or in a team namespace (but not under individual users).
>
> Realistically, even if you
On Fri, 22 Mar 2024 18:13:35 + Luca Boccassi
wrote:
> On Mon, 4 Mar 2024 at 23:58, Luca Boccassi wrote:
> >
> > On Mon, 4 Mar 2024 at 23:28, Steve McIntyre
wrote:
> >
> > > Modulo those questions, let's talk infrastructure. Off the top of
my
>
On Fri, 22 Mar 2024 18:13:35 + Luca Boccassi
wrote:
> On Mon, 4 Mar 2024 at 23:58, Luca Boccassi wrote:
> >
> > On Mon, 4 Mar 2024 at 23:28, Steve McIntyre
wrote:
> >
> > > Modulo those questions, let's talk infrastructure. Off the top of
my
>
: Jani Nikula
Cc: James Ausmus
Cc: Ville Syrjälä
Signed-off-by: Luca Coelho
---
In v5:
* fixed Ville's name's wrong charset, which prevented patchwork
from picking this up.
In v4:
* actually go back to unrestricting only for > 20. I sent the
wrong patch version in v3.
In
On Thu, 4 Apr 2024 at 13:40, Andreas Tille wrote:
>
> Hi Luca,
>
> Am Thu, Apr 04, 2024 at 12:47:11PM +0100 schrieb Luca Boccassi:
> > > > That's the price we currently pay for being not a commercial entity,
> > >
> > > I fully subscribe to this s
On Thu, 4 Apr 2024 at 11:39, Andreas Tille wrote:
>
> Hi Marc,
>
> Am Wed, Apr 03, 2024 at 05:53:46PM +0200 schrieb Marc Haber:
> > On Wed, Apr 03, 2024 at 10:37:37AM +0200, Andreas Tille wrote:
> > "we now use Wayland
> > instead of X11", "please don't create your system users with adduser and
>
We only need DMC wakelocks when we allow DC5 and DC6 states. Add the
calls to enable and disable DMC wakelock accordingly.
Signed-off-by: Luca Coelho
---
drivers/gpu/drm/i915/display/intel_display_power_well.c | 7 +++
drivers/gpu/drm/i915/display/intel_dmc.c| 4
2
This feature should be disabled by default until properly tested and
mature. Add a module parameter to enable the feature for testing,
while keeping it disabled by default for now.
Reviewed-by: Uma Shankar
Signed-off-by: Luca Coelho
---
drivers/gpu/drm/i915/display/intel_display_params.c | 5
Only allow running DMC wakelock code if the display version is 20 or
greater. Also check if DMC is loaded before enabling.
Signed-off-by: Luca Coelho
---
.../drm/i915/display/intel_display_driver.c | 1 +
drivers/gpu/drm/i915/display/intel_dmc_wl.c | 26 +++
2 files
ver needs to access memory which lies inside pre-defined
ranges, it will tell DMC to set the wakelock, access the memory, then
wait for a while and clear the wakelock.
The wakelock state is protected in the driver with spinlocks to
prevent concurrency issues.
BSpec: 71583
Signed-off-by: Luca Coe
:
https://patchwork.freedesktop.org/series/128628/
Please review.
Cheers,
Luca.
Luca Coelho (4):
drm/i915/display: add support for DMC wakelocks
drm/i915/display: don't allow DMC wakelock on older hardware
drm/i915/display: add module parameter to enable DMC wakelock
drm/i915/display: tie
; ville.syrj...@linux.intel.com; Nikula, Jani
> > Subject: [PATCH v3 4/4] drm/i915/display: tie DMC wakelock to DC5/6 state
> > transitions
> >
> > We only need DMC wakelocks when we allow DC5 and DC6 states. Add the calls
> > to enable and disable DMC wakelock accordi
able the feature for testing, while keeping it
> > disabled by
> > default for now.
> >
> > Signed-off-by: Luca Coelho
> > ---
> > drivers/gpu/drm/i915/display/intel_display_params.c | 5 +
> > drivers/gpu/drm/i915/display/intel_display_params.h | 1 +
> On 22 Mar 2024, at 10:30, Michal Orzel wrote:
>
> Hi Luca,
>
> On 12/03/2024 14:03, Luca Fancellu wrote:
>>
>>
>> Currently the memory footprint of the static shared memory feature
>> is impacting all the struct meminfo instances with memor
o intel_dmc_wl_init unconditionally but protect
> it with
> Platform check.
Good point. I have removed the call to intel_dmc_wl_init() completely
from the previous patch, like with intel_dmc_wl_enable(), so the call
to init will be in this patch and protected by the platform version as
> On 19 Mar 2024, at 14:58, Michal Orzel wrote:
>
> Hi Luca,
>
> On 12/03/2024 14:03, Luca Fancellu wrote:
>>
>>
>> The user of shm_mem member of the 'struct kernel_info' is only
>> the code managing the static shared memory feature, which can be
>
Hi folks!
I have just upgraded Jenkins to 2.452, everything seems to work fine
but please let me know if you see anything out of the ordinary. The
upgrade was due to some security issues, and I also took the chance to
upgrade some plugins for the same reason.
Luca
Luca Canali created SPARK-47728:
---
Summary: Document G1 Concurrent GC metrics
Key: SPARK-47728
URL: https://issues.apache.org/jira/browse/SPARK-47728
Project: Spark
Issue Type: Documentation
Luca Canali created SPARK-47726:
---
Summary: Document push-based shuffle metrics
Key: SPARK-47726
URL: https://issues.apache.org/jira/browse/SPARK-47726
Project: Spark
Issue Type: Documentation
Hello Rob,
[+Cc Wolfram for the I2C discussion below]
thanks for your feedback.
On Wed, 27 Mar 2024 11:09:08 -0500
Rob Herring wrote:
> On Tue, Mar 26, 2024 at 05:28:11PM +0100, Luca Ceresoli wrote:
> > Add bindings for a physical, hot-pluggable connector allowing the far end
>
Public bug reported:
When using sshd's -i option with stdio that is not a AF_INET/AF_INET6
socket, auth_get_canonical_hostname() returns "UNKNOWN" which is then
set as the value of PAM_RHOST, causing pam to try to do a reverse DNS
query of "UNKNOWN", which times out multiple times, causing a
Public bug reported:
When using sshd's -i option with stdio that is not a AF_INET/AF_INET6
socket, auth_get_canonical_hostname() returns "UNKNOWN" which is then
set as the value of PAM_RHOST, causing pam to try to do a reverse DNS
query of "UNKNOWN", which times out multiple times, causing a
of world languages.
I am thus inviting anyone with tips/or resources available to contribute to
this compiling effort. Contributors would receive the due acknowledgments,
and could specify under which conditions they want their data to be used.
You can reply here or write to lu...@uio.no .
Best,
Luca
https://bugs.kde.org/show_bug.cgi?id=478157
Luca Moscato changed:
What|Removed |Added
CC||luca.mosc...@gmail.com
--- Comment #1 from Luca
: Jani Nikula
Cc: James Ausmus
Cc: Ville Syrj�l�
Signed-off-by: Luca Coelho
---
In v4:
* actually go back to unrestricting only for > 20. I sent the
wrong patch version in v3.
In v3:
* go back to unrestricing only for > 20, since the change for
versions 14 to 20 should be
parameter will drain quickly the computer memory, especially with big
dataset, for this reason, these are not saved. However, you can recover it via
the sampled coefficients.
I hope this may help and if you have any other questions or doubts, do not
hesitate to ask!
Best regards,
Luca
Da: Brian
On Tue, 2 Apr 2024 at 16:52, Bastian Blank wrote:
>
> On Tue, Apr 02, 2024 at 03:59:25PM +0100, Luca Boccassi wrote:
> > Let's look at this the other way around: if there was no dependency, in
> > what scenario would things break and how?
>
> - linux-headers-bla and linux
On Tue, 2 Apr 2024 at 16:52, Bastian Blank wrote:
>
> On Tue, Apr 02, 2024 at 03:59:25PM +0100, Luca Boccassi wrote:
> > Let's look at this the other way around: if there was no dependency, in
> > what scenario would things break and how?
>
> - linux-headers-bla and linux
On Tue, 2 Apr 2024 08:27:39 +0200 Bastian Blank
wrote:
> On Mon, Apr 01, 2024 at 09:25:40PM +0000, Luca Boccassi wrote:
> > Why do dkms modules need the image installed to be built? At the
very
> > least they didn't use to, the headers were enough last time I had
to
> >
On Tue, 2 Apr 2024 08:27:39 +0200 Bastian Blank
wrote:
> On Mon, Apr 01, 2024 at 09:25:40PM +0000, Luca Boccassi wrote:
> > Why do dkms modules need the image installed to be built? At the
very
> > least they didn't use to, the headers were enough last time I had
to
> >
> Hi Zbigniew!
>
> On Tue, Apr 2, 2024 at 1:15 PM Zbigniew Jędrzejewski-Szmek <
> zbyszek(a)in.waw.pl wrote:
>
>
> Thanks. In the period between the proposal was written and published the
> TPM2 provider has landed in Fedora.
> PKCS#11 provider is already here for a while.
The fact that such
On Mon, 1 Apr 2024 at 21:49, Bastian Blank wrote:
>
> Control: tags -1 wontfix
>
> On Thu, Feb 29, 2024 at 01:38:12PM +0100, Bastian Blank wrote:
> > On Thu, Feb 29, 2024 at 12:12:21PM +, Luca Boccassi wrote:
> > > With the new vmlinux.h shipped in the he
On Mon, 1 Apr 2024 at 21:49, Bastian Blank wrote:
>
> Control: tags -1 wontfix
>
> On Thu, Feb 29, 2024 at 01:38:12PM +0100, Bastian Blank wrote:
> > On Thu, Feb 29, 2024 at 12:12:21PM +, Luca Boccassi wrote:
> > > With the new vmlinux.h shipped in the he
t; or Suggests: given that most installations won't actually need the
image
> package?
MR to downgrade to recommends:
https://salsa.debian.org/kernel-team/linux/-/merge_requests/1054
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
t; or Suggests: given that most installations won't actually need the
image
> package?
MR to downgrade to recommends:
https://salsa.debian.org/kernel-team/linux/-/merge_requests/1054
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
Control: tag -1 pending
Hello,
Bug #1063976 in javaproperties reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
On Sat, 30 Mar 2024 at 15:44, Russ Allbery wrote:
>
> Luca Boccassi writes:
>
> > In the end, massaged tarballs were needed to avoid rerunning autoconfery
> > on twelve thousands different proprietary and non-proprietary Unix
> > variants, back in the day. In 2024, we
On Sun, 31 Mar 2024 at 08:39, Bastian Blank wrote:
>
> On Sun, Mar 31, 2024 at 12:05:54PM +0500, Andrey Rakhmatullin wrote:
> > On Sat, Mar 30, 2024 at 11:22:33PM -0300, Santiago Ruano Rincón wrote:
> > > As others have said, the best solution is to relay on HSW for handling
> > > the
r this function would probably be
of_graph_get_next_port_endpoint() I guess, to clearly differentiate from
of_graph_get_next_device_endpoint().
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
+1 Thanks
Luca
- Original Message -
> From: "Ben Weidig"
> To: "Tapestry development"
> Sent: Saturday, 30 March, 2024 2:57:05 PM
> Subject: Re: [VOTE] Tapestry 5.8.5
>
> Ben Weidig: +1 (binding)
>
> Ran it against our test suite, l
On Sat, 30 Mar 2024 at 06:29, Russ Allbery wrote:
>
> Antonio Russo writes:
>
> > The way I see it, there are two options in handling a buildable package:
>
> > 1. That file would have been considered a build artifact, consequently
> > removed and then regenerated. No backdoor.
>
> > 2. The
On Sat, 30 Mar 2024 at 09:57, Iustin Pop wrote:
>
> On 2024-03-30 08:02:04, Gioele Barabucci wrote:
> > Now it is time to take a step forward:
> >
> > 1. new upstream release;
> > 2. the DD/DM merges the upstream release VCS into the Debian VCS;
> > 3. the buildd is notified of the new release;
>
No, that's about publishing a new service, not calling into others.
It's probably due to dbus-broker supporting SO_PEERSEC to acquire credentials.
On Fri, 29 Mar 2024 at 21:14, Mantas Mikulėnas wrote:
>
> I don't know, but it might be related to this note:
>
the phone with at least some amount of power.
Signed-off-by: Luca Weiss
---
arch/arm64/boot/dts/qcom/sm6350.dtsi | 47 ++
arch/arm64/boot/dts/qcom/sm7225-fairphone-fp4.dts | 60 ++-
2 files changed, 106 insertions(+), 1 deletion(-)
diff --git a/arch
Type-C port management functionality lives inside of the PMIC block on
pm7250b.
The Type-C port management logic controls orientation detection,
vbus/vconn sense and to send/receive Type-C Power Domain messages.
Reviewed-by: Bryan O'Donoghue
Reviewed-by: Konrad Dybcio
Signed-off-by: Luca Weiss
Add the required DTS node for the USB VBUS output regulator, which is
available on PM7250B. This will provide the VBUS source to connected
peripherals.
Reviewed-by: Bryan O'Donoghue
Signed-off-by: Luca Weiss
---
arch/arm64/boot/dts/qcom/pm7250b.dtsi | 6 ++
1 file changed, 6 insertions
Kozlowski
To: Conor Dooley
Cc: ~postmarketos/upstream...@lists.sr.ht
Cc: phone-de...@vger.kernel.org
Cc: linux-arm-...@vger.kernel.org
Cc: devicet...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Luca Weiss
Changes in v2:
- Move disabled as last property for pm7250b_vbus
Add the compatible string for the DisplayPort controller on SM6350 which
is compatible with the one on SM8350.
Acked-by: Rob Herring
Signed-off-by: Luca Weiss
---
Documentation/devicetree/bindings/display/msm/dp-controller.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation
Document the displayport controller subnode of the SM6350 MDSS.
Signed-off-by: Luca Weiss
---
.../devicetree/bindings/display/msm/qcom,sm6350-mdss.yaml| 9 +
1 file changed, 9 insertions(+)
diff --git
a/Documentation/devicetree/bindings/display/msm/qcom,sm6350-mdss.yaml
b
Add the node for the DisplayPort controller found on the SM6350 SoC.
Reviewed-by: Dmitry Baryshkov
Signed-off-by: Luca Weiss
---
arch/arm64/boot/dts/qcom/sm6350.dtsi | 88
1 file changed, 88 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sm6350.dtsi
Add the required changes to support DisplayPort (normally(?) available
via the USB-C connector) on the SM6350/SM7225 SoC.
This has been tested on a Fairphone 4 smartphone with additional changes
not included in this series (mostly just wiring up TCPM and the SBU
mux).
Signed-off-by: Luca Weiss
Add the node for the DisplayPort controller found on the SM6350 SoC.
Reviewed-by: Dmitry Baryshkov
Signed-off-by: Luca Weiss
---
arch/arm64/boot/dts/qcom/sm6350.dtsi | 88
1 file changed, 88 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sm6350.dtsi
Document the displayport controller subnode of the SM6350 MDSS.
Signed-off-by: Luca Weiss
---
.../devicetree/bindings/display/msm/qcom,sm6350-mdss.yaml| 9 +
1 file changed, 9 insertions(+)
diff --git
a/Documentation/devicetree/bindings/display/msm/qcom,sm6350-mdss.yaml
b
Add the compatible string for the DisplayPort controller on SM6350 which
is compatible with the one on SM8350.
Acked-by: Rob Herring
Signed-off-by: Luca Weiss
---
Documentation/devicetree/bindings/display/msm/dp-controller.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation
Add the required changes to support DisplayPort (normally(?) available
via the USB-C connector) on the SM6350/SM7225 SoC.
This has been tested on a Fairphone 4 smartphone with additional changes
not included in this series (mostly just wiring up TCPM and the SBU
mux).
Signed-off-by: Luca Weiss
&& (
className.contains(".pages.") ||
className.contains(".components.") ||
className.contains(".base."));
Shouldn't the "mixins" well know package be listed as well?
Luca
- Original Mess
On Wed, 20 Mar 2024 at 02:00, Nils Kattenbeck wrote:
>
> Hello,
>
> I am writing a simple oneshot service which should read access from
> the journal and systemctl status. To restrict the service I was trying
> to enable DynamicUser (and added '
> SupplementaryGroups=systemd-journal'). However,
al links, not sure how useful they will be for upstream
> discussions.
> Give the relevant details here which is better I believe instead of an
> internal link.
As we discussed offline, this seems to be common practice, and Gustavo
actually asked me to add it in a previous review, so we
Stupid typo in subject, should of course be SM6350, not SM8250.
On Thu Mar 28, 2024 at 10:42 AM CET, Luca Weiss wrote:
> Add the compatible string for the DisplayPort controller on SM6350 which
> is compatible with the one on SM8350.
>
> Signed-off-by: Luca Weiss
> ---
&
Stupid typo in subject, should of course be SM6350, not SM8250.
On Thu Mar 28, 2024 at 10:42 AM CET, Luca Weiss wrote:
> Add the compatible string for the DisplayPort controller on SM6350 which
> is compatible with the one on SM8350.
>
> Signed-off-by: Luca Weiss
> ---
&
Add the node for the DisplayPort controller found on the SM6350 SoC.
Signed-off-by: Luca Weiss
---
arch/arm64/boot/dts/qcom/sm6350.dtsi | 88
1 file changed, 88 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sm6350.dtsi
b/arch/arm64/boot/dts/qcom
Add the node for the DisplayPort controller found on the SM6350 SoC.
Signed-off-by: Luca Weiss
---
arch/arm64/boot/dts/qcom/sm6350.dtsi | 88
1 file changed, 88 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sm6350.dtsi
b/arch/arm64/boot/dts/qcom
Document the displayport controller subnode of the SM6350 MDSS.
Signed-off-by: Luca Weiss
---
.../devicetree/bindings/display/msm/qcom,sm6350-mdss.yaml | 10 ++
1 file changed, 10 insertions(+)
diff --git
a/Documentation/devicetree/bindings/display/msm/qcom,sm6350-mdss.yaml
b
Add the compatible string for the DisplayPort controller on SM6350 which
is compatible with the one on SM8350.
Signed-off-by: Luca Weiss
---
Documentation/devicetree/bindings/display/msm/dp-controller.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings
Document the displayport controller subnode of the SM6350 MDSS.
Signed-off-by: Luca Weiss
---
.../devicetree/bindings/display/msm/qcom,sm6350-mdss.yaml | 10 ++
1 file changed, 10 insertions(+)
diff --git
a/Documentation/devicetree/bindings/display/msm/qcom,sm6350-mdss.yaml
b
Add the required changes to support DisplayPort (normally(?) available
via the USB-C connector) on the SM6350/SM7225 SoC.
This has been tested on a Fairphone 4 smartphone with additional changes
not included in this series (mostly just wiring up TCPM and the SBU
mux).
Signed-off-by: Luca Weiss
Add the compatible string for the DisplayPort controller on SM6350 which
is compatible with the one on SM8350.
Signed-off-by: Luca Weiss
---
Documentation/devicetree/bindings/display/msm/dp-controller.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings
Add the required changes to support DisplayPort (normally(?) available
via the USB-C connector) on the SM6350/SM7225 SoC.
This has been tested on a Fairphone 4 smartphone with additional changes
not included in this series (mostly just wiring up TCPM and the SBU
mux).
Signed-off-by: Luca Weiss
no screen corruption.
[0] commit 6a0dbcd20ef2 ("drm/msm/a6xx: set highest_bank_bit to 13 for a610")
Fixes: b7616b5c69e6 ("drm/msm/adreno: Add A619 support")
Signed-off-by: Luca Weiss
---
@Akhil: Dmitry & Abhinav said I should ping you specifically to take a
look if you have
no screen corruption.
[0] commit 6a0dbcd20ef2 ("drm/msm/a6xx: set highest_bank_bit to 13 for a610")
Fixes: b7616b5c69e6 ("drm/msm/adreno: Add A619 support")
Signed-off-by: Luca Weiss
---
@Akhil: Dmitry & Abhinav said I should ping you specifically to take a
look if you have
Hi Maxime,
On Wed, 27 Mar 2024 13:42:40 +0100
Maxime Ripard wrote:
> On Tue, Mar 26, 2024 at 05:28:14PM +0100, Luca Ceresoli wrote:
> > This driver implements the point of a DRM pipeline where a connector allows
> > removal of all the following bridges up to the panel.
&
On Wed, 27 Mar 2024 at 07:57, Heinrich Schuchardt
wrote:
>
> On 3/26/24 22:47, Vagrant Cascadian wrote:
> > On 2024-02-16, Heinrich Schuchardt wrote:
> >> debian/patches/qemu/efi-secure-boot.patch is not a good approach to
> >> enabling secure boot with U-Boot. Variables entered via the command
[
https://issues.apache.org/jira/browse/CAMEL-20524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831246#comment-17831246
]
Luca Burgazzoli commented on CAMEL-20524:
-
so we are fine ! thank you [~gnodet]
> Harmon
want
to use it, that's fine, simply don't load keys from the console, it's a
no-op then, it doesn't have any impact unless the appropriate commands
are ran at boot, so I don't see why it should be removed.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
hoc lookup is
needed
The code handling these and other tricky aspects is accurately documented
by comments in the code.
Co-developed-by: Paul Kocialkowski
Signed-off-by: Paul Kocialkowski
Signed-off-by: Luca Ceresoli
---
MAINTAINERS | 1 +
drivers/gpu/drm/bridge/Kconfi
Supporting hardware whose final part of the DRM pipeline can be physically
removed requires the ability to detach all bridges from a given point to
the end of the pipeline.
Introduce a variant of drm_encoder_cleanup() for this.
Signed-off-by: Luca Ceresoli
---
drivers/gpu/drm/drm_encoder.c
Add bindings for a physical, hot-pluggable connector allowing the far end
of a MIPI DSI bus to be connected and disconnected at runtime.
Signed-off-by: Luca Ceresoli
---
.../bridge/hotplug-video-connector-dsi.yaml| 87 ++
MAINTAINERS
From: Paul Kocialkowski
In preparation for allowing bridges to be added to and removed from a DRM
card without destroying the whole card, add a DRM bridge notifier. Notified
events are addition and removal to/from the global bridge list.
Co-developed-by: Luca Ceresoli
Signed-off-by: Luca
tested by other
means, even with a hardware that has no removable parts, "pretending" that
one or more bridges can be removed:
* remove and re-insert the driver module for the DRM bridge after the
hotplug-bridge
* unbind/bind the DRM bridge after the hotplug-bridge from its drive
401 - 500 of 109577 matches
Mail list logo
