mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: V.Yurkov.EXT@bruker.com, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Vyacheslav Yurkov <uvv.mail@gmail.com>
Subject: Re: [PATCH 2/2] bus: add Altera timeout bridge driver
Date: Sat, 3 Oct 2026 23:24:48 +0200	[thread overview]
Message-ID: <3c7238c0-b963-42e9-b0b4-3b1f231ee9ee@kernel.org> (raw)
In-Reply-To: <20261003-feature-timeout-ip-v1-2-8837c311d571@bruker.com>

On 03/10/2026 22:19, Vyacheslav Yurkov via B4 Relay wrote:
> From: Vyacheslav Yurkov <V.Yurkov.EXT@bruker.com>
> 
> Add support for the Altera timeout bridge IP.
> 
> The bridge connects an Avalon bus to the HPS and monitors accesses for
> timeouts. When a timeout occurs the interrupt communicates the event via
> sysfs, which user space can monitor to handle it accordingly. The
> address with the timeout is reported as well.
> 

Neither this nor binding explains what is this hardware and where I can
find it.

> Signed-off-by: Vyacheslav Yurkov <V.Yurkov.EXT@bruker.com>
> ---
>  drivers/bus/Kconfig                 |  10 ++
>  drivers/bus/Makefile                |   1 +
>  drivers/bus/altera-timeout-bridge.c | 219 ++++++++++++++++++++++++++++++++++++
>  3 files changed, 230 insertions(+)
> 
> diff --git a/drivers/bus/Kconfig b/drivers/bus/Kconfig
> index e4b1db809187..8a4ad96742e5 100644
> --- a/drivers/bus/Kconfig
> +++ b/drivers/bus/Kconfig
> @@ -247,6 +247,16 @@ config DA8XX_MSTPRI
>  	  configuration. Allows to adjust the priorities of all master
>  	  peripherals.
>  
> +config ALTERA_TIMEOUT_BRIDGE
> +	tristate "Altera AXI Timeout Bridge bus"
> +	depends on OF
> +	default n
> +	help
> +	  Driver for Altera AXI Timeout Bridge, which can be used a bus.
> +	  The subordinate devices can be connected to the bridge, which
> +	  detects frozen read/write requests and notifies user space by
> +	  means of a sysfs interrupt flag.




> +
> +static ssize_t irq_count_show(struct device *dev,
> +			      struct device_attribute *attr,
> +			      char *buf)
> +{
> +	struct altera_timeout_bridge_data *driver_data = dev_get_drvdata(dev);
> +
> +	return sysfs_emit(buf, "%d\n", atomic_read(&driver_data->irq_count));
> +}
> +
> +static DEVICE_ATTR_RO(timeout_irq);
> +static DEVICE_ATTR_RO(irq_count);

Missing ABI documentation.


> +


> +
> +#define ONLY_BUS	((void *) 1) /* Match if the device is only a bus. */
> +
> +static const struct of_device_id altera_timeout_bridge_of_match[] = {
> +	{ .compatible = "altera-timeout-bridge", },
> +	{ .compatible = "simple-bus",	.data = ONLY_BUS },

I don't understand why you want to bind to generic compatible.



> +	{ /* sentinel */ }
> +};
> +MODULE_DEVICE_TABLE(of, altera_timeout_bridge_of_match);
> +
> +static struct platform_driver altera_timeout_bridge_driver = {
> +	.probe = altera_timeout_bridge_probe,
> +	.driver = {
> +		.name = "altera-timeout-bridge",
> +		.of_match_table = altera_timeout_bridge_of_match,
> +	},
> +};
> +
> +module_platform_driver(altera_timeout_bridge_driver);
> +
> +MODULE_LICENSE("GPL");
> +MODULE_DESCRIPTION("Avalon Timeout Bridge Bus");
> +MODULE_AUTHOR("Vyacheslav Yurkov (V.Yurkov.EXT@bruker.com)");
> +
> 


Best regards,
Krzysztof

      reply	other threads:[~2026-10-03 21:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 20:19 [PATCH 0/2] Add " Vyacheslav Yurkov via B4 Relay
2026-10-03 20:19 ` [PATCH 1/2] dt-bindings: bus: Add binding for Altera AXI Timeout Bridge Vyacheslav Yurkov via B4 Relay
2026-10-03 21:18   ` Krzysztof Kozlowski
2026-10-03 20:19 ` [PATCH 2/2] bus: add Altera timeout bridge driver Vyacheslav Yurkov via B4 Relay
2026-10-03 21:24   ` Krzysztof Kozlowski [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=3c7238c0-b963-42e9-b0b4-3b1f231ee9ee@kernel.org \
    --to=krzk@kernel.org \
    --cc=V.Yurkov.EXT@bruker.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=uvv.mail@gmail.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

all inboxes | Powered by JetHome®