Remove pattern constraint from location field

[parmi93]

According to the "PSA Certified Crypto Driver Interface" (Section 3.2) https://arm-software.github.io/psa-api/crypto-driver/1.0/body/manifest.html#driver-description-top-level-element, the location field may be either a non-negative integer or a C constant expression of type psa_key_location_t. For this reason, the pattern constraint is being removed, allowing the user to input any value.

[parmi93]

Now user can set up a JSON manifest file like this:

{
    "prefix": "stsafe_a110",
    "type": "opaque",
    "location": "STSAFE_A110_LOCATION", /* <- Previously, only hexadecimal values were permitted. */
    "headers": [
        "stsafe_a110_psa_driver.h"
    ],
    "capabilities": [
        {
            "entry_points": [
                "_comment": "bla bla"
            ],
        }
    ]
}

stsafe_a110_psa_driver.h:

#define STSAFE_A110_LOCATION ((psa_key_location_t)0x800001)

[gilles-peskine-arm]

LGTM

[gilles-peskine-arm]

I'm curious, are you finding the script to be usable as it is? I'm aware that only a small subset of the functionality is implemented.

[parmi93]

The script (generate_driver_wrappers.py) does the job. As for the Jinja templates (psa_crypto_driver_wrappers.h.jinja and psa_crypto_driver_wrappers_no_static.c.jinja), they are still incomplete since only a small number of entry points are supported. So I end up patching the templates for my needs, but apart from that I didn’t have to touch anything else (except having to manually call the script (generate_driver_wrappers.py) because I need to pass it the path to my patched Jinja templates).