public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: Valdis.Kletnieks@vt.edu
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
	user-mode-linux-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: 2 small kernel config issues related to UML + RTC
Date: Mon, 30 May 2011 06:16:46 +0200	[thread overview]
Message-ID: <4DE31A2E.70705@st.com> (raw)
In-Reply-To: <103895.1306689477@turing-police.cc.vt.edu>

Hi Valdis

On 5/29/2011 7:17 PM, Valdis.Kletnieks@vt.edu wrote:
> On Sun, 29 May 2011 11:22:01 +0200, Toralf Förster said:
>>   │ Symbol: STMMAC_RTC_TIMER [=n]                        
>>   │ Type  : boolean
>>   │ Prompt: Real time clock
>>   │   Defined at drivers/net/stmmac/Kconfig:50
>>   │   Depends on: <choice> && RTC_CLASS
>>   │   Location:
>>   │     -> Network device support (NETDEVICES [=y])
>>   │       -> Ethernet (1000 Mbit) (NETDEV_1000 [=n])
>>   │         -> STMicroelectronics 10/100/1000 Ethernet driver (STMMAC_ETH [=n])
>>   │           -> STMMAC Timer optimisation (STMMAC_TIMER [=n])
>>   │             -> Select Timer device (<choice> [=n])
> 
> Ouch. That has to be the strangest place one could *possibly* put an RTC driver. ;)
> 
> Giuseppe - is that RTC driver *really* an integral part of the chipset and
> won't work without the Ethernet parts, or should the driver code for the RTC
> live elsewhere in the tree?

No the external RTC (or the SH-4 TMU) HW can be used by the driver to
handle the rx/tx process mitigating the DMA interrupts. This is not the
best approach but it actually helped many people to space the CPU
especially on old chips w/o dedicate timer.

It's likely I will remove all this code as soon as I work on a chip with
the embedded watchdog.

Regards
Giuseppe

      reply	other threads:[~2011-05-30  4:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-29  9:22 2 small kernel config issues related to UML + RTC Toralf Förster
2011-05-29  9:54 ` richard -rw- weinberger
2011-05-29 17:17 ` Valdis.Kletnieks
2011-05-30  4:16   ` Giuseppe CAVALLARO [this message]

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=4DE31A2E.70705@st.com \
    --to=peppe.cavallaro@st.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toralf.foerster@gmx.de \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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