From 019e802e27905929349d2077726250df6b828017 Mon Sep 17 00:00:00 2001 From: JackN Date: Thu, 12 Oct 2023 18:52:50 -0400 Subject: [PATCH] OCTOSPI: Fix "MAXTRAN was in wrong yaml". --- data/registers/octospi_v1.yaml | 4 ++++ data/registers/octospi_v2.yaml | 4 ---- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/data/registers/octospi_v1.yaml b/data/registers/octospi_v1.yaml index b170156..be0c349 100644 --- a/data/registers/octospi_v1.yaml +++ b/data/registers/octospi_v1.yaml @@ -294,6 +294,10 @@ fieldset/DCR2: fieldset/DCR3: description: device configuration register 3 fields: + - name: MAXTRAN + description: Maximum transfer + bit_offset: 0 + bit_size: 8 - name: CSBOUND description: 'NCS boundary. This field enables the transaction boundary feature. When active, a minimum value of 3 is recommended. The NCS is released on each boundary of 2CSBOUND bytes. others: NCS boundary set to 2CSBOUND bytes' bit_offset: 16 diff --git a/data/registers/octospi_v2.yaml b/data/registers/octospi_v2.yaml index be0c349..b170156 100644 --- a/data/registers/octospi_v2.yaml +++ b/data/registers/octospi_v2.yaml @@ -294,10 +294,6 @@ fieldset/DCR2: fieldset/DCR3: description: device configuration register 3 fields: - - name: MAXTRAN - description: Maximum transfer - bit_offset: 0 - bit_size: 8 - name: CSBOUND description: 'NCS boundary. This field enables the transaction boundary feature. When active, a minimum value of 3 is recommended. The NCS is released on each boundary of 2CSBOUND bytes. others: NCS boundary set to 2CSBOUND bytes' bit_offset: 16