Message ID | 20241120075112.1662138-1-arkadiusz.kubalewski@intel.com |
---|---|
State | Accepted |
Delegated to: | Anthony Nguyen |
Headers | show |
Series | [iwl-net] ice: fix max values for dpll pin phase adjust | expand |
> -----Original Message----- > From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of Arkadiusz Kubalewski > Sent: 20 November 2024 13:21 > To: intel-wired-lan@lists.osuosl.org > Cc: netdev@vger.kernel.org; Kubalewski, Arkadiusz <arkadiusz.kubalewski@intel.com>; Kitszel, Przemyslaw <przemyslaw.kitszel@intel.com> > Subject: [Intel-wired-lan] [PATCH iwl-net] ice: fix max values for dpll pin phase adjust > > Mask admin command returned max phase adjust value for both input and output pins. Only 31 bits are relevant, last released data sheet wrongly points that 32 bits are valid - see [1] 3.2.6.4.1 Get CCU > Capabilities Command for reference. Fix of the datasheet itself is in progress. > > Fix the min/max assignment logic, previously the value was wrongly considered as negative value due to most significant bit being set. > > Example of previous broken behavior: > $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ --do pin-get --json '{"id":1}'| grep phase-adjust > 'phase-adjust': 0, > 'phase-adjust-max': 16723, > 'phase-adjust-min': -16723, > > Correct behavior with the fix: > $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ --do pin-get --json '{"id":1}'| grep phase-adjust > 'phase-adjust': 0, > 'phase-adjust-max': 2147466925, > 'phase-adjust-min': -2147466925, > > [1] https://cdrdv2.intel.com/v1/dl/getContent/613875?explicitVersion=true > > Fixes: 90e1c90750d7 ("ice: dpll: implement phase related callbacks") > Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com> > Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com> > --- > .../net/ethernet/intel/ice/ice_adminq_cmd.h | 2 ++ > drivers/net/ethernet/intel/ice/ice_dpll.c | 35 ++++++++++++------- > 2 files changed, 25 insertions(+), 12 deletions(-) > Tested-by: Pucha Himasekhar Reddy <himasekharx.reddy.pucha@intel.com> (A Contingent worker at Intel)
On Wed, Nov 20, 2024 at 08:51:12AM +0100, Arkadiusz Kubalewski wrote: > Mask admin command returned max phase adjust value for both input and > output pins. Only 31 bits are relevant, last released data sheet wrongly > points that 32 bits are valid - see [1] 3.2.6.4.1 Get CCU Capabilities > Command for reference. Fix of the datasheet itself is in progress. > > Fix the min/max assignment logic, previously the value was wrongly > considered as negative value due to most significant bit being set. Thanks Arkadiusz, I understand the most-significant-bit issue and see that is addressed through the use of ICE_AQC_GET_CGU_MAX_PHASE_ADJ. I also agree that this is a fix. But, although I like simplification afforded ice_dpll_phase_range_set() I'm not convinced it is a part of the fix. Does the code behave correctly without those changes? If so, I'm wondering if that part should be broken out into a separate follow-up patch for iwl. > > Example of previous broken behavior: > $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ > --do pin-get --json '{"id":1}'| grep phase-adjust > 'phase-adjust': 0, > 'phase-adjust-max': 16723, > 'phase-adjust-min': -16723, I'm curious to know if the values for max and min above are inverted. I.e. if, sude to the most-significant-bit issue they are: 'phase-adjust-max': -16723, 'phase-adjust-min': 16723, > > Correct behavior with the fix: > $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ > --do pin-get --json '{"id":1}'| grep phase-adjust > 'phase-adjust': 0, > 'phase-adjust-max': 2147466925, > 'phase-adjust-min': -2147466925, > > [1] https://cdrdv2.intel.com/v1/dl/getContent/613875?explicitVersion=true > > Fixes: 90e1c90750d7 ("ice: dpll: implement phase related callbacks") > Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com> > Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com> ...
>From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of >Simon Horman >Sent: Tuesday, December 3, 2024 11:05 AM > >On Wed, Nov 20, 2024 at 08:51:12AM +0100, Arkadiusz Kubalewski wrote: >> Mask admin command returned max phase adjust value for both input and >> output pins. Only 31 bits are relevant, last released data sheet wrongly >> points that 32 bits are valid - see [1] 3.2.6.4.1 Get CCU Capabilities >> Command for reference. Fix of the datasheet itself is in progress. >> >> Fix the min/max assignment logic, previously the value was wrongly >> considered as negative value due to most significant bit being set. > >Thanks Arkadiusz, > >I understand the most-significant-bit issue and see that is addressed >through the use of ICE_AQC_GET_CGU_MAX_PHASE_ADJ. I also agree that this is >a fix. > >But, although I like simplification afforded ice_dpll_phase_range_set() >I'm not convinced it is a part of the fix. Does the code behave correctly >without those changes? If so, I'm wondering if that part should be broken >out into a separate follow-up patch for iwl. > Hi Simon, Thank you for the review! Well, the extra helper function was introduced as part of review. But the logic shall be fixed anyway (negative is min/positive max), as implemented within the new function - different then original code. So yes, we could remove addition of the helper function from this patch, and just fix the logic in 2 lines function is called. I believe having it is simpler to maintain for the future. But won't argue about, please just let me know what you think, if you still want it separated, will do. >> >> Example of previous broken behavior: >> $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ >> --do pin-get --json '{"id":1}'| grep phase-adjust >> 'phase-adjust': 0, >> 'phase-adjust-max': 16723, >> 'phase-adjust-min': -16723, > >I'm curious to know if the values for max and min above are inverted. >I.e. if, sude to the most-significant-bit issue they are: > Yes, initially they were wrongly inverted in driver, since the driver was also using the most significant bit made - the value was negative. Thank you! Arkadiusz > 'phase-adjust-max': -16723, > 'phase-adjust-min': 16723, > >> >> Correct behavior with the fix: >> $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ >> --do pin-get --json '{"id":1}'| grep phase-adjust >> 'phase-adjust': 0, >> 'phase-adjust-max': 2147466925, >> 'phase-adjust-min': -2147466925, >> >> [1] https://cdrdv2.intel.com/v1/dl/getContent/613875?explicitVersion=true >> >> Fixes: 90e1c90750d7 ("ice: dpll: implement phase related callbacks") >> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com> >> Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com> > >...
diff --git a/drivers/net/ethernet/intel/ice/ice_adminq_cmd.h b/drivers/net/ethernet/intel/ice/ice_adminq_cmd.h index 547c96b9c1d5..80f3dfd27124 100644 --- a/drivers/net/ethernet/intel/ice/ice_adminq_cmd.h +++ b/drivers/net/ethernet/intel/ice/ice_adminq_cmd.h @@ -2239,6 +2239,8 @@ struct ice_aqc_get_pkg_info_resp { struct ice_aqc_get_pkg_info pkg_info[]; }; +#define ICE_AQC_GET_CGU_MAX_PHASE_ADJ GENMASK(30, 0) + /* Get CGU abilities command response data structure (indirect 0x0C61) */ struct ice_aqc_get_cgu_abilities { u8 num_inputs; diff --git a/drivers/net/ethernet/intel/ice/ice_dpll.c b/drivers/net/ethernet/intel/ice/ice_dpll.c index d5ad6d84007c..38e151c7ea23 100644 --- a/drivers/net/ethernet/intel/ice/ice_dpll.c +++ b/drivers/net/ethernet/intel/ice/ice_dpll.c @@ -2064,6 +2064,18 @@ static int ice_dpll_init_worker(struct ice_pf *pf) return 0; } +/** + * ice_dpll_phase_range_set - initialize phase adjust range helper + * @range: pointer to phase adjust range struct to be initialized + * @phase_adj: a value to be used as min(-)/max(+) boundary + */ +static void ice_dpll_phase_range_set(struct dpll_pin_phase_adjust_range *range, + u32 phase_adj) +{ + range->min = -phase_adj; + range->max = phase_adj; +} + /** * ice_dpll_init_info_pins_generic - initializes generic pins info * @pf: board private structure @@ -2105,8 +2117,8 @@ static int ice_dpll_init_info_pins_generic(struct ice_pf *pf, bool input) for (i = 0; i < pin_num; i++) { pins[i].idx = i; pins[i].prop.board_label = labels[i]; - pins[i].prop.phase_range.min = phase_adj_max; - pins[i].prop.phase_range.max = -phase_adj_max; + ice_dpll_phase_range_set(&pins[i].prop.phase_range, + phase_adj_max); pins[i].prop.capabilities = cap; pins[i].pf = pf; ret = ice_dpll_pin_state_update(pf, &pins[i], pin_type, NULL); @@ -2152,6 +2164,7 @@ ice_dpll_init_info_direct_pins(struct ice_pf *pf, struct ice_hw *hw = &pf->hw; struct ice_dpll_pin *pins; unsigned long caps; + u32 phase_adj_max; u8 freq_supp_num; bool input; @@ -2159,11 +2172,13 @@ ice_dpll_init_info_direct_pins(struct ice_pf *pf, case ICE_DPLL_PIN_TYPE_INPUT: pins = pf->dplls.inputs; num_pins = pf->dplls.num_inputs; + phase_adj_max = pf->dplls.input_phase_adj_max; input = true; break; case ICE_DPLL_PIN_TYPE_OUTPUT: pins = pf->dplls.outputs; num_pins = pf->dplls.num_outputs; + phase_adj_max = pf->dplls.output_phase_adj_max; input = false; break; default: @@ -2188,19 +2203,13 @@ ice_dpll_init_info_direct_pins(struct ice_pf *pf, return ret; caps |= (DPLL_PIN_CAPABILITIES_PRIORITY_CAN_CHANGE | DPLL_PIN_CAPABILITIES_STATE_CAN_CHANGE); - pins[i].prop.phase_range.min = - pf->dplls.input_phase_adj_max; - pins[i].prop.phase_range.max = - -pf->dplls.input_phase_adj_max; } else { - pins[i].prop.phase_range.min = - pf->dplls.output_phase_adj_max; - pins[i].prop.phase_range.max = - -pf->dplls.output_phase_adj_max; ret = ice_cgu_get_output_pin_state_caps(hw, i, &caps); if (ret) return ret; } + ice_dpll_phase_range_set(&pins[i].prop.phase_range, + phase_adj_max); pins[i].prop.capabilities = caps; ret = ice_dpll_pin_state_update(pf, &pins[i], pin_type, NULL); if (ret) @@ -2308,8 +2317,10 @@ static int ice_dpll_init_info(struct ice_pf *pf, bool cgu) dp->dpll_idx = abilities.pps_dpll_idx; d->num_inputs = abilities.num_inputs; d->num_outputs = abilities.num_outputs; - d->input_phase_adj_max = le32_to_cpu(abilities.max_in_phase_adj); - d->output_phase_adj_max = le32_to_cpu(abilities.max_out_phase_adj); + d->input_phase_adj_max = le32_to_cpu(abilities.max_in_phase_adj) & + ICE_AQC_GET_CGU_MAX_PHASE_ADJ; + d->output_phase_adj_max = le32_to_cpu(abilities.max_out_phase_adj) & + ICE_AQC_GET_CGU_MAX_PHASE_ADJ; alloc_size = sizeof(*d->inputs) * d->num_inputs; d->inputs = kzalloc(alloc_size, GFP_KERNEL);