From: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
To: Rob Herring <robh@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Mark Rutland <mark.rutland@arm.com>,
Nandor Han <nandor.han@ge.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCHv2 1/3] dt-bindings: misc: achc: Make ezport distinguishable
Date: Mon, 9 Apr 2018 23:13:37 +0200 [thread overview]
Message-ID: <20180409211337.goavadt6f22wtkbw@earth.universe> (raw)
In-Reply-To: <20180409185727.j4unhx5ig3fgm6ex@rob-hp-laptop>
[-- Attachment #1: Type: text/plain, Size: 2236 bytes --]
Hi,
On Mon, Apr 09, 2018 at 01:57:27PM -0500, Rob Herring wrote:
> On Tue, Mar 27, 2018 at 03:52:57PM +0200, Sebastian Reichel wrote:
> > This updates the GE ACHC binding, so that different compatible
> > strings are used for the programming interface, which is the
> > ezport interface from NXP MK20FN1M0VMD12 and the microcontroller's
> > normal SPI interface.
> >
> > Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
> > ---
> > Documentation/devicetree/bindings/misc/ge-achc.txt | 19 ++++++++++++++++---
> > 1 file changed, 16 insertions(+), 3 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/misc/ge-achc.txt b/Documentation/devicetree/bindings/misc/ge-achc.txt
> > index 77df94d7a32f..6c6bd6568504 100644
> > --- a/Documentation/devicetree/bindings/misc/ge-achc.txt
> > +++ b/Documentation/devicetree/bindings/misc/ge-achc.txt
> > @@ -7,7 +7,13 @@ Note: This device does not expose the peripherals as USB devices.
> >
> > Required properties:
> >
> > -- compatible : Should be "ge,achc"
> > +- compatible : Should be
> > + "ge,achc" (normal interface)
> > + "ge,achc-ezport" (flashing interface)
> > +
> > +Required properties (flashing interface only):
> > +
> > +- reset-gpios: GPIO Specifier for the reset GPIO
>
> Does the reset only affect the flashing interface and are the data pins
> shared? If not for both, then I think the correct thing to do here is
> just extend reg to support multiple values to represent multiple chip
> selects.
reset affects the whole chip and the same spi data/clock pins are
being used, so extending reg should work. The flashing cannot happen
with the same speed, though. I'm currently encoding this by using
different "spi-max-frequency" properties. I suppose I could limit
it in the driver instead. I tried to come up with an example for
your suggestion. Is this what you had in mind?
&spi_controller {
achc@multiple {
/* 0 = flashing interface, 1 = normal interface */
reg = <0>, <1>;
compatible = "ge,achc";
reset-gpios = <&gpio42 23 ACTIVE_LOW>;
spi-max-frequency = <42>; /* max speed for normal operation */
};
};
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-09 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 13:52 [PATCHv2 0/3] GE Healthcare PPD firmware upgrade driver for ACHC Sebastian Reichel
2018-03-27 13:52 ` [PATCHv2 1/3] dt-bindings: misc: achc: Make ezport distinguishable Sebastian Reichel
2018-04-09 18:57 ` Rob Herring
2018-04-09 21:13 ` Sebastian Reichel [this message]
2018-04-13 15:33 ` Rob Herring
2018-04-26 14:39 ` Sebastian Reichel
2018-03-27 13:52 ` [PATCHv2 2/3] misc: ezport-firmware: new driver Sebastian Reichel
2018-03-27 13:52 ` [PATCHv2 3/3] ARM: dts: imx53: PPD: Update ACHC programming interface Sebastian Reichel
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=20180409211337.goavadt6f22wtkbw@earth.universe \
--to=sebastian.reichel@collabora.co.uk \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nandor.han@ge.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.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).