[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Thu, 2 Feb 2023 13:51:51 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: William Qiu <william.qiu@...rfivetech.com>
Cc: linux-riscv@...ts.infradead.org, devicetree@...r.kernel.org,
linux-mmc@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Jaehoon Chung <jh80.chung@...sung.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 2/3] mmc: starfive: Add sdio/emmc driver support
On Thu, Feb 2, 2023 at 12:10 PM William Qiu
<william.qiu@...rfivetech.com> wrote:
> On 2022/12/9 5:09, Linus Walleij wrote:
> >> + priv->syscon_offset = args.args[0];
> >> + priv->syscon_shift = args.args[1];
> >> + priv->syscon_mask = args.args[2];
> >
> > Why should these three things be in the device tree instead of being derived
> > from the compatible-string or just plain hard-coded as #defines?
> > I don't get it.
> >
> Hi Linus,
>
> I'm sorry to bother you, but as for the definition of syscon, after discussing with
> my colleagues, we think it is easier to distinguish SDIO0 and SDIO1 by defining it in
> the device tree, and the code compatibility is better.
OK sounds good looking forward to seeing the result :)
Yours,
Linus Walleij
Powered by blists - more mailing lists