Skip to content

Conversation

@abonislawski
Copy link
Member

Increased ipc msg max size will allow to fit
a bigger ipc, e.g. needed for mux channel map.

Signed-off-by: Adrian Bonislawski [email protected]

Increased ipc msg max size will allow to fit
a bigger ipc, e.g. needed for mux channel map.

Signed-off-by: Adrian Bonislawski <[email protected]>
Copy link

@paulstelian97 paulstelian97 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved as long as it works with the firmware having the corresponding PR merged. There is nothing broken on any of the platforms on the firmware side I assume.


/* maximum message size for mailbox Tx/Rx */
#define SOF_IPC_MSG_MAX_SIZE 384
#define SOF_IPC_MSG_MAX_SIZE 768
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried to recall or find where this restriction originally comes from, and I couldn't. @lgirdwood could you remind please? I'll make sure to make a note this time.
I think this restriction comes from the original IPC protocol from the alternative firmware implementation? Currently size limits seem to be set in the firmware by MAILBOX_HOSTBOX_SIZE / MAILBOX_DSPBOX_SIZE macros, for which the smallest value I found was 1024. Is this complete area usable as a mailbox or is a part of it used for other purposes? So, I'd go straight with the largest possible value here. Of course, it has to be reflected in the firmware too.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lyakh it was discussed on FW PR:
thesofproject/sof#2216
Currently it cannot be set to the largest possible value but it will later with some changes to ipc msg allocations

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@abonislawski ok, got it, thanks

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how does this work if a new kernel using a max size of 768 is used with an old firmware relying on a value of 384?

And why not 1K while we've at it? or 4K as in the past?

Copy link
Member

@plbossart plbossart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

need more context on ABI and backwards compatibility


/* maximum message size for mailbox Tx/Rx */
#define SOF_IPC_MSG_MAX_SIZE 384
#define SOF_IPC_MSG_MAX_SIZE 768
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how does this work if a new kernel using a max size of 768 is used with an old firmware relying on a value of 384?

And why not 1K while we've at it? or 4K as in the past?

@plbossart plbossart added the Unclear No agreement on problem statement and resolution label Feb 4, 2020
@plbossart
Copy link
Member

@abonislawski can we close this? it's been shelved since January 21 and bit-rotting since.

@abonislawski
Copy link
Member Author

@plbossart yes, just a note for everyone: ipc msg size will be send via fw extended manifest

@plbossart
Copy link
Member

just a note for everyone: ipc msg size will be send via fw extended manifest

Ah, good to know, thanks for sharing - makes complete sense to me :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Unclear No agreement on problem statement and resolution

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants