Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH] ice: add support for auxiliary input/output pins
Date: Mon, 14 Jun 2021 10:26:18 -0700	[thread overview]
Message-ID: <0871761b-d2bd-4d98-b4c6-0779a19d62cf@intel.com> (raw)
In-Reply-To: <81762743e833402ca3c959050862cbdbacf47e86.camel@intel.com>



On 6/14/2021 10:15 AM, Nguyen, Anthony L wrote:
> On Wed, 2021-06-09 at 13:29 -0700, Jacob Keller wrote:
>> From: Maciej Machnikowski <maciej.machnikowski@intel.com>
>>
>> The E810 device supports programmable pins for enabling both input
>> and
>> output events related to the PTP hardware clock. This includes both
>> output signals with programmable period, as well as timestamping of
>> events on input pins.
>>
>> Add support for enabling these using the CONFIG_PTP_1588_CLOCK
>> interface.
>>
>> This allows programming the software defined pins to take advantage
>> of
>> the hardware clock features.
>>
>> Signed-off-by: Maciej Machnikowski <maciej.machnikowski@intel.com>
>> Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
>> ---
> 
> I'm seeing this for a 32bit build:
> 
>> make[2]: *** Deleting file 'modules-only.symvers'
>> ERROR: modpost: "__udivdi3" [drivers/net/ethernet/intel/ice/ice.ko]
> undefined!
>> ERROR: modpost: "__umoddi3" [drivers/net/ethernet/intel/ice/ice.ko]
> undefined!
>> make[2]: *** [../scripts/Makefile.modpost:150: modules-only.symvers]
> Error 1
>> make[1]: *** [/next-queue/Makefile:1754: modules] Error 2
>> make: *** [Makefile:215: __sub-make] Error 2
> 

I'm not certain which divisions are causing problems, but I suspect it
is the roundup() macro and/or some of the % modulo operations.

  reply	other threads:[~2021-06-14 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 20:29 [Intel-wired-lan] [PATCH] ice: add support for auxiliary input/output pins Jacob Keller
2021-06-14 17:15 ` Nguyen, Anthony L
2021-06-14 17:26   ` Jacob Keller [this message]
2021-06-15  8:13     ` Machnikowski, Maciej

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=0871761b-d2bd-4d98-b4c6-0779a19d62cf@intel.com \
    --to=jacob.e.keller@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox