[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL_JsqJgo0pKJjrs2fdw+q=DJYwht0X5L3Bomz8gf98mEN7hkg@mail.gmail.com>
Date: Mon, 19 Feb 2018 12:29:24 -0600
From: Rob Herring <robh+dt@...nel.org>
To: Ryder Lee <ryder.lee@...iatek.com>
Cc: Stephen Boyd <sboyd@...eaurora.org>,
Mark Brown <broonie@...nel.org>,
Lee Jones <lee.jones@...aro.org>,
Matthias Brugger <matthias.bgg@...il.com>,
linux-mediatek@...ts.infradead.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
devicetree@...r.kernel.org,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
linux-clk <linux-clk@...r.kernel.org>,
Garlic Tseng <garlic.tseng@...iatek.com>
Subject: Re: [PATCH v3 4/5] dt-bindings: clock: mediatek: update audsys
documentation to adapt MFD device
On Mon, Feb 12, 2018 at 5:28 AM, Ryder Lee <ryder.lee@...iatek.com> wrote:
> The MediaTek audio hardware block that exposes functionalities that are
> handled by separate subsystems in the kernel. These functions are all
> mapped somewhere at 0x112xxxxx, and there are some control bits are mixed
> up with other functions within the same registers.
I still don't think this change is necessary.
Just because a hardware block in DT maps to different subsystems in a
particular OS doesn't mean you need a DT node for each OS subsystem.
What we have subsystems for changes over time and DT shouldn't really
be changing based on that. And DT is not the only way to instantiate
drivers.
Rob
Powered by blists - more mailing lists