Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keller, Jacob E <jacob.e.keller@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [net-next PATCH v2 2/9] ice: PTP: move setting of tstamp_config
Date: Tue, 12 Oct 2021 17:39:09 +0000	[thread overview]
Message-ID: <7e70c127-5e4b-c5a1-63f9-0d891268c146@intel.com> (raw)
In-Reply-To: <97277fe9-ab9a-78c6-2456-1dfe643f69e9@molgen.mpg.de>

On 10/12/2021 1:10 AM, Paul Menzel wrote:
> Dear Jacob,
> 
> 
> Am 12.10.21 um 03:07 schrieb Jacob Keller:
>> The tstamp_config structure is being set inside of
>> ice_ptp_cfg_timestamp, which is the function used to set Tx and
>> Rx timestamping during initialization.
>>
>> This function is also used in order to set the PHY port timestamping
>> status. However, it makes sense to always set the tstamp_config directly
>> whenever the ice_set_tx_tstamp or ice_set_rx_tstamp functions are
>> called.
>>
>> Move assignment of tstamp_config into the related functions and out of
>> ice_ptp_cfg_timestamp.
>>
>> Now that we assign the timestamp mode in the relevant functions, we no
>> longer modify the config valuie in ice_set_timestamp_mode. In turn, we
> 
> Nit: value

Oops.

> 
>> no longer want to copy that config value into the PF cached structure.
>> Instead, this is now the source of truth for actual configuration. On
>> success of ice_set_timestamp_mode, copy the real configured mode back to
>> report it out to userspace.
>>
>> Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
>> ---
>>   drivers/net/ethernet/intel/ice/ice_ptp.c | 23 ++++++++++++-----------
>>   1 file changed, 12 insertions(+), 11 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/intel/ice/ice_ptp.c b/drivers/net/ethernet/intel/ice/ice_ptp.c
>> index 71e715c7be4f..155842447ebe 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_ptp.c
>> +++ b/drivers/net/ethernet/intel/ice/ice_ptp.c
>> @@ -285,6 +285,11 @@ static void ice_set_tx_tstamp(struct ice_pf *pf, bool on)
>>   	else
>>   		val &= ~PFINT_OICR_TSYN_TX_M;
>>   	wr32(&pf->hw, PFINT_OICR_ENA, val);
>> +
>> +	if (on)
>> +		pf->ptp.tstamp_config.tx_type = HWTSTAMP_TX_ON;
>> +	else
>> +		pf->ptp.tstamp_config.tx_type = HWTSTAMP_TX_OFF;
> 
> I?d use the ternary operator:
> >      pf->ptp.tstamp_config.tx_type = on ? HWTSTAMP_TX_ON :
HWTSTAMP_TX_OFF;
> 

Yea that would work. I can change it if there's another reason to fix up
the series. I think I had it the other way because of existing code I
was moving used a simple if statement.

>>   }
>>   
>>   /**
>> @@ -307,6 +312,11 @@ static void ice_set_rx_tstamp(struct ice_pf *pf, bool on)
>>   			continue;
>>   		vsi->rx_rings[i]->ptp_rx = on;
>>   	}
>> +
>> +	if (on)
>> +		pf->ptp.tstamp_config.rx_filter = HWTSTAMP_FILTER_ALL;
>> +	else
>> +		pf->ptp.tstamp_config.rx_filter = HWTSTAMP_FILTER_NONE;
>>   }
>>   

Same here obviously.

>>   /**
>> @@ -321,14 +331,6 @@ static void ice_ptp_cfg_timestamp(struct ice_pf *pf, bool ena)
>>   {
>>   	ice_set_tx_tstamp(pf, ena);
>>   	ice_set_rx_tstamp(pf, ena);
>> -
>> -	if (ena) {
>> -		pf->ptp.tstamp_config.rx_filter = HWTSTAMP_FILTER_ALL;
>> -		pf->ptp.tstamp_config.tx_type = HWTSTAMP_TX_ON;
>> -	} else {
>> -		pf->ptp.tstamp_config.rx_filter = HWTSTAMP_FILTER_NONE;
>> -		pf->ptp.tstamp_config.tx_type = HWTSTAMP_TX_OFF;
>> -	}
>>   }
>>   
>>   /**
>> @@ -1256,7 +1258,6 @@ ice_ptp_set_timestamp_mode(struct ice_pf *pf, struct hwtstamp_config *config)
>>   	case HWTSTAMP_FILTER_PTP_V2_L4_DELAY_REQ:
>>   	case HWTSTAMP_FILTER_NTP_ALL:
>>   	case HWTSTAMP_FILTER_ALL:
>> -		config->rx_filter = HWTSTAMP_FILTER_ALL;
>>   		ice_set_rx_tstamp(pf, true);
>>   		break;
>>   	default:
>> @@ -1288,8 +1289,8 @@ int ice_ptp_set_ts_config(struct ice_pf *pf, struct ifreq *ifr)
>>   	if (err)
>>   		return err;
>>   
>> -	/* Save these settings for future reference */
>> -	pf->ptp.tstamp_config = config;
>> +	/* Return the actual configuration set */
>> +	config = pf->ptp.tstamp_config;
>>   
>>   	return copy_to_user(ifr->ifr_data, &config, sizeof(config)) ?
>>   		-EFAULT : 0;
>>
> 
> Acked-by: Paul Menzel <pmenzel@molgen.mpg.de>
> 

I don't think the change to ternary construct is worth the re-roll. If
there's a reason to re-roll this series, I've noted these comments down.

Thanks!

-Jake

> 
> Kind regards,
> 
> Paul
> 


  reply	other threads:[~2021-10-12 17:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12  1:07 [Intel-wired-lan] [net-next PATCH v2 0/9] implement support for PTP on E822 hardware Jacob Keller
2021-10-12  1:07 ` [Intel-wired-lan] [net-next PATCH v2 1/9] ice: introduce ice_base_incval function Jacob Keller
2021-10-12  1:07 ` [Intel-wired-lan] [net-next PATCH v2 2/9] ice: PTP: move setting of tstamp_config Jacob Keller
2021-10-12  8:10   ` Paul Menzel
2021-10-12 17:39     ` Keller, Jacob E [this message]
2021-10-12  1:07 ` [Intel-wired-lan] [net-next PATCH v2 3/9] ice: use 'int err' instead of 'int status' in ice_ptp_hw.c Jacob Keller
2021-10-12  1:07 ` [Intel-wired-lan] [net-next PATCH v2 4/9] ice: introduce ice_ptp_init_phc function Jacob Keller
2021-10-12  8:23   ` Paul Menzel
2021-10-12 17:34     ` Keller, Jacob E
2021-10-12  1:07 ` [Intel-wired-lan] [net-next PATCH v2 5/9] ice: convert clk_freq capability into time_ref Jacob Keller
2021-10-12  1:07 ` [Intel-wired-lan] [net-next PATCH v2 6/9] ice: implement basic E822 PTP support Jacob Keller
2021-10-12  1:07 ` [Intel-wired-lan] [net-next PATCH v2 7/9] ice: ensure the hardware Clock Generation Unit is configured Jacob Keller
2021-10-12  1:07 ` [Intel-wired-lan] [net-next PATCH v2 8/9] ice: exit bypass mode once hardware finishes timestamp calibration Jacob Keller
2021-10-12  1:07 ` [Intel-wired-lan] [net-next PATCH v2 9/9] ice: support crosstimestamping on E822 devices if supported Jacob Keller
2021-10-12 21:29 ` [Intel-wired-lan] [net-next PATCH v2 0/9] implement support for PTP on E822 hardware Keller, Jacob E

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7e70c127-5e4b-c5a1-63f9-0d891268c146@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox