From: acourbot@nvidia•com (Alexandre Courbot)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3] of: replace Asahi Kasei Corp venter prefix
Date: Fri, 14 Nov 2014 17:38:58 +0900 [thread overview]
Message-ID: <5465BFA2.9050706@nvidia.com> (raw)
In-Reply-To: <87k32yd0bd.wl%kuninori.morimoto.gx@renesas.com>
On 11/14/2014 10:43 AM, Kuninori Morimoto wrote:
> From: Kuninori Morimoto <kuninori.morimoto.gx@renesas•com>
>
> Current vendor-prefixes.txt already has
> "ak" prefix for Asahi Kasei Corp by
> ae8c4209af2cec065fef15d200a42a04130799f7
> (of: Add vendor prefix for Asahi Kasei Corp.)
>
> It went through the appropriate review process.
> But, almost all Asahi Kasei chip drivers are
> using "asahi-kasei" prefix today.
> (arch/arm/boot/dts/tegra20-seaboard.dts only is
> using "ak,ak8975", but there are instances of
> "asahi-kasei,ak8975" in other dts files.
> And drivers/iio/magnetometer/ak8975.c
> doesn't support "ak,ak8975")
> So, we made a mistake there.
>
> In addition, checkpatch.pl reports WARNING
> if it is using "asahi-kasei" prerfix in DT file.
> (DT compatible string vendor "asahi-kasei" appears un-documented)
>
> Marking it deprecated and warning with checkpatch
> is certainly preferable.
> So, this patch replace "ak" to "asahi-kasei" in
> vendor-prefixes.txt. (and fixup tegra20-seaboard)
>
> OTOH, Asahi Kasei is usually referred to as "AKM",
> but this patch doesn't care about it.
> Because no DT is using that today.
>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas•com>
> ---
> .../devicetree/bindings/vendor-prefixes.txt | 2 +-
> arch/arm/boot/dts/tegra20-seaboard.dts | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> index 723999d..ddcb4cd 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -9,7 +9,6 @@ ad Avionic Design GmbH
> adapteva Adapteva, Inc.
> adi Analog Devices, Inc.
> aeroflexgaisler Aeroflex Gaisler AB
> -ak Asahi Kasei Corp.
> allwinner Allwinner Technology Co., Ltd.
> altr Altera Corp.
> amcc Applied Micro Circuits Corporation (APM, formally AMCC)
> @@ -20,6 +19,7 @@ amstaos AMS-Taos Inc.
> apm Applied Micro Circuits Corporation (APM)
> arm ARM Ltd.
> armadeus ARMadeus Systems SARL
> +asahi-kasei Asahi Kasei Corp.
> atmel Atmel Corporation
> auo AU Optronics Corporation
> avago Avago Technologies
> diff --git a/arch/arm/boot/dts/tegra20-seaboard.dts b/arch/arm/boot/dts/tegra20-seaboard.dts
> index a1d4bf9..7f5cf80 100644
> --- a/arch/arm/boot/dts/tegra20-seaboard.dts
> +++ b/arch/arm/boot/dts/tegra20-seaboard.dts
> @@ -405,7 +405,7 @@
> clock-frequency = <400000>;
>
> magnetometer at c {
> - compatible = "ak,ak8975";
> + compatible = "asahi-kasei,ak8975";
Mmm. So does this mean this device was never probed because the driver
did not recognize its compatible property? I cannot find "ak,ak8975"
anywhere else in the kernel.
If so,
Acked-by: Alexandre Courbot <acourbot@nvidia•com>
next prev parent reply other threads:[~2014-11-14 8:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5398AB07.4040304@wwwdotorg.org>
[not found] ` <87sinbdk44.wl%kuninori.morimoto.gx@renesas.com>
[not found] ` <878ulzx6hr.wl%kuninori.morimoto.gx@gmail.com>
[not found] ` <20140922130026.GK3290@leverpostej>
[not found] ` <CAMuHMdX22z97SbGS1HDiYfJ1PXxyEN2S8D7w4sr+4bUwD+mJZw@mail.gmail.com>
[not found] ` <20140922132743.GM3290@leverpostej>
[not found] ` <87y4rfhmgl.wl%kuninori.morimoto.gx@renesas.com>
[not found] ` <1415845309.4269.6.camel@perches.com>
[not found] ` <20141113025105.GA16652@verge.net.au>
[not found] ` <87vbmjhj00.wl%kuninori.morimoto.gx@renesas.com>
[not found] ` <20141113110740.GE3815@sirena.org.uk>
2014-11-14 1:43 ` [PATCH v3] of: replace Asahi Kasei Corp venter prefix Kuninori Morimoto
2014-11-14 8:38 ` Alexandre Courbot [this message]
2014-11-14 9:16 ` Arnd Bergmann
2014-11-14 9:30 ` Thierry Reding
2014-11-14 9:35 ` [alsa-devel] " Thierry Reding
2014-11-17 0:51 ` [PATCH v4] " Kuninori Morimoto
2014-11-17 10:26 ` Sergei Shtylyov
2014-11-18 0:30 ` [PATCH v5] of: replace Asahi Kasei Corp vendor prefix Kuninori Morimoto
2014-11-28 0:22 ` [PATCH v5][resend] of: replace Asahi Kasei Corp venter prefix Kuninori Morimoto
2014-11-28 11:45 ` Sergei Shtylyov
2014-12-02 4:57 ` [PATCH v5][resend] of: replace Asahi Kasei Corp vendor prefix Kuninori Morimoto
2014-12-15 3:53 ` [PATCH v5][resend v2] " Kuninori Morimoto
2014-12-17 2:33 ` [PATCH v5][resend v3] " Kuninori Morimoto
2015-01-09 3:40 ` [PATCH v5][resend v4] " Kuninori Morimoto
2015-01-09 3:42 ` [PATCH v5][resend v5] " Kuninori Morimoto
2015-01-09 4:36 ` [PATCH v5][resend v4] " Stephen Warren
2015-01-09 10:07 ` Kuninori Morimoto
2015-01-09 13:46 ` Rob Herring
2015-01-09 13:55 ` Arnd Bergmann
2015-01-09 16:04 ` Mark Brown
2014-12-25 3:55 ` [PATCH v5][resend v6] " Kuninori Morimoto
2015-01-13 20:03 ` [PATCH v5][resend] " Rob Herring
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=5465BFA2.9050706@nvidia.com \
--to=acourbot@nvidia$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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