From: Larry Finger <Larry.Finger@lwfinger.net>
To: George Kashperko <george@znau.edu.ua>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: SSB AI support code ([RFC3/11] SSB irqflag device op)
Date: Wed, 09 Feb 2011 11:48:08 -0600 [thread overview]
Message-ID: <4D52D358.5050208@lwfinger.net> (raw)
In-Reply-To: <1297271450.3361.0.camel@dev.znau.edu.ua>
On 02/09/2011 11:10 AM, George Kashperko wrote:
>> On 02/09/2011 08:32 AM, George Kashperko wrote:
>>> From: George Kashperko <george@znau.edu.ua>
>>>
>>> SB- and AI-style buses read irq flags from different locations.
>>> SB-ones read them from TPSFLAG whereas AI-ones from core oob register.
>>> In order to support both SB- and AI-style buses transparently
>>> irq flag accessor is implemented as ssb device op.
>>> Signed-off-by: George Kashperko <george@znau.edu.ua>
>>> ---
>>> drivers/ssb/driver_mipscore.c | 2 +-
>>> drivers/ssb/main.c | 1 +
>>> include/linux/ssb/ssb.h | 5 +++++
>>> include/linux/ssb/ssb_driver_mips.h | 1 +
>>> 4 files changed, 8 insertions(+), 1 deletion(-)
>>> --- linux-next-20110203.orig/drivers/ssb/driver_mipscore.c 2011-02-01 05:05:49.000000000 +0200
>>> +++ linux-next-20110203/drivers/ssb/driver_mipscore.c 2011-02-07 16:39:46.000000000 +0200
>>> @@ -47,7 +47,7 @@ static const u32 ipsflag_irq_shift[] = {
>>> SSB_IPSFLAG_IRQ4_SHIFT,
>>> };
>>>
>>> -static inline u32 ssb_irqflag(struct ssb_device *dev)
>>> +u32 ssb_irqflag_sb(struct ssb_device *dev)
>>> {
>>> u32 tpsflag = ssb_read32(dev, SSB_TPSFLAG);
>>> if (tpsflag)
>>> --- linux-next-20110203.orig/drivers/ssb/main.c 2011-02-07 16:35:50.000000000 +0200
>>> +++ linux-next-20110203/drivers/ssb/main.c 2011-02-07 16:49:40.000000000 +0200
>>> @@ -1367,6 +1367,7 @@ static const struct ssb_bus_ops ssb_ssb_
>>> .device_disable = ssb_device_disable_sb,
>>> .admatch_base = ssb_admatch_base_sb,
>>> .admatch_size = ssb_admatch_size_sb,
>>> + .irqflag = ssb_irqflag_sb,
>>> };
>>>
>>> static int __init ssb_modinit(void)
>>> --- linux-next-20110203.orig/include/linux/ssb/ssb_driver_mips.h 2011-02-01 05:05:49.000000000 +0200
>>> +++ linux-next-20110203/include/linux/ssb/ssb_driver_mips.h 2011-02-07 16:39:10.000000000 +0200
>>> @@ -29,6 +29,7 @@ extern void ssb_mipscore_init(struct ssb
>>> extern u32 ssb_cpu_clock(struct ssb_mipscore *mcore);
>>>
>>> extern unsigned int ssb_mips_irq(struct ssb_device *dev);
>>> +extern u32 ssb_irqflag_sb(struct ssb_device *dev);
>>>
>>>
>>> #else /* CONFIG_SSB_DRIVER_MIPS */
>>> --- linux-next-20110203.orig/include/linux/ssb/ssb.h 2011-02-07 16:35:50.000000000 +0200
>>> +++ linux-next-20110203/include/linux/ssb/ssb.h 2011-02-07 16:38:34.000000000 +0200
>>> @@ -124,6 +124,7 @@ struct ssb_bus_ops {
>>> void (*device_disable)(struct ssb_device *dev, u32 core_specific_flags);
>>> u32 (*admatch_base)(struct ssb_device *dev, u32 adm);
>>> u32 (*admatch_size)(struct ssb_device *dev, u32 adm);
>>> + u32 (*irqflag)(struct ssb_device *dev);
>>> };
>>>
>>>
>>> @@ -485,6 +486,10 @@ static inline u32 ssb_admatch_size(struc
>>> {
>>> return dev->ops->admatch_size(dev, adm);
>>> }
>>> +static inline u32 ssb_irqflag(struct ssb_device *dev)
>>> +{
>>> + return dev->ops->irqflag(dev);
>>> +}
>>>
>>>
>>> /* The SSB DMA API. Use this API for any DMA operation on the device.
>>>
>>>
>>>
>>> --
>>
>> This one fails to compile with the following error:
>>
>> drivers/ssb/main.c:1370:14: error: ‘ssb_irqflag_sb’ undeclared here (not in a
>> function)
>> make[1]: *** [drivers/ssb/main.o] Error 1
>> make: *** [drivers/ssb/] Error 2
>>
>> Larry
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> Well, might the problem here is again caused with mine wrong post of <[RFC9/11] SSB modify irqflag treatment>
> Could you please remove that one and reaply whole set of patches again.
> Sorry for inconveniences.
That cannot be the problem with this one. Each patch in a series MUST compile
correctly so that anyone that is bisecting the code always can build a kernel.
The code doesn't necessarily have to work correctly - that would be nice, but it
must compile. #3 fails this test.
Larry
next prev parent reply other threads:[~2011-02-09 17:47 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 13:36 SSB AI support code George Kashperko
2011-02-09 14:29 ` SSB AI support code ([RFC1/11] SSB admatch redefine) George Kashperko
2011-02-09 14:31 ` SSB AI support code ([RFC2/11] SSB reintroduce handlers as device ops) George Kashperko
2011-02-09 14:32 ` SSB AI support code ([RFC3/11] SSB irqflag device op) George Kashperko
2011-02-09 16:19 ` Larry Finger
2011-02-09 17:10 ` George Kashperko
2011-02-09 17:48 ` Larry Finger [this message]
2011-02-09 18:23 ` George Kashperko
2011-02-09 19:19 ` Larry Finger
2011-02-09 19:26 ` George Kashperko
2011-02-09 19:42 ` Larry Finger
2011-02-09 14:34 ` SSB AI support code ([RFC4/11] SSB core control and state device ops) George Kashperko
2011-02-09 20:35 ` Rafał Miłecki
2011-02-09 21:01 ` Rafał Miłecki
2011-02-09 21:21 ` George Kashperko
2011-02-09 21:03 ` George Kashperko
2011-02-09 21:14 ` Michael Büsch
2011-02-09 21:55 ` Rafał Miłecki
2011-02-09 21:58 ` George Kashperko
2011-02-09 22:00 ` George Kashperko
2011-02-09 22:02 ` Michael Büsch
2011-02-09 22:22 ` George Kashperko
2011-02-09 14:36 ` SSB AI support code ([RFC5/11] SSB propagate core control and state ops usage) George Kashperko
2011-02-09 20:58 ` Rafał Miłecki
2011-02-09 21:12 ` Michael Büsch
2011-02-09 21:26 ` George Kashperko
2011-02-09 21:50 ` Rafał Miłecki
2011-02-09 21:55 ` George Kashperko
2011-02-09 14:37 ` SSB AI support code ([RFC6/11] SSB introduce bus_check_core routine) George Kashperko
2011-02-09 14:39 ` SSB AI support code ([RFC7/11] SSB introduce ssb_bus_detect routine) George Kashperko
2011-02-09 14:40 ` SSB AI support code ([RFC8/11] SSB separate SB-specific scanning) George Kashperko
2011-02-09 14:41 ` SSB AI support code ([RFC9/11] SSB modify irqflag treatment) George Kashperko
2011-02-09 16:23 ` Larry Finger
2011-02-09 16:53 ` George Kashperko
2011-02-09 14:44 ` SSB AI support code ([RFC9/11] SSB separate SB-specific code) George Kashperko
2011-02-09 14:45 ` SSB AI support code ([RFC10/11] SSB modify irqflag treatment) George Kashperko
2011-02-09 14:46 ` SSB AI support code ([RFC11/11] SSB add AI-bus support) George Kashperko
2011-02-09 16:25 ` Larry Finger
2011-02-09 18:33 ` George Kashperko
2011-02-09 16:49 ` Larry Finger
2011-02-09 21:35 ` SSB AI support code Rafał Miłecki
2011-02-09 21:41 ` George Kashperko
2011-02-09 21:51 ` Michael Büsch
2011-02-09 22:53 ` Rafał Miłecki
2011-02-09 23:10 ` Michael Büsch
2011-02-09 23:18 ` Larry Finger
2011-02-10 5:24 ` SSB AI support code ([RFC] v2) George Kashperko
2011-02-10 10:20 ` Michael Büsch
2011-02-10 17:40 ` George Kashperko
2011-02-10 18:11 ` Michael Büsch
[not found] ` <1297362251.15805.51.camel@dev.znau.edu.ua>
[not found] ` <1297363781.30218.37.camel@maggie>
2011-02-10 19:52 ` George Kashperko
2011-02-10 20:07 ` Michael Büsch
2011-02-15 14:50 ` Rafał Miłecki
2011-02-15 15:05 ` George Kashperko
2011-02-09 23:30 ` SSB AI support code George Kashperko
2011-02-15 14:48 ` Rafał Miłecki
2011-02-15 14:53 ` George Kashperko
2011-02-12 13:03 ` Hauke Mehrtens
2011-02-12 14:15 ` George Kashperko
2011-02-17 9:28 ` Roland Vossen
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=4D52D358.5050208@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=george@znau.edu.ua \
--cc=linux-wireless@vger.kernel.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).