public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sam Winchenbach <sam.winchenbach@framepointer.org>
Cc: linux-kernel@vger.kernel.org, mdf@kernel.org, hao.wu@intel.com,
	yilun.xu@intel.com, trix@redhat.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, michal.simek@amd.com,
	linux-fpga@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Sam Winchenbach <swinchenbach@arka.org>
Subject: Re: [PATCH 1/2] dt-bindings: fpga: zynq: Document ICAP on boot
Date: Mon, 31 Mar 2025 14:43:59 +0200	[thread overview]
Message-ID: <14b12882-119d-4c24-9634-e4cc37a39212@kernel.org> (raw)
In-Reply-To: <p4bujnmgkcvsu4qipmgh2j2loedepmwgp7zlaxrurhaveb6tbc@ibqtbjnbzdzj>

On 31/03/2025 14:30, Sam Winchenbach wrote:
>>
>>> +    type: boolean
>>> +    description: If present, the ICAP controller will be enabled when
>>> +      the driver probes. This is useful if the fabric is loaded
>>> +      during the boot process and contains a core, such as the SEM,
>>
>> I don't get how this is suitable for DT. If you decide to load the
>> fabric from driver, that's driver decision so not DT.
> 
> Before writing the fabric to the FPGA the driver disables the ICAP, enabling
> the PCAP. Once writing is complete it unconditionally disables the PCAP,
> enabling the ICAP. This patch just makes it so, depending on the use case,
> the ICAP can be enabled at boot. This will not prevent the system from being
> able to load a fabric through the driver. I added in this boolean so existing
> behavior would be maintained.
> 
> Do you recommend another approach such as writing to a sysfs attribute to
> switch from PCAP to ICAP?
Not sure yet. Can't you check the status of ICAP before programming and
then enable it only if was enabled before?

Best regards,
Krzysztof

  reply	other threads:[~2025-03-31 12:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 14:19 [PATCH 1/2] dt-bindings: fpga: zynq: Document ICAP on boot Sam Winchenbach
2025-03-28 14:19 ` [PATCH 2/2] fpga: zynq-fpga: Allow ICAP enable on probe Sam Winchenbach
2025-03-29  4:59 ` [PATCH 1/2] dt-bindings: fpga: zynq: Document ICAP on boot Krzysztof Kozlowski
2025-03-31 12:30   ` Sam Winchenbach
2025-03-31 12:43     ` Krzysztof Kozlowski [this message]
2025-03-31 13:07       ` Sam Winchenbach
2025-04-01  6:17         ` Krzysztof Kozlowski
2025-04-09  6:03         ` Krzysztof Kozlowski
2025-04-24 10:02         ` Xu Yilun

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=14b12882-119d-4c24-9634-e4cc37a39212@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hao.wu@intel.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=michal.simek@amd.com \
    --cc=robh@kernel.org \
    --cc=sam.winchenbach@framepointer.org \
    --cc=swinchenbach@arka.org \
    --cc=trix@redhat.com \
    --cc=yilun.xu@intel.com \
    /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