[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230711131443.2a4af476@kernel.org>
Date: Tue, 11 Jul 2023 13:14:43 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@...el.com>
Cc: Jiri Pirko <jiri@...nulli.us>, "vadfed@...a.com" <vadfed@...a.com>,
"jonathan.lemon@...il.com" <jonathan.lemon@...il.com>, "pabeni@...hat.com"
<pabeni@...hat.com>, "corbet@....net" <corbet@....net>,
"davem@...emloft.net" <davem@...emloft.net>, "edumazet@...gle.com"
<edumazet@...gle.com>, "vadfed@...com" <vadfed@...com>, "Brandeburg, Jesse"
<jesse.brandeburg@...el.com>, "Nguyen, Anthony L"
<anthony.l.nguyen@...el.com>, "M, Saeed" <saeedm@...dia.com>,
"leon@...nel.org" <leon@...nel.org>, "richardcochran@...il.com"
<richardcochran@...il.com>, "sj@...nel.org" <sj@...nel.org>,
"javierm@...hat.com" <javierm@...hat.com>, "ricardo.canuelo@...labora.com"
<ricardo.canuelo@...labora.com>, "mst@...hat.com" <mst@...hat.com>,
"tzimmermann@...e.de" <tzimmermann@...e.de>, "Michalik, Michal"
<michal.michalik@...el.com>, "gregkh@...uxfoundation.org"
<gregkh@...uxfoundation.org>, "jacek.lawrynowicz@...ux.intel.com"
<jacek.lawrynowicz@...ux.intel.com>, "airlied@...hat.com"
<airlied@...hat.com>, "ogabbay@...nel.org" <ogabbay@...nel.org>,
"arnd@...db.de" <arnd@...db.de>, "nipun.gupta@....com"
<nipun.gupta@....com>, "axboe@...nel.dk" <axboe@...nel.dk>, "linux@...y.sk"
<linux@...y.sk>, "masahiroy@...nel.org" <masahiroy@...nel.org>,
"benjamin.tissoires@...hat.com" <benjamin.tissoires@...hat.com>,
"geert+renesas@...der.be" <geert+renesas@...der.be>, "Olech, Milena"
<milena.olech@...el.com>, "kuniyu@...zon.com" <kuniyu@...zon.com>,
"liuhangbin@...il.com" <liuhangbin@...il.com>, "hkallweit1@...il.com"
<hkallweit1@...il.com>, "andy.ren@...cruise.com" <andy.ren@...cruise.com>,
"razor@...ckwall.org" <razor@...ckwall.org>, "idosch@...dia.com"
<idosch@...dia.com>, "lucien.xin@...il.com" <lucien.xin@...il.com>,
"nicolas.dichtel@...nd.com" <nicolas.dichtel@...nd.com>, "phil@....cc"
<phil@....cc>, "claudiajkang@...il.com" <claudiajkang@...il.com>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, poros <poros@...hat.com>, mschmidt
<mschmidt@...hat.com>, "linux-clk@...r.kernel.org"
<linux-clk@...r.kernel.org>, "vadim.fedorenko@...ux.dev"
<vadim.fedorenko@...ux.dev>
Subject: Re: [RFC PATCH v9 00/10] Create common DPLL configuration API
On Tue, 11 Jul 2023 17:17:51 +0000 Kubalewski, Arkadiusz wrote:
> >I think better to add the check to pin-register so future synce pin
> >users don't have similar weird ideas. Could you please add this check?
>
> Don't think it is way to go, and I don't think there is anything good
> with preventing device drivers from labeling their pins the way they want.
We had a long argument about how label should have a clearly defined
meaning. We're not going to rehash it on every revision. What did
I miss :|
Powered by blists - more mailing lists