From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793962221; b=w8Jzf/5bHPJwWO5wZk7fzXuFFb9Z23LveUcsxDyud9oFo+6snHEJ7oaKvdakPmHcau2a /He6QPI8PM01gExAvEKnDpVcSM5lojFogfvLnl91q7LueyV8OJhKh0DakIGYb17u0QL5A 1PxU9p46YkpghU/I7WmM+VcSZI3Q44tMXnGbZqeNFGMRCUg9ZMqyEusgy/3aMYDsx9Re7 sfE+xsGIGqDTK9r4Jz8I5tvuO7pfhOUYkkcb/6Qs1U3bbkxt1agdYhxmnSB02h/roxOO/ AYeUTAAFLW8ScT/e/7gnB7LdU77b3MCU+a0zMgXloA8kiTzq2edzHOJZtScbUaPAYHw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793962221; h=DMARC-Filter:DKIM-Signature:Received:X-MC-Unique: X-Mimecast-MFC-AGG-ID:Received:Received:Message-ID:Date:MIME-Version: User-Agent:Subject:To:Cc:References:Content-Language:From:In-Reply-To: Content-Type:Content-Transfer-Encoding:X-Scanned-By; bh=JoGxU1FmWoIU8UQ+roEGVXwQfBtIFU5DeEvnVZCDq6k=; b=x4dS0t2gjXJ2yKRwgBv1eya3mYKZhrycVQn4RZdqrALabVBlWFNTWOePVc+SBKZWq0/d zjDlDfJPxBhDzZBi7/swdaR5Ij5G2Dcspw54MVBqRX6YW+hqMRH1JEZwS674GGJrq2XtH ZWHtYtQMxIeNcbpXBQG49RSskqB+rcVn2uNZg472YrZ7qSgRg5QdaWR/fnC13YJYh6U0M rYG6plexk9BoKGb5esU6woGgJOonf1fiF3zgYPK2n7uSfQE8+oZ3AMZKo1GP8eMgJ5Rpv nKPwFGj2EKEtVcurWc3sbkjDqCBNnvOKuW2lBCSFJjgNDrrrZ6VZxKieu4wgWA6WEuA== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=XJ16e9mI; arc=none smtp.remote-ip=170.10.129.124 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 29AF4606D81F for ; Fri, 6 Nov 2026 10:50:21 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 29AF4606D81F Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=XJ16e9mI DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1793962220; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=JoGxU1FmWoIU8UQ+roEGVXwQfBtIFU5DeEvnVZCDq6k=; b=XJ16e9mIAazTFj0jdmVbFWDj6hec4SIHSHCGVTsCQugOnIdfErtU0kug5dcb9ii1rmFvKo Fe+0c11CpeN9aOpWUxz6AhW9cAB6uvf0vLn3a7YYj7Vspnut5WywsQRsRGGlh3Dz2QrsJ2 2EHlFMv5OgirRE36MeMYGXZtDV+vrOs= Received: from mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-471-dYFMcNNNNEWLqLiCwqSYaA-1; Fri, 06 Nov 2026 05:50:16 -0500 X-MC-Unique: dYFMcNNNNEWLqLiCwqSYaA-1 X-Mimecast-MFC-AGG-ID: dYFMcNNNNEWLqLiCwqSYaA_1793962214 Received: from mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id ADF391955F54; Fri, 6 Nov 2026 10:50:13 +0000 (UTC) Received: from [100.91.101.41] (headnet04.pony-001.prod.iad2.dc.redhat.com [10.2.32.116]) by mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id AA1F81800480; Fri, 6 Nov 2026 10:50:09 +0000 (UTC) Message-ID: <8650a441-1c03-4b3a-aabc-13e047831ff2@redhat.com> Date: Fri, 6 Nov 2026 11:50:08 +0100 X-Mailing-List: netdev@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH net-next v2 08/14] selftests: dpll: add pin priority test To: Petr Oros , netdev@vger.kernel.org Cc: Jonathan Corbet , Shuah Khan , Shuah Khan , Randy Dunlap , Jani Nikula , Vadim Fedorenko , Arkadiusz Kubalewski , Jiri Pirko , Andrew Lunn , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org References: <20261105151852.1844305-1-poros@redhat.com> <20261105151852.1844305-9-poros@redhat.com> Content-Language: en-US From: Ivan Vecera In-Reply-To: <20261105151852.1844305-9-poros@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.93 On 11/5/26 16:18, Petr Oros wrote: > Add a test that sets a new priority on an input pin, reads it back and > restores the original value. The range of priorities a device accepts is > not advertised over netlink, so the test tries one below the current > value and then the small values every driver accepts, since a large > current value may mark an unused pin outside the settable range, as the > ice driver does with 255. A driver may still refuse all of them for a > constraint the interface does not tell, so that is a skip on a device > provided by the user, with the reason the tool reported, and a failure > on the device the script created, whose simulator accepts every > priority. The test skips when the dpll tool lacks the prio keyword of > pin set, and the restore is deferred right after the original value is > read so that an interrupted run restores it too. A pin that does not > advertise the priority-can-change capability or does not report a > priority is a skip on a device provided by the user and a failure on the > device the script created, whose pins have both. > > The dpllsim_add_pin helper gains an optional priority argument, which is > written only when it is given, so that a pin without one keeps the > default of the simulator. A priority is accepted for input pins only, > so the callers pass one for those alone. > > The standard device lays its inputs out as gnss0 with priority 0 and > ext0 with priority 1, and the stress devices get random priorities on > their input pins. > > Signed-off-by: Petr Oros Reviewed-by: Ivan Vecera