On 01/29/2013 05:01 PM, Thomas Petazzoni wrote:
Dear Florian Fainelli,
On Tue, 29 Jan 2013 16:24:08 +0100, Florian Fainelli wrote:
This patch converts the Marvell MV643XX ethernet driver to use the
Marvell Orion MDIO driver. As a result, PowerPC and ARM platforms
registering the Marvell
Create functions to simplify if file_ops contain either a read
or aio_read op, or likewise write or aio_write. We will be adding
read_iter and write_iter and don't need to be complicating the code
in multiple places.
Signed-off-by: Dave Kleikamp
---
drivers/mtd/nand/nandsim.c | 4
Signed-off-by: Dave Kleikamp
Cc: Ben Myers
Cc: Alex Elder
Cc: x...@oss.sgi.com
---
fs/xfs/xfs_file.c | 51 ---
1 file changed, 20 insertions(+), 31 deletions(-)
diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
index 67284ed..c5d74e8 100644
---
File systems implementing read_iter & write_iter should not be required
to keep aio_read and aio_write as well. The vfs should always call
read/write_iter if they exist. This will make it easier to remove the
aio_read/write operation in the future.
Signed-off-by: Dave Kleikamp
Cc: Alexander Viro
From: Zach Brown
This adds iov_iter wrappers around copy_to_user() to match the existing
wrappers around copy_from_user().
This will be used by the generic file system buffered read path.
Signed-off-by: Dave Kleikamp
Cc: Zach Brown
---
fs/iov-iter.c | 80
The trick here is to initialize the dio state so that do_direct_IO()
consumes the pages we provide and never tries to map user pages. This
is done by making sure that final_block_in_request covers the page that
we set in the dio. do_direct_IO() will return before running out of
pages.
The
From: Zach Brown
This adds an interface that lets kernel callers submit aio iocbs without
going through the user space syscalls. This lets kernel callers avoid
the management limits and overhead of the context. It will also let us
integrate aio operations with other kernel apis that the user
On Tue, 29 Jan 2013, Joe Perches wrote:
> On Tue, 2013-01-29 at 10:55 -0500, valdis.kletni...@vt.edu wrote:
> > On Sun, 27 Jan 2013 23:19:47 +0300, Dan Carpenter said:
> >
> > > Yeah. I think it would be, but adding bitflags together instead of
> > > doing bitwise ORs is very common as well.
>
Al,
I'd like to push this patchset to linux-next. Would you like to pull it
into your vfs tree, would you rather I submitted it separately, or do
you have any issues with it before including it?
This patchset was begun by Zach Brown and was originally submitted for
review in October, 2009.
From: Zach Brown
This adds a set of iov_iter_ops calls which work with memory which is
specified by an array of bio_vec structs instead of an array of iovec
structs.
The big difference is that the pages referenced by the bio_vec elements
are pinned. They don't need to be faulted in and we can
Signed-off-by: Dave Kleikamp
Cc: Steven Whitehouse
Cc: cluster-de...@redhat.com
---
fs/gfs2/file.c | 21 ++---
1 file changed, 10 insertions(+), 11 deletions(-)
diff --git a/fs/gfs2/file.c b/fs/gfs2/file.c
index 991ab2d..63af1a6 100644
--- a/fs/gfs2/file.c
+++ b/fs/gfs2/file.c
From: Zach Brown
This adds iocb cmds which specify that memory is held in iov_iter
structures. This lets kernel callers specify memory that can be
expressed in an iov_iter, which includes pages in bio_vec arrays.
Only kernel callers can provide an iov_iter so it doesn't make a lot of
sense to
btrfs can use generic_file_read_iter(). Base btrfs_file_write_iter()
on btrfs_file_aio_write(), then have the latter call the former.
Signed-off-by: Dave Kleikamp
Cc: Zach Brown
Cc: Chris Mason
Cc: linux-bt...@vger.kernel.org
---
fs/btrfs/file.c | 42 ++
On Tuesday 29 January 2013, Alexey Brodkin wrote:
> in(out)_8/in(out)_be16/in(out)_le16 are very powerpc/microblaze
> specific. To enable use of Xilinx System ACE driver build for other
> architectures (for example it's possible to use it on Xilinx ml-509
> board with ARC700 in FPGA) we need to
Signed-off-by: Dave Kleikamp
Cc: Artem Bityutskiy
Cc: Adrian Hunter
Cc: linux-...@lists.infradead.org
---
fs/ubifs/file.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/fs/ubifs/file.c b/fs/ubifs/file.c
index 5bc7781..cfe6210 100644
--- a/fs/ubifs/file.c
+++
From: Zach Brown
This moves the current iov_iter functions behind an ops struct of
function pointers. The current iov_iter functions all work with memory
which is specified by iovec arrays of user space pointers.
This patch is part of a series that lets us specify memory with bio_vec
arrays of
Signed-off-by: Dave Kleikamp
Cc: Tyler Hicks
Cc: Dustin Kirkland
Cc: ecryp...@vger.kernel.org
---
fs/ecryptfs/file.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/fs/ecryptfs/file.c b/fs/ecryptfs/file.c
index d45ba45..5aaa180 100644
---
From: Zach Brown
ocfs2's .aio_read and .aio_write methods are changed to take
iov_iter and pass it to generic functions. Wrappers are made to pack
the iovecs into iters and call these new functions.
Signed-off-by: Dave Kleikamp
Cc: Zach Brown
Cc: Mark Fasheh
Cc: Joel Becker
Cc:
A future patch hides the internals of struct iov_iter, so fuse should
be using the supported interface.
Signed-off-by: Dave Kleikamp
Acked-by: Miklos Szeredi
Cc: fuse-de...@lists.sourceforge.net
---
fs/fuse/file.c | 29 -
1 file changed, 8 insertions(+), 21
Em Thu, Jan 24, 2013 at 11:45:58PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, Jan 25, 2013 at 10:44:44AM +0900, Namhyung Kim escreveu:
> > From: Namhyung Kim
> >
> > The ->counts field was never freed in the current code. Add
> > perf_evsel__free_counts() function to free it properly.
From: Asias He
Signed-off-by: Asias He
Signed-off-by: Dave Kleikamp
---
drivers/char/raw.c | 4 ++--
fs/block_dev.c | 19 +--
include/linux/fs.h | 4 ++--
3 files changed, 13 insertions(+), 14 deletions(-)
diff --git a/drivers/char/raw.c b/drivers/char/raw.c
index
swap_writepage can now call nfs's write_iter f_op, eliminating the need to
implement for the special-case direct_IO a_op. There is no longer a need to
pass the uio flag through the direct write path.
Signed-off-by: Dave Kleikamp
Acked-by: Rik van Riel
Cc: Mel Gorman
Cc: Trond Myklebust
Cc:
This patch implements the read_iter and write_iter file operations which
allow kernel code to initiate directIO. This allows the loop device to
read and write directly to the server, bypassing the page cache.
Signed-off-by: Dave Kleikamp
Cc: Zach Brown
Cc: Trond Myklebust
Cc:
From: Zach Brown
direct IO treats memory from user iovecs and memory from arrays of
kernel pages very differently. User memory is pinned and worked with in
batches while kernel pages are always pinned and don't require
additional processing.
Rather than try and provide an abstraction that
use the generic_file_read_iter(), create ext4_file_write_iter() based on
ext4_file_write(), and make ext4_file_write() a wrapper around
ext4_file_write_iter().
Signed-off-by: Dave Kleikamp
Cc: Zach Brown
Cc: "Theodore Ts'o"
Cc: Andreas Dilger
Cc: linux-e...@vger.kernel.org
---
fs/ext4/file.c
Signed-off-by: Dave Kleikamp
Cc: Jan Kara
---
fs/udf/file.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/udf/file.c b/fs/udf/file.c
index c4164dc..a5d69c0 100644
--- a/fs/udf/file.c
+++ b/fs/udf/file.c
@@ -133,8 +133,8 @@ const struct
From: Zach Brown
Right now only callers of generic_perform_write() pack their iovec
arguments into an iov_iter structure. All the callers higher up in the
stack work on raw iovec arguments.
This patch introduces the use of the iov_iter abstraction higher up the
stack. Private generic path
Signed-off-by: Dave Kleikamp
Cc: David Howells
Cc: linux-...@lists.infradead.org
---
fs/afs/file.c | 4 ++--
fs/afs/internal.h | 3 +--
fs/afs/write.c| 9 -
3 files changed, 7 insertions(+), 9 deletions(-)
diff --git a/fs/afs/file.c b/fs/afs/file.c
index 8f6e923..27b9b66 100644
From: Zach Brown
Signed-off-by: Dave Kleikamp
Cc: Zach Brown
---
include/linux/bio.h | 8
1 file changed, 8 insertions(+)
diff --git a/include/linux/bio.h b/include/linux/bio.h
index 820e7aa..f5f9829 100644
--- a/include/linux/bio.h
+++ b/include/linux/bio.h
@@ -290,6 +290,14 @@
On Tue, 29 Jan 2013, KY Srinivasan wrote:
> > > I agree with you that your patch is valid for making the Hyper-V code more
> > robust but not for dealing
> > > with general issue of Xen emulating Hyper-V.
> >
> > What "general issue" would that be?
>
> Not all Hyper-V specific features are
On Tue, 2013-01-29 at 10:55 -0500, valdis.kletni...@vt.edu wrote:
> On Sun, 27 Jan 2013 23:19:47 +0300, Dan Carpenter said:
>
> > Yeah. I think it would be, but adding bitflags together instead of
> > doing bitwise ORs is very common as well.
>
> The fact it's common doesn't mean it's good
On Tuesday 29 January 2013, Viresh Kumar wrote:
> Adding Arnd in cc.
>
> On 29 January 2013 20:36, Andy Shevchenko
> wrote:
> > In some cases we got the device without dma_mask configured. We have to
> > apply
> > the default value to avoid crashes during memory mapping.
> >
> > Signed-off-by:
in(out)_8/in(out)_be16/in(out)_le16 are very powerpc/microblaze
specific. To enable use of Xilinx System ACE driver build for other
architectures (for example it's possible to use it on Xilinx ml-509
board with ARC700 in FPGA) we need to use generic implementation of
accessors.
Current
On 01/29/2013 09:54 AM, Ruslan Bilovol wrote:
> Hi,
>
> The following patches update cpuinfo to print CPU
> model name for ARM. First patch exactly makes needed
> changes for ARM architecture.
> Second patch adds this ability to OMAP4 SoCs.
>
> This adds a common approach to show SoC name.
>
>
On Tue, Jan 29, 2013 at 05:54:24PM +0200, Ruslan Bilovol wrote:
> CPU implementer : 0x41
> CPU name: OMAP4470 ES1.0 HS
Sigh. No. Look at what you're doing - look carefully at the above.
"CPU implementer" - 0x41. That's A. For ARM Ltd. ARM Ltd implemented
this CPU. Did ARM Ltd
> -Original Message-
> From: Stefano Stabellini [mailto:stefano.stabell...@eu.citrix.com]
> Sent: Tuesday, January 29, 2013 10:31 AM
> To: KY Srinivasan
> Cc: Olaf Hering; Jan Beulich; Stefano Stabellini; Greg KH; linux-
> ker...@vger.kernel.org
> Subject: RE: [PATCH] x86: Hyper-V:
Added Cc: linux-pm.
On Jan 29 Mark Einon wrote:
> On 28 January 2013 23:01, Stefan Richter wrote:
> > On Jan 28 Mark Einon wrote:
> >> This patch fixes the kernel warning generated when putting an MSI MS-1727
> >> GT740 laptop into suspend mode. The call sequence in this case calls
> >>
On my system one of the tests failed with
"Fatal error: exception Failure("No OCaml compiler found! Install either
ocamlopt or ocamlopt.opt")".
Investigating such issues is easier if the executed command line is being shown.
Signed-off-by: Bernd Schubert
CC: Julia Lawall
CC: Nicolas Palix
Do not run with verbosity on/off depending on the ONLINE variable,
which gets set with C=1 or C=2, but allow the user to set the
verbosity using kernel default make V= paramemter.
Verbosity is off by default now.
Signed-off-by: Bernd Schubert
CC: Julia Lawall
CC: Nicolas Palix
CC:
On 17:54-20130129, Ruslan Bilovol wrote:
> Hi,
>
> The following patches update cpuinfo to print CPU
> model name for ARM. First patch exactly makes needed
> changes for ARM architecture.
> Second patch adds this ability to OMAP4 SoCs.
>
> This adds a common approach to s
On Tue, Jan 29, 2013 at 10:34:53AM -0500, Alan Stern wrote:
> On Mon, 28 Jan 2013, Russell King - ARM Linux wrote:
>
> > On Mon, Jan 28, 2013 at 10:17:33AM -0500, Alan Stern wrote:
> > > On Mon, 28 Jan 2013, Roger Quadros wrote:
> > >
> > > > Make use of devm_request_and_ioremap() and correct
Dear Florian Fainelli,
On Tue, 29 Jan 2013 16:24:08 +0100, Florian Fainelli wrote:
> This patch converts the Marvell MV643XX ethernet driver to use the
> Marvell Orion MDIO driver. As a result, PowerPC and ARM platforms
> registering the Marvell MV643XX ethernet driver are also updated to
>
On Sun, 27 Jan 2013 13:40:40 -0800, Hugh Dickins said:
> My reservations so far would be: how many installations actually have
> more than one swap area, so is it a good tradeoff to add more overhead
> to help those at the (slight) expense of everyone else? The increasingly
> ugly page_mapping()
On Sun, 27 Jan 2013 23:19:47 +0300, Dan Carpenter said:
> Yeah. I think it would be, but adding bitflags together instead of
> doing bitwise ORs is very common as well.
The fact it's common doesn't mean it's good programming practice,
or even correct. Consider:
#define F_FOO 0x01
#define
If an OF node doesn't specify an interrupt property, 'uioinfo->irq'
will be assigned to the UIO_IRQ_NONE value meaning no interrupt
support. Trying to re-setup the irq later results in an error again
and probing fails. To prevent this do not try to re-setup the irq
if it was configured to
Set up the CPU model name during OMAP ID initialisation
so it will be displayed in /proc/cpuinfo:
/ # cat proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 10 (v7l)
BogoMIPS: 1590.23
Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls
CPU
Hi,
The following patches update cpuinfo to print CPU
model name for ARM. First patch exactly makes needed
changes for ARM architecture.
Second patch adds this ability to OMAP4 SoCs.
This adds a common approach to show SoC name.
Looks like there were few attempts to do similar
changes to
Currently, reading /proc/cpuinfo provides userspace with CPU ID of
the CPU carrying out the read from the file.
Userspace using this information may decide what module
to load or how to configure some specific (and processor-depended)
settings or so.
However, since really different SoCs can share
Am 29.01.2013 12:11, schrieb Alexander Holler:
To explain the problem on shutdown a bit further, I think the following
happens (usb and driver are statically linked and started by the kernel):
shutdown -> kill signal -> usb stack shuts down -> udlfb waits (forever)
for a kill or an urb which
On Mon, Jan 28, 2013 at 06:49:55PM +0100, Stephane Eranian wrote:
> On Sun, Jan 27, 2013 at 6:33 PM, Jiri Olsa wrote:
> > hi,
> > I was looking at the offcore stuff and it looks like we might
> > be missing some constraints for offcore response events on
> > Sandy/IvyBridge.
> >
> > The table
Dear Florian Fainelli,
On Tue, 29 Jan 2013 16:24:07 +0100, Florian Fainelli wrote:
> This patch changes the Marvell MDIO driver to be registered by using
> both Device Tree and platform device methods. The driver voluntarily
> does not use devm_ioremap() to share the same error path for Device
Hi Linus,
Please pull these fixes for XFS. Here are fixes for returning
EFSCORRUPTED on probe of a non-xfs filesystem, the stack switch in
xfs_bmapi_allocate, a crash in _xfs_buf_find, speculative
preallocation as the filesystem nears ENOSPC, an unmount hang, a race
with AIO, and
Dear Florian Fainelli,
On Tue, 29 Jan 2013 16:24:06 +0100, Florian Fainelli wrote:
> #define MVMDIO_SMI_DATA_SHIFT 0
> #define MVMDIO_SMI_PHY_ADDR_SHIFT 16
> @@ -36,12 +40,28 @@
> #define MVMDIO_SMI_WRITE_OPERATION 0
> #define MVMDIO_SMI_READ_VALID
On 01/29/2013 04:32 PM, Thomas Petazzoni wrote:
Dear Florian Fainelli,
On Tue, 29 Jan 2013 16:24:04 +0100, Florian Fainelli wrote:
Fix the driver remove callback to unmap the base register address and
not leak this mapping after the driver has been removed.
Signed-off-by: Florian Fainelli
On Mon, 28 Jan 2013, Russell King - ARM Linux wrote:
> On Mon, Jan 28, 2013 at 10:17:33AM -0500, Alan Stern wrote:
> > On Mon, 28 Jan 2013, Roger Quadros wrote:
> >
> > > Make use of devm_request_and_ioremap() and correct comment.
> >
> > Didn't a big patch come through recently converting all
It seems there are about 80 new, but undocumented addtions at
the top level Documentation directory. This fixes up the top
level 00-INDEX by adding new entries and deleting a couple orphans.
Some subdirs could probably still use a check/cleanup too though.
Cc: Rob Landley
Signed-off-by: Paul
The BeagleBone dev kit uses the built-in RTC module, so
it would be nice to have this built by default in the
omap2plus defconfig.
Signed-off-by: Mark Jackson
---
arch/arm/configs/omap2plus_defconfig |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/omap2plus_defconfig
Dear Florian Fainelli,
On Tue, 29 Jan 2013 16:24:05 +0100, Florian Fainelli wrote:
> This patch renames the base register cookie in the mvmdio drive from
> "smireg" to "regs" since a subsequent patch is going to use an ioremap()
> cookie whose size is larger than a single register of 4 bytes. No
On 01/29/2013 05:30 PM, Alan Stern wrote:
> On Tue, 29 Jan 2013, Roger Quadros wrote:
>
>> For each port that is in PHY mode we obtain a PHY device using the USB PHY
>> library and put it out of suspend.
>>
>> It is up to platform code to associate the PHY to the controller's
>> port and it is
Hi Mike,
On Tue, Jan 29, 2013 at 05:42:43PM +0400, Mike Lykov wrote:
>
> So my questions:
>
> 1. Are there a BUG in soft lockup detection mechanizm? Changing
> watchdog_thresh to 30 have a side effect in production - D-state
> userspace processes will be detected slowly. Are there a need to
>
Dear Florian Fainelli,
On Tue, 29 Jan 2013 16:24:04 +0100, Florian Fainelli wrote:
> Fix the driver remove callback to unmap the base register address and
> not leak this mapping after the driver has been removed.
>
> Signed-off-by: Florian Fainelli
What about using devm_request_and_ioremap()
On Tue, 29 Jan 2013, KY Srinivasan wrote:
> > The patch which started this thread is still valid because it enables
> > feature B only if the featurebit for B is enabled.
>
> Why would we need this if we have some other way of detecting that Hyper-V is
> being
> emulated.
I don't think that
On Tue, 29 Jan 2013, Roger Quadros wrote:
> For each port that is in PHY mode we obtain a PHY device using the USB PHY
> library and put it out of suspend.
>
> It is up to platform code to associate the PHY to the controller's
> port and it is upto the PHY driver to manage the PHY's resources.
On Sat, 2013-01-26 at 15:19 -0800, Yinghai Lu wrote:
> On Sat, Jan 26, 2013 at 2:41 PM, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > There is no guarantee that acpi_bus_scan() and acpi_bus_trim() will
> > not be run in parallel for the same scope of the ACPI namespace,
> > which
This patch converts the Marvell MV643XX ethernet driver to use the
Marvell Orion MDIO driver. As a result, PowerPC and ARM platforms
registering the Marvell MV643XX ethernet driver are also updated to
register a Marvell Orion MDIO driver. This driver voluntarily overlaps
with the Marvell Ethernet
Hi all,
This patch converts the mv643xx_eth driver to use the mvmdio MDIO bus driver
instead of rolling its own implementation. As a result, all users of this
mv643xx_eth driver are converted to register an "orion-mdio" platform_device.
The mvmdio driver is also updated to support an interrupt
This patch renames the base register cookie in the mvmdio drive from
"smireg" to "regs" since a subsequent patch is going to use an ioremap()
cookie whose size is larger than a single register of 4 bytes. No
functionnal code change introduced.
Signed-off-by: Florian Fainelli
---
Fix the driver remove callback to unmap the base register address and
not leak this mapping after the driver has been removed.
Signed-off-by: Florian Fainelli
---
drivers/net/ethernet/marvell/mvmdio.c |3 +++
1 file changed, 3 insertions(+)
diff --git
On 01/29/2013 04:17 PM, Stefan Weinhuber wrote:
Hannes Reinecke wrote on 2013-01-29 08:12:00:
[..]
+static ssize_t
+dasd_timeout_store(struct device *dev, struct device_attribute *attr,
+ const char *buf, size_t count)
+{
+ struct dasd_device *device;
+ struct request_queue *q;
+
On Tue, Jan 29, 2013 at 10:52 AM, Mika Westerberg
wrote:
> We had a discusssion about this with Andy as well. The thing is that there
> is no way in current resource to pass DMA request line numbers supported by
> the controller to the driver in a generic way. We on the other hand have to
> deal
This patch changes the Marvell MDIO driver to be registered by using
both Device Tree and platform device methods. The driver voluntarily
does not use devm_ioremap() to share the same error path for Device Tree
and non-Device Tree cases.
Signed-off-by: Florian Fainelli
---
This patch enhances the "mvmdio" to support a SMI error/done interrupt
line which can be used along with a wait queue instead of doing
busy-waiting on the registers. This is a feature which is available in
the mv643xx_eth SMI code and thus reduces again the gap between the two.
Signed-off-by:
On 01/25/2013 05:40 PM, Peter Huewe wrote:
Found with coccicheck.
The semantic patch that makes this change is available
in scripts/coccinelle/api/memdup.cocci.
Signed-off-by: Peter Huewe
Signed-off-by: Rob Clark
---
drivers/staging/omapdrm/omap_gem.c |4 ++--
1 files changed, 2
Adding Arnd in cc.
On 29 January 2013 20:36, Andy Shevchenko
wrote:
> In some cases we got the device without dma_mask configured. We have to apply
> the default value to avoid crashes during memory mapping.
>
> Signed-off-by: Andy Shevchenko
> ---
> drivers/dma/dw_dmac.c |6 ++
> 1
On Tue, 29 Jan 2013, Vivek Gautam wrote:
> This change de-asserts vbus_gpio on suspend and
> re-asserts on resume in order to save power.
> NOTE, this change means no USB charging in suspend
> mode.
Doing this would mean USB devices could not wake up the system. This
would be unacceptable.
Hannes Reinecke wrote on 2013-01-29 08:12:00:
[..]
> +static ssize_t
> +dasd_timeout_store(struct device *dev, struct device_attribute *attr,
> + const char *buf, size_t count)
> +{
> + struct dasd_device *device;
> + struct request_queue *q;
> + unsigned long val, flags;
> +
> +
On Tue, Jan 29, 2013 at 05:06:24PM +0200, Alexander Shishkin wrote:
> Michael Chan writes:
>
> > From: Stephen Hurd
> >
> > Add support for the UART device present in Broadcom TruManage capable
> > NetXtreme chips (ie: 5761m 5762, and 5725).
> >
> > This implementation has a hidden transmit
> -Original Message-
> From: Olaf Hering [mailto:o...@aepfle.de]
> Sent: Tuesday, January 29, 2013 4:27 AM
> To: Jan Beulich
> Cc: Stefano Stabellini; KY Srinivasan; Greg KH; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] x86: Hyper-V: register clocksource only if its advertised
>
On Mon, Jan 28, 2013 at 10:57:23AM -0500, David Teigland wrote:
> On Fri, Jan 25, 2013 at 05:31:08PM -0800, Tejun Heo wrote:
> > idr_destroy() can destroy idr by itself and idr_remove_all() is being
> > deprecated.
> >
> > The conversion isn't completely trivial for recover_idr_clear() as
> >
On Tue, 2013-01-29 at 08:53 -0600, Rob Herring wrote:
> If you specify to use the builtin's, do you still get inline rev
> instructions emitted?
You mean from the architecture's __arch_swab32() et al. macros?
No. If the architecture enables ARCH_USE_BUILTIN_BSWAP and the compiler
version checks
In some cases we got the device without dma_mask configured. We have to apply
the default value to avoid crashes during memory mapping.
Signed-off-by: Andy Shevchenko
---
drivers/dma/dw_dmac.c |6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/dma/dw_dmac.c
Michael Chan writes:
> From: Stephen Hurd
>
> Add support for the UART device present in Broadcom TruManage capable
> NetXtreme chips (ie: 5761m 5762, and 5725).
>
> This implementation has a hidden transmit FIFO, so running in single-byte
> interrupt mode results in too many interrupts. The
On Tue, 2013-01-29 at 12:28 +0100, Rafael J. Wysocki wrote:
> On Monday, January 28, 2013 07:35:39 PM Toshi Kani wrote:
> > On Mon, 2013-01-28 at 13:59 +0100, Rafael J. Wysocki wrote:
> > > From: Rafael J. Wysocki
> > >
> > > Introduce struct acpi_scan_handler for representing objects that
> > >
On Fri, 2013-01-25 at 18:20 +0800, Jovi Zhang wrote:
> >From ac499cd340bf2ba47b3d1dd129a3bb7527c195ae Mon Sep 17 00:00:00 2001
> From: Jovi Zhang
> Date: Fri, 25 Jan 2013 18:03:07 +0800
> Subject: [PATCH] tracing: fix twice trace iterator init
>
> trace iterator is already inited in
On Tue, Jan 29, 2013 at 01:51:34PM +, Lan, Tianyu wrote:
> Hi greg:
> My pleasure. I have sent the patch to you and usb mailist yesterday.
> http://marc.info/?l=linux-usb=135939249906217=2
> So please have a check.
Ah, got it, sorry, I missed it in my large "todo" mbox.
greg k-h
Return value for an empty phandle was -EEXIST before commit 15c9a0ac, that
changed the return value in this case to -ENOENT. However, of_gpio_named_count
relies upon the return value to be -EEXIST and relies upon being able to
distinguish this case from the case of no list at all which also
On Wed, 2013-01-09 at 12:45 +0100, Arend van Spriel wrote:
> Maybe this one is already known, but I did not find a post about it. So
> here it is.
>
> Regards,
> Arend
[snip]
> [9.589986] =
> [9.595365] [ INFO: possible recursive locking
This patch series fixes a bug where of_gpio_named count relied upon a return
value that was no longer returned from of_parse_phandle_with_args and adds the
possibility for of_gpio_named_count to return error values.
In addition, for of_spi_register_master it fixes a bug, adds documentation,
adds
Using memset does not set an array of integers properly
Signed-off-by: Andreas Larsson
---
drivers/spi/spi.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
index 9c2acf1..a4baa0a 100644
--- a/drivers/spi/spi.c
+++
On Mon 21-01-13 22:00:08, Jan Kara wrote:
> On Thu 17-01-13 15:50:29, Andrew Morton wrote:
> > On Fri, 18 Jan 2013 00:46:14 +0100
> > Jan Kara wrote:
> >
> > > On Thu 17-01-13 13:39:17, Andrew Morton wrote:
> > > > On Thu, 17 Jan 2013 22:04:42 +0100
> > > > Jan Kara wrote:
> > > >
> > > > >
When using a gpio chip select with a OF_GPIO_ACTIVE_LOW flag, this needs to be
known to the controller driver.
Signed-off-by: Andreas Larsson
---
Documentation/devicetree/bindings/spi/spi-bus.txt |3 +-
drivers/spi/spi.c | 24 ++--
This lets of_gpio_named_count return an errno on errors by being able to
distinguish between reaching the end of the phandle list and getting some other
error from of_parse_phandle_with_args.
Return error from of_spi_register_master when there is an "cs-gpios" list for
which gp_gpio_named_count
On 01/28/2013 07:30 PM, Kim Phillips wrote:
> Enable the compiler intrinsic for byte swapping on arch ARM. This
> allows the compiler to detect and be able to optimize out byte
> swappings, e.g. in big endian to big endian moves.
>
> AFAICT, arm gcc got __builtin_bswap{32,64} support in 4.6,
>
Holes in the cs-gpios DT phandle list is supposed to mark that native
chipselects is to be used. The value returned from of_get_named_gpio_flags in
this case is -EEXIST. By initializing cs_gpios and cs_gpio with -EEXIST, this
and only this errno will indicate to a spi controller driver that a
This adds missing kernel-doc entries for cs_gpios in struct spi_master and
cs_gpio in struct spi_device.
Signed-off-by: Andreas Larsson
---
include/linux/spi/spi.h |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
index
By shuffling the code, reduce a few ifdefs in firmware_class.c.
Also, firmware_buf fmt field is changed to is_pages_buf boolean for
simplification.
Signed-off-by: Takashi Iwai
---
drivers/base/firmware_class.c | 369 --
1 file changed, 179 insertions(+),
Hi Ming,
here is the revised patch series after your review.
In addition to points you suggested, I changed the return value of
_request_firmware_prepare() to be more naturally processed, and fixed
one forgotten unbalanced put_device() call.
The rest are same as the former version, just adapted
Since 3.7 kernel, the firmware loader can read the firmware files
directly, and the traditional user-mode helper is invoked only as a
fallback. This seems working pretty well, and the next step would be
to reduce the redundant user-mode helper stuff in future.
This patch is a preparation for
FW_STATUS_ABORT can be set only during the user-helper invocation,
thus we can ignore the check when CONFIG_HW_LOADER_USER_HELPER is
disabled.
Signed-off-by: Takashi Iwai
---
drivers/base/firmware_class.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git
This patch adds a new kconfig, CONFIG_FW_LOADER_USER_HELPER, and
guards the user-helper codes in firmware_class.c with ifdefs.
Yeah, yeah, there are lots of ifdefs in this patch. The further
clean-up with code shuffling follows in the next.
Signed-off-by: Takashi Iwai
---
drivers/base/Kconfig
401 - 500 of 1454 matches
Mail list logo
