linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konradybcio@gmail.com>,
	Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	konrad.dybcio@linaro.org, andersson@kernel.org,
	andi.shyti@kernel.org, linux-arm-msm@vger.kernel.org,
	dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-i2c@vger.kernel.org, conor+dt@kernel.org,
	agross@kernel.org, devicetree@vger.kernel.org, vkoul@kernel.org,
	linux@treblig.org, dan.carpenter@linaro.org, Frank.Li@nxp.com,
	konradybcio@kernel.org, bryan.odonoghue@linaro.org,
	krzk+dt@kernel.org, robh@kernel.org
Cc: quic_vdadhani@quicinc.com
Subject: Re: [PATCH v5 1/4] dt-bindindgs: i2c: qcom,i2c-geni: Document shared flag
Date: Tue, 10 Dec 2024 16:56:26 +0100	[thread overview]
Message-ID: <c55d8212-9b7e-4ede-a15d-3fbeeb95f956@kernel.org> (raw)
In-Reply-To: <1035d5c0-7034-4797-8a89-d0d92811c0ef@gmail.com>

>> There would be spare register but i think it should be in sync with hardware team. let me check with them and update back if any bit can be repurposed for this feature. I agree, if any register is available, it can programmed prior to kernel.
>>> It would need to be reserved on all SoCs though (future and
>>> past), to make sure the contract is always held up, but I
>>> think finding a persistent bit that has never been used
>>> shouldn't be impossible.
>>>
>> Yes, let me check it with hardware and firmware team and update back. Does this mean, there can't be a such software sharing mechanism (purely software decision) based on DTSI flag ?
> 
> I suppose that depends on our needs. If we can set that bit
> before Linux starts (i.e. in UEFI), we can avoid touching
> the pinctrl state regardless of whether the other entities
> have started up yet to avoid overcomplicating it.
> 
> If we need Linux to set that bit, we would still need some
> mechanism like a dt property. But I really think that the
> bootloader should be burdened with this instead, given it
> has a better understanding of the hardware due to it being
> well, the bootloader).
> 
> Krzysztof, I'm assuming that sounds sane from your
> perspective too?
Yes, sound okay.

Best regards,
Krzysztof

  reply	other threads:[~2024-12-10 15:56 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29 14:43 [PATCH v5 0/4] Enable shared SE support over I2C Mukesh Kumar Savaliya
2024-11-29 14:43 ` [PATCH v5 1/4] dt-bindindgs: i2c: qcom,i2c-geni: Document shared flag Mukesh Kumar Savaliya
2024-11-29 15:14   ` Krzysztof Kozlowski
2024-12-02  4:00     ` Mukesh Kumar Savaliya
2024-12-02  7:19       ` Krzysztof Kozlowski
2024-12-02 10:38         ` Mukesh Kumar Savaliya
2024-12-02 11:04           ` Krzysztof Kozlowski
2024-12-02 11:13             ` Krzysztof Kozlowski
2024-12-09 15:07               ` Mukesh Kumar Savaliya
2024-12-02 12:55             ` Mukesh Kumar Savaliya
2024-12-02 14:04               ` Konrad Dybcio
2024-12-09 15:01                 ` Mukesh Kumar Savaliya
2024-12-10  7:28                 ` Krzysztof Kozlowski
2024-12-10  9:09                   ` Konrad Dybcio
2024-12-10 11:53                     ` Krzysztof Kozlowski
2024-12-10 12:05                       ` Krzysztof Kozlowski
2024-12-10 12:38                         ` Konrad Dybcio
2024-12-10 15:17                           ` Mukesh Kumar Savaliya
2024-12-10 15:24                             ` Konrad Dybcio
2024-12-10 15:56                               ` Krzysztof Kozlowski [this message]
2024-12-10 17:52                           ` Bjorn Andersson
2024-11-30  4:45   ` Bjorn Andersson
2024-12-02 10:38     ` Mukesh Kumar Savaliya
2024-12-03 15:43       ` Bjorn Andersson
2024-11-29 14:43 ` [PATCH v5 2/4] dmaengine: gpi: Add Lock and Unlock TRE support to access I2C exclusively Mukesh Kumar Savaliya
2024-12-02  6:47   ` Vinod Koul
2024-12-02 10:43     ` Mukesh Kumar Savaliya
2024-12-04 12:21       ` Vinod Koul
2024-12-18 12:34         ` Mukesh Kumar Savaliya
2024-12-24  9:58           ` Vinod Koul
2024-12-26 12:22             ` Mukesh Kumar Savaliya
2025-01-14  9:18               ` Mukesh Kumar Savaliya
2024-11-29 14:43 ` [PATCH v5 3/4] soc: qcom: geni-se: Do not keep GPIOs to sleep state for shared SE usecase Mukesh Kumar Savaliya
2024-11-29 14:43 ` [PATCH v5 4/4] i2c: i2c-qcom-geni: Enable i2c controller sharing between two subsystems Mukesh Kumar Savaliya
2024-12-13 13:05   ` Konrad Dybcio
2024-12-15  8:59     ` Mukesh Kumar Savaliya
2024-12-16 12:10       ` Konrad Dybcio
2024-12-16 12:47         ` Mukesh Kumar Savaliya

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c55d8212-9b7e-4ede-a15d-3fbeeb95f956@kernel.org \
    --to=krzk@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@gmail.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@treblig.org \
    --cc=quic_msavaliy@quicinc.com \
    --cc=quic_vdadhani@quicinc.com \
    --cc=robh@kernel.org \
    --cc=vkoul@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).