From: Sergei Shtylyov <sshtylyov-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Cc: Sergei Shtylyov
<sshtylyov-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>,
"Gupta, Ajay Kumar" <ajay.gupta-l0cyMroinI0@public.gmane.org>,
"linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Balbi, Felipe" <balbi-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH v2] musb: am35x: fix compile error due to control apis
Date: Tue, 07 Dec 2010 16:20:21 +0300 [thread overview]
Message-ID: <4CFE3495.5090204@ru.mvista.com> (raw)
In-Reply-To: <20101206175445.GF8345-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Hello.
On 06-12-2010 20:54, Tony Lindgren wrote:
>>>>> As the control.h have been moved to new location and it's
>>>>> uses are not allowed to drivers directly so moving the phy
>>>>> control, interrupt clear and reset functionality to board
>>>>> files.
>>>> I'm not fond of the whole approach. I'm not sure why accesses to the
>>>> control registers are such a no-no, taking into account that one needs to
>>>> access such regisyter to clear the interrupt...
> Because drivers should arch independent and any tinkering of the
> platform level registers will lead into pains later on that
> I end up having to deal with.
> To me it seem you just init to separate out the transceiver,
> right?
We also have to install a hook to clear the MUSB level interrupt via the
control register -- that's a thing that makes me dubious about not allowing
drivers to access the control registers.
> Tony
WBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-12-07 13:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 8:13 [PATCH v2] musb: am35x: fix compile error due to control apis Ajay Kumar Gupta
[not found] ` <1291623211-959-1-git-send-email-ajay.gupta-l0cyMroinI0@public.gmane.org>
2010-12-06 10:37 ` Sergei Shtylyov
[not found] ` <4CFCBCF1.9010902-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2010-12-06 12:31 ` Gupta, Ajay Kumar
2010-12-06 17:13 ` Sergei Shtylyov
2010-12-06 17:54 ` Tony Lindgren
[not found] ` <20101206175445.GF8345-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2010-12-07 13:20 ` Sergei Shtylyov [this message]
[not found] ` <4CFE3495.5090204-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2010-12-15 3:01 ` Paul Walmsley
2011-01-18 19:15 ` Ben Gamari
2011-01-24 15:45 ` Ben Gamari
[not found] ` <87k4hu8fvx.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-01-27 4:48 ` Felipe Balbi
[not found] ` <20110127044810.GJ2429-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org>
2011-01-27 12:31 ` Ben Gamari
2011-02-01 7:26 ` Felipe Balbi
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=4CFE3495.5090204@ru.mvista.com \
--to=sshtylyov-igf4poytycdqt0dzr+alfa@public.gmane.org \
--cc=ajay.gupta-l0cyMroinI0@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@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 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.