From: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Patrice CHOTARD <patrice.chotard-qxv4g6HH51o@public.gmane.org>
Cc: Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>,
Ulf Hansson <ulf.hansson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Michael Turquette
<mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Alexandre TORGUE <alexandre.torgue-qxv4g6HH51o@public.gmane.org>,
linux-mmc <linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-clk <linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux ARM
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Andrea Merello
<andrea.merello-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 04/14] mmc: mmci: Add STM32 variant
Date: Tue, 16 Jan 2018 08:38:33 +0100 [thread overview]
Message-ID: <CACRpkdY88umqVBcFNy7Z6vgHztRr7MbAjh-AWz0nYgFXoOwCLQ@mail.gmail.com> (raw)
In-Reply-To: <ce14077b-2b8b-f8a7-2107-78b1d9dcab27-qxv4g6HH51o@public.gmane.org>
On Mon, Jan 15, 2018 at 6:17 PM, Patrice CHOTARD <patrice.chotard-qxv4g6HH51o@public.gmane.org> wrote:
>>> + {
>>> + .id = 0x00880180,
>>> + .mask = 0x00ffffff,
>>> + .data = &variant_stm32,
>>> + },
>>
>> Since ux500 was 480180 I wonder what variants 5,6,7 are...
>
> What is the rule to define the id ?
These four bits mean "revision".
The number comes from hardware, so the ST ASIC department
has some person who is responsible for revising the VHDL or
Verilog code that this hardware is compiled from, and that person
is bumping the version.
Theoretically it is a "company function" or something bureaucratic
like that updating the hardware so I guess it could be several
people following procedure who have updated this number in the
hardware over the years.
But I bet it is a single person in Grenoble who has been doing
the MMC/SD block since it appeared.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-01-16 7:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 12:15 [PATCH 00/14] Add MMCI support for STM32F SoCs family patrice.chotard-qxv4g6HH51o
2018-01-12 12:15 ` [PATCH 01/14] mmc: mmci: Don't pretend all variants to have MMCIMASK1 register patrice.chotard
[not found] ` <1515759368-16946-2-git-send-email-patrice.chotard-qxv4g6HH51o@public.gmane.org>
2018-01-15 1:01 ` Linus Walleij
2018-01-12 12:15 ` [PATCH 02/14] mmc: mmci: Don't pretend all variants to have MCI_STARBITERR flag patrice.chotard
[not found] ` <1515759368-16946-3-git-send-email-patrice.chotard-qxv4g6HH51o@public.gmane.org>
2018-01-15 1:03 ` Linus Walleij
2018-01-15 12:32 ` Ulf Hansson
2018-01-15 17:27 ` Patrice CHOTARD
2018-01-12 12:15 ` [PATCH 03/14] mmc: mmci: Add support for setting pad type via pinctrl patrice.chotard
[not found] ` <1515759368-16946-4-git-send-email-patrice.chotard-qxv4g6HH51o@public.gmane.org>
2018-01-15 1:07 ` Linus Walleij
2018-01-15 12:43 ` Ulf Hansson
2018-01-15 17:42 ` Patrice CHOTARD
2018-01-12 12:15 ` [PATCH 04/14] mmc: mmci: Add STM32 variant patrice.chotard
2018-01-15 1:13 ` Linus Walleij
2018-01-15 17:17 ` Patrice CHOTARD
[not found] ` <ce14077b-2b8b-f8a7-2107-78b1d9dcab27-qxv4g6HH51o@public.gmane.org>
2018-01-16 7:38 ` Linus Walleij [this message]
2018-01-12 12:15 ` [PATCH 05/14] ARM: dts: stm32: Add SDIO controller for stm32f746 patrice.chotard
2018-01-12 12:16 ` [PATCH 06/14] ARM: dts: stm32: Add SDIO controller for stm32f429 patrice.chotard
2018-01-12 12:16 ` [PATCH 07/14] ARM: dts: stm32: Add pin map for SDIO controller on stm32f4 patrice.chotard
2018-01-12 12:16 ` [PATCH 08/14] ARM: dts: stm32: Enable SDIO controller on stm32f469 disco board patrice.chotard
2018-01-12 12:16 ` [PATCH 09/14] ARM: dts: stm32: Enable SDIO controller on stm32429i-eval board patrice.chotard
2018-01-12 12:16 ` [PATCH 10/14] ARM: stm32: Add AMBA support for STM32F4 and STM32F7 SoCs patrice.chotard
2018-01-12 12:16 ` [PATCH 11/14] ARM: configs: stm32: Enable MMC_ARMMMCI support patrice.chotard
2018-01-12 12:16 ` [PATCH 12/14] ARM: configs: stm32: Enable EXT3_FS support patrice.chotard
2018-01-12 12:16 ` [PATCH 13/14] clk: stm32: Add clk entry for SDMMC2 on stm32F769 patrice.chotard
2018-01-12 18:52 ` Stephen Boyd
2018-01-12 12:16 ` [PATCH 14/14] gpio: stmpe: i2c transfer are forbiden in atomic context patrice.chotard
[not found] ` <1515759368-16946-15-git-send-email-patrice.chotard-qxv4g6HH51o@public.gmane.org>
2018-01-15 9:57 ` Linus Walleij
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=CACRpkdY88umqVBcFNy7Z6vgHztRr7MbAjh-AWz0nYgFXoOwCLQ@mail.gmail.com \
--to=linus.walleij-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=alexandre.torgue-qxv4g6HH51o@public.gmane.org \
--cc=andrea.merello-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=patrice.chotard-qxv4g6HH51o@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=ulf.hansson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).