On Tue, Aug 21, 2018 at 08:01:59PM +0530, Lokesh Vutla wrote:
> K3 specific SoCs have a dedicated microcontroller for doing
> resource management. Any HLOS/firmware on compute clusters should
> load a firmware to this microcontroller before accessing any resource.
> Adding support for loading this firmware.
>
> After the K3 system controller got loaded with firmware and started
> up it sends out a boot notification message through the secure proxy
> facility using the TI SCI protocol. Intercept and receive this message
> through the rproc start operation which will need to get invoked
> explicitly after the firmware got loaded.
[snip]
> +/**
> + * struct k3_sysctrler_msg_hdr - Generic Header for Messages and responses.
> + * @cmd_id: Message ID. One of K3_MSG_*
> + * @host_id: Host ID of the message
> + * @seq_ne: Message identifier indicating a transfer sequence.
> + * @flags: Flags for the message.
> + */
> +struct k3_sysctrler_msg_hdr {
> + u16 cmd_id;
> + u8 host_id;
> + u8 seq_nr;
> + u32 flags;
> +} __attribute__ ((__packed__));Here and elsewhere please use __packed. Thanks! -- Tom
signature.asc
Description: PGP signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
