Commit c0603369 authored by Robert Schmidt's avatar Robert Schmidt

Remove unused or write-only variables

parent 62333cd3
...@@ -203,7 +203,6 @@ int nr_dlsch_encoding(PHY_VARS_gNB *gNB, ...@@ -203,7 +203,6 @@ int nr_dlsch_encoding(PHY_VARS_gNB *gNB,
// The harq_pid is not unique among the active HARQ processes in the instance so we use dlsch_id instead // The harq_pid is not unique among the active HARQ processes in the instance so we use dlsch_id instead
TB_parameters->harq_unique_pid = dlsch_id; TB_parameters->harq_unique_pid = dlsch_id;
TB_parameters->BG = rel15->maintenance_parms_v3.ldpcBaseGraph; TB_parameters->BG = rel15->maintenance_parms_v3.ldpcBaseGraph;
TB_parameters->Z = harq->Z;
TB_parameters->A = A; TB_parameters->A = A;
start_meas(dlsch_segmentation_stats); start_meas(dlsch_segmentation_stats);
TB_parameters->Kb = nr_segmentation(harq->b, TB_parameters->Kb = nr_segmentation(harq->b,
......
...@@ -62,12 +62,8 @@ typedef struct { ...@@ -62,12 +62,8 @@ typedef struct {
uint8_t *b; uint8_t *b;
/// Pointers to transport block segments /// Pointers to transport block segments
uint8_t **c; uint8_t **c;
/// Frame where current HARQ round was sent
uint32_t frame;
/// Interleaver outputs /// Interleaver outputs
uint8_t *f; uint8_t *f;
/// LDPC lifting size
uint32_t Z;
/// REs unavailable for DLSCH (overlapping with PTRS, CSIRS etc.) /// REs unavailable for DLSCH (overlapping with PTRS, CSIRS etc.)
uint32_t unav_res; uint32_t unav_res;
} NR_DL_gNB_HARQ_t; } NR_DL_gNB_HARQ_t;
...@@ -118,10 +114,6 @@ typedef struct { ...@@ -118,10 +114,6 @@ typedef struct {
typedef struct { typedef struct {
/// Pointers to variables related to DLSCH harq process /// Pointers to variables related to DLSCH harq process
NR_DL_gNB_HARQ_t harq_process; NR_DL_gNB_HARQ_t harq_process;
/// Active flag for baseband transmitter processing
uint8_t active;
/// Number of soft channel bits
uint32_t G;
} NR_gNB_DLSCH_t; } NR_gNB_DLSCH_t;
typedef struct { typedef struct {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment