From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Mikhail Goryunov <gormih78-o+MxOtu4lMCHXe+LvDLADg@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: spidev t20 on 2.6.36.2 kernel problem
Date: Thu, 04 Apr 2013 12:26:23 -0600 [thread overview]
Message-ID: <515DC5CF.5030303@wwwdotorg.org> (raw)
In-Reply-To: <1714461365098590-5jccDmya2mZuio3avFS2gg@public.gmane.org>
On 04/04/2013 12:03 PM, Mikhail Goryunov wrote:
> By the way in the upstream kernel 3.8.5 in my opinion there is no header file with registers of tegra t20?
Which aspect of the registers?
If you mean the base address of each HW module: that is described in
device-tree now. See arch/arm/boot/dts/tegra20.dtsi.
If you mean the individual register fields for each module, those are
part of the individual drivers; either in the .c file or an accompanying
.h file. For example, drivers/gpio/gpio-tegra.c or
sound/soc/tegra/tegra20_i2s.h.
prev parent reply other threads:[~2013-04-04 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 6:50 spidev t20 on 2.6.36.2 kernel problem Горюнов Михаил
[not found] ` <1243821364971837-NntFpNdt8ZFxpj1cXAZ9Bg@public.gmane.org>
2013-04-03 9:33 ` Горюнов Михаил
2013-04-03 16:48 ` Stephen Warren
[not found] ` <883501365053928@web30f.yandex.ru>
[not found] ` <883501365053928-2LdmG2lj+95xpj1cXAZ9Bg@public.gmane.org>
2013-04-04 17:36 ` Stephen Warren
[not found] ` <515DBA35.6000309-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-04-04 18:03 ` Mikhail Goryunov
[not found] ` <1714461365098590-5jccDmya2mZuio3avFS2gg@public.gmane.org>
2013-04-04 18:26 ` Stephen Warren [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=515DC5CF.5030303@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=gormih78-o+MxOtu4lMCHXe+LvDLADg@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).