public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: christian.taedcke-oss@weidmueller.com
Cc: u-boot@lists.denx.de,
	Christian Taedcke <christian.taedcke@weidmueller.com>,
	Simon Glass <sjg@chromium.org>,
	Michal Simek <michal.simek@amd.com>
Subject: Re: [PATCH v4 2/2] event: Add fpga load event
Date: Wed, 19 Jul 2023 16:30:50 -0400	[thread overview]
Message-ID: <20230719203050.GD1670569@bill-the-cat> (raw)
In-Reply-To: <20230719134544.235585-2-christian.taedcke-oss@weidmueller.com>

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

On Wed, Jul 19, 2023 at 03:45:44PM +0200, christian.taedcke-oss@weidmueller.com wrote:
> From: Christian Taedcke <christian.taedcke@weidmueller.com>
> 
> This enables implementing custom logic after a bitstream was loaded
> into the fpga.
> 
> Signed-off-by: Christian Taedcke <christian.taedcke@weidmueller.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
[snip]
> diff --git a/include/event.h b/include/event.h
> index fe41080fa6..77124c2e73 100644
> --- a/include/event.h
> +++ b/include/event.h
> @@ -31,6 +31,9 @@ enum event_t {
>  	/* Init hooks */
>  	EVT_MISC_INIT_F,
>  
> +	/* Fpga load hook */
> +	EVT_FPGA_LOAD,
> +
>  	/* Device tree fixups before booting */
>  	EVT_FT_FIXUP,
>  
> @@ -59,6 +62,19 @@ union event_data {
>  		struct udevice *dev;
>  	} dm;
>  
> +	/**
> +	 * struct event_fpga_load - fpga load event
> +	 *
> +	 * @buf: The buffer that was loaded into the fpga
> +	 * @bsize: The size of the buffer that was loaded into the fpga
> +	 * @result: Result of the load operation
> +	 */
> +	struct event_fpga_load {
> +		const void *buf;
> +		size_t bsize;
> +		int result;
> +	} fpga_load;
> +
>  	/**
>  	 * struct event_ft_fixup - FDT fixup before booting
>  	 *

Since here is where you're introducing a size_t to event.h, here is
where you also need to add <linux/types.h> to event.h

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2023-07-19 20:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19 13:45 [PATCH v4 1/2] board/km/cent2: add include common.h christian.taedcke-oss
2023-07-19 13:45 ` [PATCH v4 2/2] event: Add fpga load event christian.taedcke-oss
2023-07-19 20:30   ` Tom Rini [this message]
2023-07-19 19:11 ` [PATCH v4 1/2] board/km/cent2: add include common.h Simon Glass
2023-07-19 20:28 ` Tom Rini

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=20230719203050.GD1670569@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=christian.taedcke-oss@weidmueller.com \
    --cc=christian.taedcke@weidmueller.com \
    --cc=michal.simek@amd.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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