Introduce Customization struct (#458)
* Introduce Customization trait * Introduce Customization trait including the customization accessors that control various behaviors. * Expose Customization through a getter API in Env, and make the code that directly access the constants currently switch to accessing the customizations via Env. * TockEnv's customization getter implementation directly returns the reference of the global DEFAULT_CUSTOMIZATION constant, so the constant values are still inlined and dead code won't be compiled. * We'll add the customizations from global constants to the struct one-by-one, only MAX_MSG_SIZE in this commit. * Small fixes * Fix deploy script * put is_valid under std gate
This commit is contained in:
4
src/env/mod.rs
vendored
4
src/env/mod.rs
vendored
@@ -1,3 +1,4 @@
|
||||
use crate::api::customization::Customization;
|
||||
use crate::api::firmware_protection::FirmwareProtection;
|
||||
use crate::api::upgrade_storage::UpgradeStorage;
|
||||
use crate::ctap::status_code::Ctap2StatusCode;
|
||||
@@ -24,6 +25,7 @@ pub trait Env {
|
||||
type UpgradeStorage: UpgradeStorage;
|
||||
type FirmwareProtection: FirmwareProtection;
|
||||
type Write: core::fmt::Write;
|
||||
type Customization: Customization;
|
||||
|
||||
fn rng(&mut self) -> &mut Self::Rng;
|
||||
fn user_presence(&mut self) -> &mut Self::UserPresence;
|
||||
@@ -44,4 +46,6 @@ pub trait Env {
|
||||
/// using the defmt crate) and ignore this API. Non-embedded environments may either use this
|
||||
/// API or use the log feature (to be implemented using the log crate).
|
||||
fn write(&mut self) -> Self::Write;
|
||||
|
||||
fn customization(&self) -> &Self::Customization;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user