-
Notifications
You must be signed in to change notification settings - Fork 51
UE: implement TRS processing in PHY #199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1184,16 +1184,32 @@ void pdsch_processing(PHY_VARS_NR_UE *ue, const UE_nr_rxtx_proc_t *proc, nr_phy_ | |
| } | ||
|
|
||
| // do procedures for CSI-RS | ||
| if (phy_data->csirs_vars.active == 1) { | ||
| for(int symb = 0; symb < ue->frame_parms.symbols_per_slot; symb++) { | ||
| if(is_csi_rs_in_symbol(phy_data->csirs_vars.csirs_config_pdu, symb)) { | ||
| if (!slot_fep_map[symb]) { | ||
| nr_slot_fep(ue, &ue->frame_parms, proc->nr_slot_rx, symb, rxdataF, link_type_dl, 0, ue->common_vars.rxdata); | ||
| slot_fep_map[symb] = true; | ||
| { | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would remove this parenthesis that gives an unnecessary indentation
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I added the parenthesis to minimize the scope of the buffer
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. adding a new scope does not change the stack size in anyway, could you please explain what you mean? or is it to reduce the scope? this has nothing to do with the stack.
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. my understanding is that when the program leaves a scope, it reclaims the stack. so in this case after leaving the scope, the physical memory used by trs_estimates[] could be reused by whatever comes next.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. that is correct, thanks. it makes now sense to me. You could alternatively also create a function, but for me it's fine then. |
||
| /* | ||
| CSI-RS for tracking use only one port. | ||
| Number of CSI-RS resources for tracking is always 2 per slot. | ||
| Computed estimates from first resource is saved and used while estimating second resource. | ||
| */ | ||
| c16_t trs_estimates[ue->frame_parms.nb_antennas_rx][1][ue->frame_parms.ofdm_symbol_size]; | ||
| for (int res = 0; res < MAX_CSI_RES_SLOT; res++) { | ||
| if (phy_data->csirs_vars[res].active == 1) { | ||
| for (int symb = 0; symb < ue->frame_parms.symbols_per_slot; symb++) { | ||
| if (is_csi_rs_in_symbol(phy_data->csirs_vars[res].csirs_config_pdu, symb)) { | ||
| if (!slot_fep_map[symb]) { | ||
| nr_slot_fep(ue, &ue->frame_parms, proc->nr_slot_rx, symb, rxdataF, link_type_dl, 0, ue->common_vars.rxdata); | ||
| slot_fep_map[symb] = true; | ||
| } | ||
| } | ||
| } | ||
| nr_ue_csi_rs_procedures(ue, | ||
| proc, | ||
| rxdataF, | ||
| &phy_data->csirs_vars[res].csirs_config_pdu, | ||
| trs_estimates, | ||
| res, | ||
| (res == 1) ? phy_data->csirs_vars[0].csirs_config_pdu.symb_l0 : -1); | ||
| } | ||
| } | ||
| nr_ue_csi_rs_procedures(ue, proc, rxdataF, &phy_data->csirs_vars.csirs_config_pdu); | ||
| } | ||
|
|
||
| int16_t *llr[2]; | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.