LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Robert Marko <robert.marko@sartura.hr> To: Andrew Lunn <andrew@lunn.ch> Cc: Rob Herring <robh@kernel.org>, Linus Walleij <linus.walleij@linaro.org>, Bartosz Golaszewski <bgolaszewski@baylibre.com>, Lee Jones <lee.jones@linaro.org>, Philipp Zabel <p.zabel@pengutronix.de>, "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>, devicetree <devicetree@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Luka Perkov <luka.perkov@sartura.hr>, "Jonathan M. Polom" <jmp@epiphyte.org>, Paul Menzel <pmenzel@molgen.mpg.de>, Donald Buczek <buczek@molgen.mpg.de> Subject: Re: [PATCH v6 5/6] dt-bindings: mfd: Add Delta TN48M CPLD drivers bindings Date: Tue, 19 Oct 2021 12:54:50 +0200 [thread overview] Message-ID: <CA+HBbNGQ9OCn9T-XW7MUL-H8LkL6Dcot1NExO+xv9gsuPxjLRw@mail.gmail.com> (raw) In-Reply-To: <YW4n7hUIEB320dFv@lunn.ch> On Tue, Oct 19, 2021 at 4:05 AM Andrew Lunn <andrew@lunn.ch> wrote: > > > > > > + GPIO controller module provides GPIO-s for the SFP slots. > > > > > + It is split into 3 controllers, one output only for the SFP TX disable > > > > > + pins, one input only for the SFP present pins and one input only for > > > > > + the SFP LOS pins. > > Late to the conversation, so i might be asking questions already > asked... > > So the PLD has restrictions? You have a collection of GPOs and a > collection of GPIs? You don't have an GPIOs? Yes, the CPLD is hardwired per board with the specific FW for it. There are no true GPIO-s, only input or output pins depending on their purpose in the SFP cage. > > > > > > + > > > > > +properties: > > > > > + compatible: > > > > > + enum: > > > > > + - delta,tn48m-gpio-sfp-tx-disable > > > > > + - delta,tn48m-gpio-sfp-present > > > > > + - delta,tn48m-gpio-sfp-los > > Do these names have any real significant? Are you really forced to > connect the SFP cage in this dedicated manor? Is there any reason why > i cannot use a GPO to control an LED? A GPI for a button? Yes, there are connected like this on the TN48M switch, names directly match their purpose. The CPLD is customized per each switch model, so TN4810M which is the 48 x 10G SFP+ uses the same CPLD model but is wired differently and with a different FW. Since it's a CPLD you technically use whatever pin to connect stuff, but it completely depends on the FW implementation as there is no traditional GPIO block with XYZ number of pins. I have multiple vendors and models using the same CPLD but its wired completely different and the register layout is different. So you cant force any of the input pins to output mode or change their value at all, its all hardwired. Regards, Robert > > Andrew -- Robert Marko Staff Embedded Linux Engineer Sartura Ltd. Lendavska ulica 16a 10000 Zagreb, Croatia Email: robert.marko@sartura.hr Web: www.sartura.hr
next prev parent reply other threads:[~2021-10-19 10:55 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-07 12:33 [PATCH v6 1/6] mfd: simple-mfd-i2c: Add Delta TN48M CPLD support Robert Marko 2021-06-07 12:33 ` [PATCH v6 2/6] gpio: Add Delta TN48M CPLD GPIO driver Robert Marko 2021-06-07 12:33 ` [PATCH v6 3/6] dt-bindings: reset: Add Delta TN48M Robert Marko 2021-06-07 12:33 ` [PATCH v6 4/6] reset: Add Delta TN48M CPLD reset controller Robert Marko 2021-06-07 12:33 ` [PATCH v6 5/6] dt-bindings: mfd: Add Delta TN48M CPLD drivers bindings Robert Marko 2021-06-25 11:46 ` Robert Marko 2021-07-13 22:25 ` Rob Herring 2021-07-18 9:15 ` Robert Marko 2021-07-19 10:46 ` Lee Jones 2021-07-19 22:59 ` Rob Herring 2021-07-21 14:16 ` Linus Walleij 2021-08-03 19:22 ` Robert Marko 2021-08-11 12:17 ` Linus Walleij 2021-08-24 8:03 ` Robert Marko 2021-09-07 21:02 ` Robert Marko 2021-09-25 14:47 ` Robert Marko 2021-10-03 22:48 ` Linus Walleij 2021-10-12 16:31 ` Robert Marko 2021-10-19 1:40 ` Andrew Lunn 2021-10-19 10:49 ` Robert Marko 2021-10-19 2:05 ` Andrew Lunn 2021-10-19 10:54 ` Robert Marko [this message] 2021-06-07 12:33 ` [PATCH v6 6/6] MAINTAINERS: Add Delta Networks TN48M CPLD drivers Robert Marko
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=CA+HBbNGQ9OCn9T-XW7MUL-H8LkL6Dcot1NExO+xv9gsuPxjLRw@mail.gmail.com \ --to=robert.marko@sartura.hr \ --cc=andrew@lunn.ch \ --cc=bgolaszewski@baylibre.com \ --cc=buczek@molgen.mpg.de \ --cc=devicetree@vger.kernel.org \ --cc=jmp@epiphyte.org \ --cc=lee.jones@linaro.org \ --cc=linus.walleij@linaro.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=luka.perkov@sartura.hr \ --cc=p.zabel@pengutronix.de \ --cc=pmenzel@molgen.mpg.de \ --cc=robh@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: linkBe 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).