From: Peter Rosin <peda@axentia.se>
To: Florian Vaussard <florian.vaussard@heig-vd.ch>,
<devicetree@vger.kernel.org>, Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Slawomir Stepien <sst@poczta.fm>,
Joachim Eastwood <manabian@gmail.com>,
Matt Ranostay <mranostay@gmail.com>,
Cristina Moraru <cristina.moraru09@gmail.com>,
<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] iio: potentiometer: mcp4531: Add device tree binding
Date: Wed, 22 Jun 2016 09:06:16 +0200 [thread overview]
Message-ID: <dfdbc7dd-8457-c0ef-9f0e-e2c1d96e5b11@axentia.se> (raw)
In-Reply-To: <829a4507-39d7-e04a-9672-6309def89ee2@heig-vd.ch>
On 2016-06-22 08:22, Florian Vaussard wrote:
> Hello Peter,
>
> Le 21. 06. 16 à 09:51, Peter Rosin a écrit :
>> That is, if you need this patch at all, see my reply to 2/3...
>>
>
> This seems necessary in order to have the vendor ID in the compatible string.
Hmm, I don't think so. The way I read the response from Rob was that
*my* device tree snippet should not assume that the i2c subsystem
ignores the vendor. So, I think that even w/o this patch a DT entry
like
mcp4651-104@28 {
compatible = "microchip,mcp4651-104";
reg = <0x28>;
};
will work, precisely since i2c ignores the microchip, part (and thus
allows you to omit/misspell it). I.e. I think that Rob is concerned
with how the DT is documented/defined, and not so much about how it
is then implemented in Linux.
I haven't actually tested that though, so I may be completely wrong
in all of the above statements...
Cheers,
Peter
next prev parent reply other threads:[~2016-06-22 7:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 6:55 [PATCH 0/3] iio: potentiometer: mcp4531: New parts and device tree Florian Vaussard
2016-06-21 6:55 ` [PATCH 1/3] iio: potentiometer: mcp4531: Add support for MCP454x, MCP456x, MCP464x and MCP466x Florian Vaussard
2016-06-21 7:28 ` Peter Rosin
2016-06-21 6:55 ` [PATCH 2/3] iio: potentiometer: mcp4531: Add device tree binding documentation Florian Vaussard
2016-06-21 7:38 ` Peter Rosin
2016-06-21 7:49 ` Florian Vaussard
2016-06-21 21:37 ` Rob Herring
2016-06-21 21:43 ` Rob Herring
2016-06-22 6:19 ` Florian Vaussard
2016-06-21 6:55 ` [PATCH 3/3] iio: potentiometer: mcp4531: Add device tree binding Florian Vaussard
2016-06-21 7:34 ` kbuild test robot
2016-06-21 7:51 ` Peter Rosin
2016-06-22 6:22 ` Florian Vaussard
2016-06-22 7:06 ` Peter Rosin [this message]
2016-06-23 8:50 ` Florian Vaussard
2016-06-26 14:53 ` Jonathan Cameron
2016-06-26 14:53 ` [PATCH 0/3] iio: potentiometer: mcp4531: New parts and device tree Jonathan Cameron
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=dfdbc7dd-8457-c0ef-9f0e-e2c1d96e5b11@axentia.se \
--to=peda@axentia.se \
--cc=cristina.moraru09@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=florian.vaussard@heig-vd.ch \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manabian@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mranostay@gmail.com \
--cc=pawel.moll@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=sst@poczta.fm \
/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
all inboxes | Powered by JetHome®