From: Sergey Lisov <sleirsgoevy@gmail.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: synopsys-dw-mshc-common: add "fifo-access-32bit" property
Date: Sun, 12 Mar 2023 04:48:33 -0700 (PDT) [thread overview]
Message-ID: <640dbc11.c20a0220.d7aba.1818@mx.google.com> (raw)
In-Reply-To: <951dec3a-1a3e-6d17-20fb-9e5915606c40@linaro.org>
> ... and should not be. It should come with a specific compatible
> followed by this fallback. The specific compatible then will define
> 32-bit access.
OK, I'll then make a new revision with this baked into a compatible
string.
next prev parent reply other threads:[~2023-03-12 11:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <640db6ef.2e0a0220.9d4ba.1500@mx.google.com>
2023-03-12 11:34 ` [PATCH v2 1/2] dt-bindings: synopsys-dw-mshc-common: add "fifo-access-32bit" property Krzysztof Kozlowski
2023-03-12 11:48 ` Sergey Lisov [this message]
2023-03-12 11:48 ` Sergey Lisov
2023-03-12 11:48 ` Sergey Lisov
[not found] <640db0e7.c20a0220.babe.16cb@mx.google.com>
2023-03-12 11:13 ` Krzysztof Kozlowski
2023-03-12 11:26 ` Sergey Lisov
2023-03-12 11:26 ` Sergey Lisov
2023-03-12 11:26 ` Sergey Lisov
[not found] <640dae27.2e0a0220.d5632.151c@mx.google.com>
2023-03-12 10:53 ` Krzysztof Kozlowski
2023-03-12 11:00 ` Sergey Lisov
2023-03-12 11:00 ` Sergey Lisov
2023-03-12 11:01 ` Sergey Lisov
2023-03-11 18:15 [PATCH v2 0/2] mmc: dw_mmc: fix DW MMC cores with 32-bit bus on 64-bit Linux systems Sergey Lisov
2023-03-11 18:15 ` [PATCH v2 1/2] dt-bindings: synopsys-dw-mshc-common: add "fifo-access-32bit" property Sergey Lisov
2023-03-12 10:18 ` Krzysztof Kozlowski
2023-03-12 10:42 ` Krzysztof Kozlowski
2023-03-12 10:49 ` Sergey Lisov
2023-03-12 10:49 ` Sergey Lisov
2023-03-12 10:49 ` Sergey Lisov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=640dbc11.c20a0220.d7aba.1818@mx.google.com \
--to=sleirsgoevy@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jh80.chung@samsung.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.