All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: devicetree@vger.kernel.org,
	Alexandre Torgue <alexandre.torgue@st.com>,
	linux-kernel@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Patrice Chotard <patrice.chotard@st.com>,
	linux@armlinux.org.uk, Rob Herring <robh+dt@kernel.org>,
	linux-i2c@vger.kernel.org,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	M'boumba Cedric Madianga <cedric.madianga@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 2/5] i2c: Add STM32F4 I2C driver
Date: Thu, 15 Dec 2016 20:40:02 +0100	[thread overview]
Message-ID: <20161215194001.GA1741@katana> (raw)
In-Reply-To: <20161215193307.436sggu4zy4zezoe@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 395 bytes --]


> I thought (but I could be wrong) that if the driver is called
> "stm32f4-i2c", it is used to match "st,stm32f4-i2c" even without
> .of_match_table. If this doesn't work, please disregard my question.

This currently works only for *i2c client drivers*, it never did for i2c
adapters. And even for clients, this behaviour is going to be deprecated
somewhen. There are people working on it...


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 2/5] i2c: Add STM32F4 I2C driver
Date: Thu, 15 Dec 2016 20:40:02 +0100	[thread overview]
Message-ID: <20161215194001.GA1741@katana> (raw)
In-Reply-To: <20161215193307.436sggu4zy4zezoe@pengutronix.de>


> I thought (but I could be wrong) that if the driver is called
> "stm32f4-i2c", it is used to match "st,stm32f4-i2c" even without
> .of_match_table. If this doesn't work, please disregard my question.

This currently works only for *i2c client drivers*, it never did for i2c
adapters. And even for clients, this behaviour is going to be deprecated
somewhen. There are people working on it...

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161215/46d9fc21/attachment-0001.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "M'boumba Cedric Madianga" <cedric.madianga@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@st.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Patrice Chotard <patrice.chotard@st.com>,
	linux@armlinux.org.uk, linux-i2c@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/5] i2c: Add STM32F4 I2C driver
Date: Thu, 15 Dec 2016 20:40:02 +0100	[thread overview]
Message-ID: <20161215194001.GA1741@katana> (raw)
In-Reply-To: <20161215193307.436sggu4zy4zezoe@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 395 bytes --]


> I thought (but I could be wrong) that if the driver is called
> "stm32f4-i2c", it is used to match "st,stm32f4-i2c" even without
> .of_match_table. If this doesn't work, please disregard my question.

This currently works only for *i2c client drivers*, it never did for i2c
adapters. And even for clients, this behaviour is going to be deprecated
somewhen. There are people working on it...


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-12-15 19:40 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 16:15 [PATCH v6 0/5] Add support for the STM32F4 I2C M'boumba Cedric Madianga
2016-12-12 16:15 ` M'boumba Cedric Madianga
2016-12-12 16:15 ` [PATCH v6 1/5] dt-bindings: Document the STM32 I2C bindings M'boumba Cedric Madianga
2016-12-12 16:15   ` M'boumba Cedric Madianga
2016-12-12 16:15 ` [PATCH v6 2/5] i2c: Add STM32F4 I2C driver M'boumba Cedric Madianga
2016-12-12 16:15   ` M'boumba Cedric Madianga
2016-12-13  9:20   ` Uwe Kleine-König
2016-12-13  9:20     ` Uwe Kleine-König
2016-12-15 15:26     ` M'boumba Cedric Madianga
2016-12-15 15:26       ` M'boumba Cedric Madianga
2016-12-15 15:26       ` M'boumba Cedric Madianga
2016-12-15 19:33       ` Uwe Kleine-König
2016-12-15 19:33         ` Uwe Kleine-König
2016-12-15 19:40         ` Wolfram Sang [this message]
2016-12-15 19:40           ` Wolfram Sang
2016-12-15 19:40           ` Wolfram Sang
     [not found]     ` <20161213092031.d2ax2pnpzzicriel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2016-12-15 19:42       ` Wolfram Sang
2016-12-15 19:42         ` Wolfram Sang
2016-12-15 19:42         ` Wolfram Sang
2016-12-12 16:15 ` [PATCH v6 3/5] ARM: dts: stm32: Add I2C1 support for STM32F429 SoC M'boumba Cedric Madianga
2016-12-12 16:15   ` M'boumba Cedric Madianga
     [not found]   ` <1481559342-6106-4-git-send-email-cedric.madianga-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-13 10:01     ` Alexandre Torgue
2016-12-13 10:01       ` Alexandre Torgue
2016-12-13 10:01       ` Alexandre Torgue
2016-12-12 16:15 ` [PATCH v6 4/5] ARM: dts: stm32: Add I2C1 support for STM32429 eval board M'boumba Cedric Madianga
2016-12-12 16:15   ` M'boumba Cedric Madianga
2016-12-13 10:02   ` Alexandre Torgue
2016-12-13 10:02     ` Alexandre Torgue
2016-12-13 10:02     ` Alexandre Torgue
2016-12-12 16:15 ` [PATCH v6 5/5] ARM: configs: stm32: Add I2C support for STM32 defconfig M'boumba Cedric Madianga
2016-12-12 16:15   ` M'boumba Cedric Madianga
     [not found]   ` <1481559342-6106-6-git-send-email-cedric.madianga-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-13 10:03     ` Alexandre Torgue
2016-12-13 10:03       ` Alexandre Torgue
2016-12-13 10:03       ` Alexandre Torgue

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=20161215194001.GA1741@katana \
    --to=wsa@the-dreams.de \
    --cc=alexandre.torgue@st.com \
    --cc=cedric.madianga@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=patrice.chotard@st.com \
    --cc=robh+dt@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.