devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xu Yilun <yilun.xu@linux.intel.com>
To: Phil Pemberton <philpem@philpem.me.uk>
Cc: Moritz Fischer <mdf@kernel.org>, Xu Yilun <yilun.xu@intel.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Tom Rix <trix@redhat.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	linux-fpga@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] fpga: ts73xx-fpga: add OF match table for device tree probing
Date: Mon, 4 May 2026 19:19:12 +0800	[thread overview]
Message-ID: <afiAsAUkNdVkXwFO@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <20260409122016.3940462-3-philpem@philpem.me.uk>

On Thu, Apr 09, 2026 at 01:20:16PM +0100, Phil Pemberton wrote:
> The ts73xx-fpga driver currently only matches by platform device name,
> which prevents it from being probed when the device is described in a
> device tree. Add an of_device_id table so the driver can match against
> the "technologic,ts7300-fpga" compatible string.
> 
> The TS-7350 and TS-7390 use different FPGAs with a different programming
> interface, so while the driver is named "ts73xx-fpga", it doesn't apply
> to them.
> 
> Signed-off-by: Phil Pemberton <philpem@philpem.me.uk>
> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>

Reviewed-by: Xu Yilun <yilun.xu@intel.com>

Applied this series to for-next.

      reply	other threads:[~2026-05-04 11:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09 12:20 [PATCH v3 0/2] Add device tree binding for ts73xx-fpga Phil Pemberton
2026-04-09 12:20 ` [PATCH v3 1/2] dt-bindings: fpga: Add Technologic Systems TS-7300 FPGA Manager Phil Pemberton
2026-04-09 12:20 ` [PATCH v3 2/2] fpga: ts73xx-fpga: add OF match table for device tree probing Phil Pemberton
2026-05-04 11:19   ` Xu Yilun [this message]

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=afiAsAUkNdVkXwFO@yilunxu-OptiPlex-7050 \
    --to=yilun.xu@linux.intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=philpem@philpem.me.uk \
    --cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).