The QSPI devices I've looked at have some auxiliary functionality - a multi-byte unique ID, and a certain amount of OTP memory.
Any thoughts on how this could best be exposed to the outside world?
My initial thought is a single ioctl()-like interface, to make it simple to add additional options later.
QSPI Auxiliary Functionality
- Giovanni
- Site Admin
- Posts: 14444
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1074 times
- Been thanked: 921 times
- Contact:
Re: QSPI Auxiliary Functionality
Hi,
It is already possible to send custom commands by calling the inner functions, currently there is no official API, it could be an idea.
Giovanni
It is already possible to send custom commands by calling the inner functions, currently there is no official API, it could be an idea.
Giovanni
Re: QSPI Auxiliary Functionality
I implemented this using the threatened ioctl()-like interface, as the attached.
Mostly to give some ideas - maybe add a pointer in the VMT to the ioctl() routine. And there are some other error codes which could usefully be added.
Mostly to give some ideas - maybe add a pointer in the VMT to the ioctl() routine. And there are some other error codes which could usefully be added.
- Attachments
-
- QSPI_ioctl.zip
- (2.34 KiB) Downloaded 164 times
- Giovanni
- Site Admin
- Posts: 14444
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1074 times
- Been thanked: 921 times
- Contact:
Re: QSPI Auxiliary Functionality
Not yet, I will do another pass on the flash driver later, I am on another thing right now.
Giovanni
Giovanni
Return to “Development and Feedback”
Who is online
Users browsing this forum: No registered users and 7 guests