All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Lapshin <max@flussonic.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] i350 software defined pins sysfs access
Date: Thu, 13 Jun 2019 09:51:34 +0300	[thread overview]
Message-ID: <640C4F07-20AB-4D98-8A6D-770F0CE1C412@flussonic.com> (raw)
In-Reply-To: <3827f4b8-506d-f55a-3279-f8a17699ee5e@silicom-usa.com>


> 
> The igb driver already uses these pins for PTP if that's configured and
> the 82575 uses SDP3 as a power enable for SFP cages, sgmii PHYs, etc.
> You'll need to avoid letting userspace poke at SDPs that the driver is
> already using.

I should write code to avoid touching these registers for these cases?

> 
> Assuming this can coexist with the existing usage, why not register this
> as a gpio_chip with the gpiolib framework?

Ok, I will  take a look at it.


> 
>> Subject: [PATCH] i350: Add support for Intel i350 software defined pins
>> 
>> +
>> +/* Software defined pins 2-3 */
>> +#define IGB_CTRL_EXT_SDP2_DATA E1000_CTRL_EXT_SDP2_DATA /* Value of SW Defineable Pin 2 */
>> +#define IGB_CTRL_EXT_SDP3_DATA E1000_CTRL_EXT_SDP3_DATA /* Value of SW Defineable Pin 3 */
>> +#define IGB_CTRL_EXT_SDP2_DIR  E1000_CTRL_EXT_SDP2_DIR  /* SDP2 Data direction */
>> +#define IGB_CTRL_EXT_SDP3_DIR  E1000_CTRL_EXT_SDP3_DIR  /* SDP3 Data direction */
> 
> Looks like e1000_defines.h already has this info.
> 

Only partially, so I decided to copy it to avoid situtation then I have in one code  IGB_ and E1000_  defines.

It is not good?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20190613/1fe61572/attachment.html>

  reply	other threads:[~2019-06-13  6:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 21:01 [Intel-wired-lan] i350 software defined pins sysfs access Max Lapshin
2019-06-12 21:03 ` Stephen Douthit
2019-06-13  6:51   ` Max Lapshin [this message]
2019-06-13 14:02     ` Stephen Douthit

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=640C4F07-20AB-4D98-8A6D-770F0CE1C412@flussonic.com \
    --to=max@flussonic.com \
    --cc=intel-wired-lan@osuosl.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 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.