All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
	davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, netdev@vger.kernel.org,
	Yochai Hagvi <yochai.hagvi@intel.com>,
	Wojciech Drewek <wojciech.drewek@intel.com>,
	Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
	Sunitha Mekala <sunithax.d.mekala@intel.com>
Subject: Re: [PATCH net 1/6] ice: fix connection state of DPLL and out pin
Date: Thu, 22 Feb 2024 14:22:17 +0100	[thread overview]
Message-ID: <ZddKiZt1-OSAX39M@nanopsycho> (raw)
In-Reply-To: <2d4d91a0-5539-4cc0-850a-3ccd44fcc648@linux.dev>

Thu, Feb 22, 2024 at 01:31:53PM CET, vadim.fedorenko@linux.dev wrote:
>On 20/02/2024 21:44, Tony Nguyen wrote:
>> From: Yochai Hagvi <yochai.hagvi@intel.com>
>> 
>> Fix the connection state between source DPLL and output pin, updating the
>> attribute 'state' of 'parent_device'. Previously, the connection state
>> was broken, and didn't reflect the correct state.
>> 
>> When 'state_on_dpll_set' is called with the value
>> 'DPLL_PIN_STATE_CONNECTED' (1), the output pin will switch to the given
>> DPLL, and the state of the given DPLL will be set to connected.
>> E.g.:
>> 	--do pin-set --json '{"id":2, "parent-device":{"parent-id":1,
>> 						       "state": 1 }}'
>> This command will connect DPLL device with id 1 to output pin with id 2.
>> 
>> When 'state_on_dpll_set' is called with the value
>> 'DPLL_PIN_STATE_DISCONNECTED' (2) and the given DPLL is currently
>> connected, then the output pin will be disabled.
>> E.g:
>> 	--do pin-set --json '{"id":2, "parent-device":{"parent-id":1,
>> 						       "state": 2 }}'
>> This command will disable output pin with id 2 if DPLL device with ID 1 is
>> connected to it; otherwise, the command is ignored.
>> 
>> Fixes: d7999f5ea64b ("ice: implement dpll interface to control cgu")
>> Reviewed-by: Wojciech Drewek <wojciech.drewek@intel.com>
>> Reviewed-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
>> Signed-off-by: Yochai Hagvi <yochai.hagvi@intel.com>
>> Tested-by: Sunitha Mekala <sunithax.d.mekala@intel.com> (A Contingent worker at Intel)
>> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
>> ---
>>   drivers/net/ethernet/intel/ice/ice_dpll.c | 43 +++++++++++++++++------
>>   1 file changed, 32 insertions(+), 11 deletions(-)
>> 
>
>For the series:
>
>Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>

I also find this set okay. Feel free to add my rwb tag as well.

Reviewed-by: Jiri Pirko <jiri@nvidia.com>

  reply	other threads:[~2024-02-22 13:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 21:44 [PATCH net 0/6][pull request] Intel Wired LAN Driver Updates 2024-02-20 (ice) Tony Nguyen
2024-02-20 21:44 ` [PATCH net 1/6] ice: fix connection state of DPLL and out pin Tony Nguyen
2024-02-22 12:31   ` Vadim Fedorenko
2024-02-22 13:22     ` Jiri Pirko [this message]
2024-02-20 21:44 ` [PATCH net 2/6] ice: fix dpll input pin phase_adjust value updates Tony Nguyen
2024-02-20 21:44 ` [PATCH net 3/6] ice: fix dpll and dpll_pin data access on PF reset Tony Nguyen
2024-02-20 21:44 ` [PATCH net 4/6] ice: fix dpll periodic work data updates " Tony Nguyen
2024-02-20 21:44 ` [PATCH net 5/6] ice: fix pin phase adjust " Tony Nguyen
2024-02-20 21:44 ` [PATCH net 6/6] ice: Fix ASSERT_RTNL() warning during certain scenarios Tony Nguyen
2024-02-23  3:30 ` [PATCH net 0/6][pull request] Intel Wired LAN Driver Updates 2024-02-20 (ice) patchwork-bot+netdevbpf

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=ZddKiZt1-OSAX39M@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=anthony.l.nguyen@intel.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sunithax.d.mekala@intel.com \
    --cc=vadim.fedorenko@linux.dev \
    --cc=wojciech.drewek@intel.com \
    --cc=yochai.hagvi@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.