[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEev2e-iAN+br0wa8dXSyjTgh=vNCyqwxo42EaksCjXOdzeFWw@mail.gmail.com>
Date: Fri, 16 Jan 2026 15:34:10 -0600
From: Anirudh Srinivasan <asrinivasan@....tenstorrent.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Drew Fustini <dfustini@....tenstorrent.com>, Joel Stanley <jms@....tenstorrent.com>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Michael Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>,
Philipp Zabel <p.zabel@...gutronix.de>, linux-riscv@...ts.infradead.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-clk@...r.kernel.org, joel@....id.au, fustini@...nel.org, mpe@...nel.org,
mpe@....tenstorrent.com, npiggin@....tenstorrent.com, agross@...nel.org,
agross@....tenstorrent.com
Subject: Re: [PATCH 2/8] soc: tenstorrent: Add header with Atlantis syscon
register offsets
Hi Krzysztof,
On Fri, Jan 16, 2026 at 3:06 AM Krzysztof Kozlowski <krzk@...nel.org> wrote:
>
>
> There is no user of this. Split your work in logical patches. Adding
> unused header is not a meaningful logical split because it is unused.
Understood
>
> Completely unreadable: missing any sort of reasonable indent between
> values.
I had formatted these with clang-format, but it doesn't look good. I
can make it a bit better.
>
> Why do you need to doicument register values and provide them to all
> kernel drivers?
(Including the subsequent commits), these registers documented in this
file are shared across the clock and reset controller, so they're
added here (soc/tenstorrent).
Powered by blists - more mailing lists