diff for duplicates of <1302123428.20093.6.camel@maggie> diff --git a/a/1.txt b/N1/1.txt index f5050d7..86b4ecd 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,5 @@ -On Wed, 2011-04-06 at 22:42 +0200, Rafa? Mi?ecki wrote: -> 2011/4/6 Rafa? Mi?ecki <zajec5@gmail.com>: +On Wed, 2011-04-06 at 22:42 +0200, Rafał Miłecki wrote: +> 2011/4/6 Rafał Miłecki <zajec5@gmail.com>: > > If we want to have two drivers working on two (different) cores > > simultaneously, we will have to add trivial mutex to group core > > switching with core operation (read/write). @@ -10,3 +10,19 @@ On Wed, 2011-04-06 at 22:42 +0200, Rafa? Mi?ecki wrote: I don't think that this is a problem at all. All that magic does happen inside of the bus I/O handlers. Just like SSB does it. +>From a driver point of view, the I/O functions just need to +be atomic. + +For SSB it's not always 100% atomic, but we're always safe +due to some assumptions being made. But this is an SSB implementation +detail that is different from AXI. So don't look too closely +at the SSB implementation of the I/O functions. You certainly want +to implement them slightly differently in AXI. SSB currently doesn't +make use of the additional sliding windows, because they are not +available in the majority of SSB devices. + +The AXI bus subsystem will manage the sliding windows and the driver +doesn't know about the details. + +-- +Greetings Michael. diff --git a/a/content_digest b/N1/content_digest index fe509ea..001c50b 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,13 +5,24 @@ "ref\0BANLkTin-u=U_-cUH9oCco0LjEBuQmh4wag@mail.gmail.com\0" "ref\0BANLkTi=x89+52cMeutOB7J--QQta+mX_wg@mail.gmail.com\0" "From\0Michael B\303\274sch <mb@bu3sch.de>\0" - "Subject\0[RFC][PATCH] bcmai: introduce AI driver\0" + "Subject\0Re: [RFC][PATCH] bcmai: introduce AI driver\0" "Date\0Wed, 06 Apr 2011 22:57:08 +0200\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Rafa\305\202 Mi\305\202ecki <zajec5@gmail.com>\0" + "Cc\0Arend van Spriel <arend@broadcom.com>" + linux-wireless@vger.kernel.org <linux-wireless@vger.kernel.org> + John W. Linville <linville@tuxdriver.com> + Larry Finger <Larry.Finger@lwfinger.net> + George Kashperko <george@znau.edu.ua> + b43-dev@lists.infradead.org <b43-dev@lists.infradead.org> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + Russell King <rmk@arm.linux.org.uk> + Arnd Bergmann <arnd@arndb.de> + linuxdriverproject <devel@linuxdriverproject.org> + " linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>\0" "\00:1\0" "b\0" - "On Wed, 2011-04-06 at 22:42 +0200, Rafa? Mi?ecki wrote: \n" - "> 2011/4/6 Rafa? Mi?ecki <zajec5@gmail.com>:\n" + "On Wed, 2011-04-06 at 22:42 +0200, Rafa\305\202 Mi\305\202ecki wrote: \n" + "> 2011/4/6 Rafa\305\202 Mi\305\202ecki <zajec5@gmail.com>:\n" "> > If we want to have two drivers working on two (different) cores\n" "> > simultaneously, we will have to add trivial mutex to group core\n" "> > switching with core operation (read/write).\n" @@ -21,6 +32,22 @@ "\n" "I don't think that this is a problem at all.\n" "All that magic does happen inside of the bus I/O handlers.\n" - Just like SSB does it. + "Just like SSB does it.\n" + ">From a driver point of view, the I/O functions just need to\n" + "be atomic.\n" + "\n" + "For SSB it's not always 100% atomic, but we're always safe\n" + "due to some assumptions being made. But this is an SSB implementation\n" + "detail that is different from AXI. So don't look too closely\n" + "at the SSB implementation of the I/O functions. You certainly want\n" + "to implement them slightly differently in AXI. SSB currently doesn't\n" + "make use of the additional sliding windows, because they are not\n" + "available in the majority of SSB devices.\n" + "\n" + "The AXI bus subsystem will manage the sliding windows and the driver\n" + "doesn't know about the details.\n" + "\n" + "-- \n" + Greetings Michael. -138cd8674c89894833c64fb3487b8414b2d085924b0f9161280c6cdb3897d65f +a1e030f514429140ade96cdeff01c81cf523f519a789005518f790c009d8a81a
diff --git a/a/content_digest b/N2/content_digest index fe509ea..70f8c68 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -4,7 +4,7 @@ "ref\0op.vti9ote53ri7v4@arend-laptop\0" "ref\0BANLkTin-u=U_-cUH9oCco0LjEBuQmh4wag@mail.gmail.com\0" "ref\0BANLkTi=x89+52cMeutOB7J--QQta+mX_wg@mail.gmail.com\0" - "From\0Michael B\303\274sch <mb@bu3sch.de>\0" + "From\0mb@bu3sch.de (Michael B\303\274sch)\0" "Subject\0[RFC][PATCH] bcmai: introduce AI driver\0" "Date\0Wed, 06 Apr 2011 22:57:08 +0200\0" "To\0linux-arm-kernel@lists.infradead.org\0" @@ -23,4 +23,4 @@ "All that magic does happen inside of the bus I/O handlers.\n" Just like SSB does it. -138cd8674c89894833c64fb3487b8414b2d085924b0f9161280c6cdb3897d65f +0d521f4aeec6a882aa5232d576ebbb606ad6d8e4dd79892bac704bb1bf5e3830
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.