| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <ffa2a863c8a9b99582ad6648600d372b@mainlining.org> Date: Wed, 13 Nov 2024 16:32:52 +0100 From: barnabas.czeman@...nlining.org To: Bryan O'Donoghue <bryan.odonoghue@...aro.org> Cc: Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>, Robert Foss <rfoss@...nel.org>, Todor Tomov <todor.too@...il.com>, Mauro Carvalho Chehab <mchehab@...nel.org>, Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, devicetree@...r.kernel.org, Vladimir Lypak <vladimir.lypak@...il.com> Subject: Re: [PATCH v4 3/3] media: qcom: camss: Add MSM8953 resources On 2024-11-13 16:23, Bryan O'Donoghue wrote: > On 13/11/2024 13:28, Vladimir Zapolskiy wrote: >> So, we have to rely on the documentation here. Bryan, can you please >> check, if VDDA_MIPI_CSI pad on MSM8916 and/or MSM8953 is related to >> CSIPHY or CSID power supply? Thank you in advance. > > No there's really no indication in the documents I have how the input > gets routed internally, CSID, CSIPHY, both.. not clear. > > I think Barnabás is right, the best source of information we have for > this one is the downstream dtsi => CSID. I have found the regulator also in downstream msm_csid driver i hope it helps a bit. https://git.codelinaro.org/clo/la/kernel/msm-4.9/-/blob/LA.UM.10.6.2.c26-01500-89xx.0/drivers/media/platform/msm/camera_v2/sensor/csid/msm_csid.c#L73 > > --- > bod
Powered by blists - more mailing lists