From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Meghana Malladi <m-malladi@ti.com>,
vigneshr@ti.com, javier.carrasco.cruz@gmail.com,
jacob.e.keller@intel.com, diogo.ivo@siemens.com,
horms@kernel.org, richardcochran@gmail.com, pabeni@redhat.com,
kuba@kernel.org, edumazet@google.com, davem@davemloft.net,
andrew+netdev@lunn.ch
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, srk@ti.com,
Roger Quadros <rogerq@kernel.org>,
danishanwar@ti.com
Subject: Re: [PATCH net] net: ti: icss-iep: Reject perout generation request
Date: Thu, 27 Feb 2025 16:06:17 +0000 [thread overview]
Message-ID: <542018d4-ded1-40c6-9a97-d3789877b771@linux.dev> (raw)
In-Reply-To: <20250227092441.1848419-1-m-malladi@ti.com>
On 27/02/2025 09:24, Meghana Malladi wrote:
> IEP driver supports both perout and pps signal generation
> but perout feature is faulty with half-cooked support
> due to some missing configuration. Remove perout
> support from the driver and reject perout requests with
> "not supported" error code.
>
> Fixes: c1e0230eeaab2 ("net: ti: icss-iep: Add IEP driver")
> Signed-off-by: Meghana Malladi <m-malladi@ti.com>
> ---
>
> This patch is a bug fix to disable/remove a faulty feature, which will be
> enabled separately as a feature addition to net-next, as suggested by
> Jakub Kicinski and Jacob Keller:
> https://lore.kernel.org/all/20250220172410.025b96d6@kernel.org/
>
> drivers/net/ethernet/ti/icssg/icss_iep.c | 21 +--------------------
> 1 file changed, 1 insertion(+), 20 deletions(-)
>
> diff --git a/drivers/net/ethernet/ti/icssg/icss_iep.c b/drivers/net/ethernet/ti/icssg/icss_iep.c
> index 768578c0d958..d59c1744840a 100644
> --- a/drivers/net/ethernet/ti/icssg/icss_iep.c
> +++ b/drivers/net/ethernet/ti/icssg/icss_iep.c
> @@ -474,26 +474,7 @@ static int icss_iep_perout_enable_hw(struct icss_iep *iep,
> static int icss_iep_perout_enable(struct icss_iep *iep,
> struct ptp_perout_request *req, int on)
> {
> - int ret = 0;
> -
> - mutex_lock(&iep->ptp_clk_mutex);
> -
> - if (iep->pps_enabled) {
> - ret = -EBUSY;
> - goto exit;
> - }
> -
> - if (iep->perout_enabled == !!on)
> - goto exit;
> -
> - ret = icss_iep_perout_enable_hw(iep, req, on);
> - if (!ret)
> - iep->perout_enabled = !!on;
> -
> -exit:
> - mutex_unlock(&iep->ptp_clk_mutex);
> -
> - return ret;
> + return -EOPNOTSUPP;
> }
>
> static void icss_iep_cap_cmp_work(struct work_struct *work)
>
> base-commit: 29b036be1b0bfcfc958380d5931325997fddf08a
LGTM. It maybe cleaner to remove PTP_CLK_REQ_PEROUT in
icss_iep_ptp_enable as well, but if the idea is to bring the feature
back, then it should be good enough.
Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
next prev parent reply other threads:[~2025-02-27 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 9:24 [PATCH net] net: ti: icss-iep: Reject perout generation request Meghana Malladi
2025-02-27 16:06 ` Vadim Fedorenko [this message]
2025-02-27 16:20 ` 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=542018d4-ded1-40c6-9a97-d3789877b771@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=diogo.ivo@siemens.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-malladi@ti.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rogerq@kernel.org \
--cc=srk@ti.com \
--cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox