On Thu, 2024-12-12 at 13:23 +0100, Krzysztof Kozlowski wrote: > External email : Please do not click links or open attachments until > you have verified the sender or the content. > > > On 12/12/2024 12:24, Jason-JH Lin (林睿祥) wrote: > > > > > > > > > > On Wed, Dec 11, 2024 at 11:22:49AM +0800, Jason-JH.Lin wrote: > > > > > > Add the Global Command Engine (GCE) header file to define > > > > > > the > > > > > > GCE > > > > > > thread priority, GCE subsys ID and GCE events for MT8196. > > > > > > > > > > This we see from the diff. What we do not see is why priority > > > > > is > > > > > a > > > > > binding. Looking briefly at existing code: it is not a > > > > > binding, > > > > > there > > > > > is > > > > > no driver user. > > > > > > > > > > > > > This priority value is used to configure the priority level for > > > > each > > > > GCE hardware thread, so it is a necessary hardware attribute. > > > > > > I did not say these are not "hardware". I said these are not > > > bindings. > > > Bring arguments why these are bindings. > > > > > > > Not only bringing arguments, we use it to configure each GCE > > thread's > > priority. > > > > Please forgive me to ask a trivial question. > > Do you mean if there is no driver using it directly, then it can > > not be > > a binding? > > Here: > <qqqwdzmcnkuga6qvvszgg7o2myb26sld5i37e4konhln2n4cgc@mwtropwj3ywv> > Your reply in this example is really clear: Register values are not bindings, they do not bind anything. Bindings are imaginary numbers starting from 0 or 1 which are used between drivers and DTS, serving as abstraction layer (or abstraction values) between these two. Now I can understand what the binding should be. Thank you very much.
