These patches add support for the Aculab E1/T1 cPCI carrier card to the
natsemi driver. The first patch provides support for using the MII port
with no PHY and the second adds the quirk required to configure the
card.
--
You grabbed my hand and we fell into it, like a daydream - or a fever.
-
To
Aculab E1/T1 PMXc cPCI carrier card cards present a natsemi on the cPCI
bus with an oversized EEPROM using a direct MII-MII connection with no
PHY. This patch adds a new device table entry supporting these cards.
Signed-Off-By: Mark Brown [EMAIL PROTECTED]
Index: linux/drivers/net/natsemi.c
the MII
ioctl()s.
This is useful for systems where the device is connected without a PHY
or where either information or actions outside the scope of the driver
are required in order to use the PHYs.
Signed-Off-By: Mark Brown [EMAIL PROTECTED]
---
Previous versions of this patch exposed the new
On Wed, Feb 14, 2007 at 03:28:34PM +0200, Ahmed S. Darwish wrote:
A trivial comment actually, Is there a point to write multi-line comments
in two different formats ?
No goal in doing that, no - it wasn't a conscious decision.
--
You grabbed my hand and we fell into it, like a daydream - or
These patches add support for the Aculab E1/T1 cPCI carrier card to the
natsemi driver. The first patch provides support for using the MII port
with no PHY and the second adds the quirks required to detect and
configure the card.
This revision should address the issues raised by Jeff over the
Aculab E1/T1 PMXc cPCI carrier card cards present a natsemi on the cPCI
bus with an oversized EEPROM using a direct MII-MII connection with no
PHY. This patch adds a new device table entry supporting these cards.
Signed-Off-By: Mark Brown [EMAIL PROTECTED]
---
This revision removes extra
the MII
ioctl()s.
This is useful for systems where the device is connected without a PHY
or where either information or actions outside the scope of the driver
are required in order to use the PHYs.
Signed-Off-By: Mark Brown [EMAIL PROTECTED]
---
This revision of the patch fixes some issues brought
for the vanilla cards.
This patch fixes the problem minimally.
Signed-Off-By: Mark Brown [EMAIL PROTECTED]
--- linux.orig/drivers/net/natsemi.c2007-02-23 11:13:03.0 +
+++ linux/drivers/net/natsemi.c 2007-02-23 11:12:00.0 +
@@ -260,7 +260,7 @@
static const struct
On Fri, Feb 23, 2007 at 07:47:40AM -0600, Bob Tracy wrote:
ACK except for a missing comma at the end of the line being replaced,
which prevents the patch from applying cleanly. Otherwise, this fixes
the problem I was having. Thanks!
Aargh.
--- linux.orig/drivers/net/natsemi.c2007-02-23
for the vanilla cards.
This patch fixes the problem minimally.
Signed-Off-By: Mark Brown [EMAIL PROTECTED]
--- linux.orig/drivers/net/natsemi.c2007-02-23 11:13:03.0 +
+++ linux/drivers/net/natsemi.c 2007-02-23 11:12:00.0 +
@@ -260,7 +260,7 @@
static const struct
-by: Graeme Gregory [EMAIL PROTECTED]
Signed-off-by: Mike Arthur [EMAIL PROTECTED]
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Cc: Stanley Cai [EMAIL PROTECTED]
Cc: Rodolfo Giometti [EMAIL PROTECTED]
Cc: Russell King [EMAIL PROTECTED]
Cc: Marc Kleine-Budde [EMAIL PROTECTED]
Cc: Ian Molton [EMAIL PROTECTED
Signed-off-by: Liam Girdwood [EMAIL PROTECTED]
Signed-off-by: Graeme Gregory [EMAIL PROTECTED]
Signed-off-by: Mike Arthur [EMAIL PROTECTED]
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Cc: Stanley Cai [EMAIL PROTECTED]
Cc: Rodolfo Giometti [EMAIL PROTECTED]
Cc: Russell King [EMAIL PROTECTED]
Cc
Signed-off-by: Liam Girdwood [EMAIL PROTECTED]
Signed-off-by: Graeme Gregory [EMAIL PROTECTED]
Signed-off-by: Mike Arthur [EMAIL PROTECTED]
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Cc: Stanley Cai [EMAIL PROTECTED]
Cc: Rodolfo Giometti [EMAIL PROTECTED]
Cc: Russell King [EMAIL PROTECTED]
Cc
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Signed-off-by: Liam Girdwood [EMAIL PROTECTED]
---
MAINTAINERS|9 ++
drivers/input/touchscreen/Kconfig | 52
drivers/input/touchscreen/Makefile | 17 +++
3 files changed
Signed-off-by: Liam Girdwood [EMAIL PROTECTED]
Signed-off-by: Graeme Gregory [EMAIL PROTECTED]
Signed-off-by: Mike Arthur [EMAIL PROTECTED]
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Cc: Stanley Cai [EMAIL PROTECTED]
Cc: Rodolfo Giometti [EMAIL PROTECTED]
Cc: Russell King [EMAIL PROTECTED]
Cc
Signed-off-by: Liam Girdwood [EMAIL PROTECTED]
Signed-off-by: Graeme Gregory [EMAIL PROTECTED]
Signed-off-by: Mike Arthur [EMAIL PROTECTED]
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Cc: Stanley Cai [EMAIL PROTECTED]
Cc: Rodolfo Giometti [EMAIL PROTECTED]
Cc: Russell King [EMAIL PROTECTED]
Cc
On Thu, Jan 10, 2008 at 04:41:18PM +0100, Sam Ravnborg wrote:
On Thu, Jan 10, 2008 at 11:51:10AM +, Mark Brown wrote:
+wm97xx-ts-objs := wm97xx-core.o
Use
wm97xx-ts-y := wm97xx-core.o
+wm97xx-ts-objs += wm9713.o
+endif
So this becomes:
wm97xx-ts-$(CONFIG_TOUCHSCREEN_WM9713
On Mon, Jan 14, 2008 at 10:56:06AM +0100, Marc Kleine-Budde wrote:
reMark Brown wrote:
Cc: Marc Kleine-Budde [EMAIL PROTECTED]
^^
it's [EMAIL PROTECTED]
Fixed, sorry about that.
+ /* use PEN_DOWN GPIO 13 to assert IRQ on GPIO line 2 */
On Mon, Jan 14, 2008 at 04:06:46PM +0100, Marc Kleine-Budde wrote:
Mark Brown wrote:
On Mon, Jan 14, 2008 at 10:56:06AM +0100, Marc Kleine-Budde wrote:
The driver really isn't intended to cope with them. As you say, other
boards may have things wired up differently and therefore require
On Mon, Feb 11, 2008 at 07:00:30PM -0500, Pete MacKay wrote:
In wm97xx-core.c, should
+int wm97xx_resume(struct device *dev)
be static?
Also, should
Yes, and in fact I had both fixes present in the development branch but
had forgotten to cherry pick them over into the upstream branch -
Signed-off-by: Liam Girdwood [EMAIL PROTECTED]
Signed-off-by: Graeme Gregory [EMAIL PROTECTED]
Signed-off-by: Mike Arthur [EMAIL PROTECTED]
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Cc: Dmitry Baryshkov [EMAIL PROTECTED]
Cc: Stanley Cai [EMAIL PROTECTED]
Cc: Rodolfo Giometti [EMAIL PROTECTED]
Cc
Signed-off-by: Liam Girdwood [EMAIL PROTECTED]
Signed-off-by: Graeme Gregory [EMAIL PROTECTED]
Signed-off-by: Mike Arthur [EMAIL PROTECTED]
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Cc: Dmitry Baryshkov [EMAIL PROTECTED]
Cc: Stanley Cai [EMAIL PROTECTED]
Cc: Rodolfo Giometti [EMAIL PROTECTED]
Cc
Signed-off-by: Liam Girdwood [EMAIL PROTECTED]
Signed-off-by: Graeme Gregory [EMAIL PROTECTED]
Signed-off-by: Mike Arthur [EMAIL PROTECTED]
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Cc: Dmitry Baryshkov [EMAIL PROTECTED]
Cc: Stanley Cai [EMAIL PROTECTED]
Cc: Rodolfo Giometti [EMAIL PROTECTED]
Cc
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Signed-off-by: Liam Girdwood [EMAIL PROTECTED]
---
MAINTAINERS|9 ++
drivers/input/touchscreen/Kconfig | 52
drivers/input/touchscreen/Makefile |7 +
3 files changed, 68
This patch series adds support for the touchscreen controllers provided
by Wolfson Microelectronics WM97xx series chips in both polled and
streaming modes. The series can also be pulled via git from:
git://opensource.wolfsonmicro.com/linux-2.6-touch upstream
This version incorporates
On Tue, Feb 12, 2008 at 11:28:43PM -0500, Pete MacKay wrote:
We're using the wm9712 codec with the sound/soc/pxa code configured in and
came across this build error:
Which kernel version are you building against? I've been testing with
v2.6.24 (and have just updated to v2.6.25-rc1 which is
On Tue, Feb 12, 2008 at 10:58:50PM +, Dmitry Baryshkov wrote:
You used platform_device_register, but should be using platform_device_add,
otherwise you get barfs with 2.6.25-rc1 (device is initialized twice). Also
Thanks for that. I feel like I should knock up a patch to clarify the
This patch series adds support for the touchscreen controllers provided
by Wolfson Microelectronics WM97xx series chips in both polled and
streaming modes. The series can also be pulled via git from:
git://opensource.wolfsonmicro.com/linux-2.6-touch upstream
This version:
- Has been
Signed-off-by: Liam Girdwood [EMAIL PROTECTED]
Signed-off-by: Graeme Gregory [EMAIL PROTECTED]
Signed-off-by: Mike Arthur [EMAIL PROTECTED]
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Cc: Dmitry Baryshkov [EMAIL PROTECTED]
Cc: Stanley Cai [EMAIL PROTECTED]
Cc: Rodolfo Giometti [EMAIL PROTECTED]
Cc
Signed-off-by: Liam Girdwood [EMAIL PROTECTED]
Signed-off-by: Graeme Gregory [EMAIL PROTECTED]
Signed-off-by: Mike Arthur [EMAIL PROTECTED]
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Cc: Dmitry Baryshkov [EMAIL PROTECTED]
Cc: Stanley Cai [EMAIL PROTECTED]
Cc: Rodolfo Giometti [EMAIL PROTECTED]
Cc
]
Signed-off-by: Graeme Gregory [EMAIL PROTECTED]
Signed-off-by: Mike Arthur [EMAIL PROTECTED]
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Cc: Dmitry Baryshkov [EMAIL PROTECTED]
Cc: Stanley Cai [EMAIL PROTECTED]
Cc: Rodolfo Giometti [EMAIL PROTECTED]
Cc: Russell King [EMAIL PROTECTED]
Cc: Pete MacKay
Signed-off-by: Liam Girdwood [EMAIL PROTECTED]
Signed-off-by: Graeme Gregory [EMAIL PROTECTED]
Signed-off-by: Mike Arthur [EMAIL PROTECTED]
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Cc: Dmitry Baryshkov [EMAIL PROTECTED]
Cc: Stanley Cai [EMAIL PROTECTED]
Cc: Rodolfo Giometti [EMAIL PROTECTED]
Cc
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Signed-off-by: Liam Girdwood [EMAIL PROTECTED]
---
MAINTAINERS| 10 +++
drivers/input/touchscreen/Kconfig | 52
drivers/input/touchscreen/Makefile |7 +
3 files changed, 69
Signed-off-by: Liam Girdwood [EMAIL PROTECTED]
Signed-off-by: Graeme Gregory [EMAIL PROTECTED]
Signed-off-by: Mike Arthur [EMAIL PROTECTED]
Signed-off-by: Mark Brown [EMAIL PROTECTED]
Cc: Dmitry Baryshkov [EMAIL PROTECTED]
Cc: Stanley Cai [EMAIL PROTECTED]
Cc: Rodolfo Giometti [EMAIL PROTECTED]
Cc
On Thu, Feb 14, 2008 at 06:10:19PM +0300, Dmitry wrote:
2008/2/13, Mark Brown [EMAIL PROTECTED]:
+#define WM97XX_ADCSEL_X0x1000 /* x coord measurement */
+#define WM97XX_ADCSEL_Y0x2000 /* y coord measurement */
+#define WM97XX_ADCSEL_PRES 0x3000
On Mon, Oct 29, 2012 at 09:49:01PM +0200, Felipe Balbi wrote:
On Fri, Oct 26, 2012 at 05:03:16PM +0100, Mark Brown wrote:
You could have the driver explicitly set the flag, it would just be one
extra line, but it seems marginally nicer to just do it.
You didn't get the whole picture I'm
On Sun, Oct 28, 2012 at 09:12:52PM +0100, Linus Walleij wrote:
The answer is that it does not know. Because drivers have
different needs. Depending on how the hardware and
system is done.
...
I'm not making this up, it is a very real phenomenon on the
Ux500 and I don't think we are unique.
On Tue, Oct 30, 2012 at 07:46:31AM +1100, Stephen Rothwell wrote:
Then you need to have a different branch being tested by Fenguang and
friends to what you have in linux-next. The stuff that you put into
linux-next has to be at least build tested, so you should delay pushing
it up to your
On Tue, Oct 30, 2012 at 01:49:49PM +0200, Felipe Balbi wrote:
On Tue, Oct 30, 2012 at 11:24:10AM +, Mark Brown wrote:
We need some place to put the SoC integration; power domains seem like
the obvious place to me but YMMV. Nothing about having this out of the
except that pin muxing
On Tue, Oct 30, 2012 at 03:02:23PM +0100, Linus Walleij wrote:
I worry that we will end up with power/resource domain
code that start to look like this:
suspend()
switch (device.id) {
case DEV_FOO:
clk_disable();
pinctrl_set_state();
power_domain_off();
case DEV_BAR:
Well, if
On Tue, Oct 30, 2012 at 03:16:02PM +0100, Linus Walleij wrote:
On Tue, Oct 30, 2012 at 3:07 PM, Mark Brown
Essentially all the patches I'm seeing adding pinctrl are totally
mindless, most of them are just doing the initial setup on boot and not
doing any active management at runtime at all
On Tue, Oct 30, 2012 at 11:13:34AM +0530, Laxman Dewangan wrote:
On Tuesday 30 October 2012 12:44 AM, Stephen Warren wrote:
I think it depends on DMAENGINE, not the specific driver now, doesn't it?
Taking example from the mfd, we depends on particular driver, not
from the core driver.
I
On Tue, Oct 30, 2012 at 05:16:42PM +0200, Felipe Balbi wrote:
On Tue, Oct 30, 2012 at 02:07:15PM +, Mark Brown wrote:
and all of that SoC-specific detail is already hidden behind power
domains, runtime PM, pinctrl, clk API, regulator framework, etc.
That's all getting rather open
On Tue, Oct 30, 2012 at 07:25:13PM +0200, Felipe Balbi wrote:
On Tue, Oct 30, 2012 at 03:58:21PM +, Mark Brown wrote:
But then this comes round to the mindless code that ought to be factored
out :) Only the more interesting cases that do something unusual really
register here.
fair
On Tue, Oct 30, 2012 at 12:34:05PM +0530, Laxman Dewangan wrote:
Tegra20/Tegra30 supports the spi interface through its SLINK
controller. Add spi driver for SLINK controller.
Applied, thanks.
signature.asc
Description: Digital signature
On Wed, Oct 31, 2012 at 04:00:17PM +0100, Grant Likely wrote:
For the API, I don't think it is a good idea at all to try and
abstract away gpios on multiple controllers. I understand that it
makes life a lot easier for userspace to abstract those details away,
but the problem is that it hides
On Thu, Nov 01, 2012 at 09:54:00AM +0100, Linus Walleij wrote:
Well, the pinctrl grabbers in these drivers are using these states also
for platforms that do not even select CONFIG_PM. For example
mach-nomadik is quite happy that the PL011 driver is thusly
muxing in its pins. And would
On Thu, Nov 01, 2012 at 03:01:28PM +0100, Linus Walleij wrote:
On Thu, Nov 1, 2012 at 1:07 PM, Mark Brown
For the pin hogging I'd actually been thinking separately that we should
just have the device core do a devm_pinctrl_get_set_default() prior to
probing the device and store the result
On Thu, Nov 01, 2012 at 02:02:36PM +0800, Axel Lin wrote:
Signed-off-by: Axel Lin axel@ingics.com
Applied, thanks.
signature.asc
Description: Digital signature
On Thu, Nov 01, 2012 at 11:48:42AM +0530, Ashish Jangam wrote:
This patch fixes this issue to by following any read or write with a dummy
read
to a safe register address. A safe register address is one where the contents
will not affect the operation of the system.
Apart from this the
On Tue, Oct 30, 2012 at 10:51:11PM +0100, Linus Walleij wrote:
On Tue, Oct 30, 2012 at 7:37 PM, Mark Brown
More seriously the amount of time we seem to have been spending recently
on changes which end up requiring us to go through essentially every
driver and add code to them (often
mapping can be done when
adding the sub device RTC.
Rewiewed-by: Mark Brown broo...@opensource.wolfsonmicro.com
signature.asc
Description: Digital signature
On Fri, Sep 14, 2012 at 03:05:46PM +0300, Peter Ujfalusi wrote:
With this parameter added to dmaengine_prep_dma_cyclic() the API will be in
sync with other dmaengine_prep_*() functions.
The dmaengine_prep_dma_cyclic() function primarily used by audio for cyclic
transfer required by ALSA, we
On Mon, Sep 10, 2012 at 01:46:18PM +0300, Peter Ujfalusi wrote:
Hello,
Applied all, thanks.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
On Thu, Sep 20, 2012 at 04:04:57PM -0600, Stephen Warren wrote:
Mark, if this gets into 3.7, I can fix up all the Tegra .dts files during 3.8.
I don't know which branch you generated this against but it doesn't
apply to any of the obvious branches in my regulator tree. There's a
modify/delete
On Tue, Sep 18, 2012 at 08:01:25AM -0400, Matt Porter wrote:
Adds pinctrl support to support OMAP platforms that boot from DT
and rely on pinctrl support to set pinmuxes.
Applied, thanks.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On Mon, Sep 17, 2012 at 04:51:20PM -0700, Guenter Roeck wrote:
The I2C core provides a means to instantiate devices from userspace
using sysfs attributes. Provide the same mechanism for SPI devices.
So, unlike I2C this is only going to work for a subset of controllers -
anything that relies on
On Tue, Sep 18, 2012 at 03:53:53PM +0200, Roland Stigge wrote:
Even with devicetree support, we needed platform data to provide some data,
leading to mixed device tree and platform data. This patch makes it possible
to
provide all that information via device tree. Now, the data must be
On Mon, Sep 24, 2012 at 02:36:25PM +0530, Ashish Jangam wrote:
Any update on this patch?
Don't top post or send contentless pings.
The general quality problems with your submissions don't encourage fast
review both technically and in terms of reviewer enthusiasm; for example
in this case the
On Mon, Sep 24, 2012 at 08:08:32PM +0200, Takashi Iwai wrote:
At Mon, 24 Sep 2012 10:17:15 +0200,
Mark, could you tell me when it's ready? Since I'll be off from
tomorrow, I'd like to resolve sooner.
My time is up, so I merged Peter's two patches on the top of for-next
branch of sound
On Mon, Sep 24, 2012 at 01:24:59PM -0600, Stephen Warren wrote:
From: Stephen Warren swar...@nvidia.com
As explained in patch 1, this series deprecates the regulator-compatible
DT property, and updates various binding documentation and examples for
this change.
Applied regulator patches,
On Wed, Sep 05, 2012 at 05:06:04PM +0530, Sourav Poddar wrote:
+static struct regmap_config smsc_regmap_config = {
+ .reg_bits = 8,
+ .val_bits = 8,
+ .max_register = SMSC_MAX_REGISTER - 1;
+ .cache_type = REGCACHE_COMPRESSED,
+};
That
On Wed, Sep 12, 2012 at 12:22:47PM +0200, cimina...@gnudd.com wrote:
From: Davide Ciminaghi cimina...@gnudd.com
A driver for the apb-soc registers is needed by the clock
infrastructure code to configure and control clocks on the sta2x11
chip.
Since some of the functions in sta2x11-mfd.c
.
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
---
include/linux/pageblock-flags.h |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/linux/pageblock-flags.h b/include/linux/pageblock-flags.h
index eed27f4..8d67f30 100644
--- a/include/linux
On Wed, Sep 26, 2012 at 04:56:15PM +0200, Davide Ciminaghi wrote:
On Tue, Sep 25, 2012 at 08:20:48PM +0100, Mark Brown wrote:
Glancing at the diff here this looks a lot like regmap-mmio... not sure
if it is or not, though.
that would be ideal, but I also need to deal with the common clock
On Wed, Sep 26, 2012 at 06:31:45PM +0200, Davide Ciminaghi wrote:
Oh, and there's another problem (I'm looking at the code right now, I had
forgotten about this): the clock framework also asks for a spinlock_t *.
Regmap has its own spinlock (or mutex), and I don't think it would be a
good
It can misreport.
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
---
drivers/mfd/arizona-irq.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mfd/arizona-irq.c b/drivers/mfd/arizona-irq.c
index f7886c8..ef0f2d0 100644
--- a/drivers/mfd/arizona-irq.c
+++ b/drivers
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
---
drivers/mfd/wm5110-tables.c | 96 ++-
1 file changed, 95 insertions(+), 1 deletion(-)
diff --git a/drivers/mfd/wm5110-tables.c b/drivers/mfd/wm5110-tables.c
index bd8782c..adda6b1 100644
On Thu, Sep 27, 2012 at 03:41:10PM +0200, Davide Ciminaghi wrote:
Maybe there's another solution: what about adding a couple of function
pointers (lock, unlock) to struct regmap_config ? If they're set to NULL,
everything works as usual. If they're not NULL, regmap uses such functions
to do
On Thu, Sep 27, 2012 at 12:55:35AM -0300, Fabio Estevam wrote:
From: Fabio Estevam fabio.este...@freescale.com
On a mx53qsb dt-kernel the da9052-core driver fails to probe:
da9052 1-0048: DA9052 ADC IRQ failed ret=-22
In request_threaded_irq() the first parameter is missing the
On Thu, Sep 27, 2012 at 02:34:45PM +, Arnd Bergmann wrote:
On Thursday 27 September 2012, Mark Brown wrote:
The driver shouldn't be relying on irq_base at all, it should use
regmap_get_virq() to look up the interrupt number. If it relies on
irq_base then the user is forced to assign
On Thu, Sep 27, 2012 at 07:22:38PM +0200, Joachim Eastwood wrote:
[ 13.14] sysfs: cannot create duplicate filename
'/devices/platform/ssc.0/atmel-ssc-dai.0'
[ 13.14] Modules linked in: snd_soc_mpa1600_wm8776(+)
Oh, dear. This is probably a genuine bug, triggered by but not really
On Thu, Sep 27, 2012 at 05:59:19PM +0200, Marek Szyprowski wrote:
On Thursday, September 27, 2012 1:29 PM Thierry Reding wrote:
any idea why CMA might be broken in next-20120926. I see that there
haven't been any major changes to CMA itself, but there's been quite a
bit of restructuring of
On Wed, Oct 03, 2012 at 09:23:36AM +0200, Paul Bolle wrote:
On Tue, 2012-10-02 at 20:11 -0400, valdis.kletni...@vt.edu wrote:
On Mon, 01 Oct 2012 11:03:21 +0100, Mark Brown said:
That implies that 'ret' will be set in the if-branch. ('val_count' could
be zero if 'val_len
This makes things consistent with the rest of the API and is actually what
the documentation says. We don't currently have any in tree users so low
cost.
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
---
drivers/base/regmap/regmap.c |4 ++--
include/linux/regmap.h
Rather than just returning a single error code for every possible thing we
can notice print an error message saying what the problem was. This makes
it very much easier to figure out what's wrong and fix it.
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
---
drivers/base/regmap
If a register range is named then provide a debugfs file showing the
contents of the range separately.
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
---
drivers/base/regmap/internal.h |1 +
drivers/base/regmap/regmap-debugfs.c | 31
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
---
drivers/regulator/lp8788-ldo.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/lp8788-ldo.c b/drivers/regulator/lp8788-ldo.c
index 6796eeb..e496ba0 100644
--- a/drivers/regulator/lp8788
For more useful diagnostics.
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
---
drivers/base/regmap/internal.h |1 +
drivers/base/regmap/regmap.c |1 +
include/linux/regmap.h |4
3 files changed, 6 insertions(+)
diff --git a/drivers/base/regmap
This will allow the use of the same code for reading register ranges.
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
---
drivers/base/regmap/regmap-debugfs.c | 19 ++-
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/drivers/base/regmap/regmap
On Wed, Oct 03, 2012 at 02:06:57PM -0300, Fabio Estevam wrote:
+ /* Allocate a virtual IRQ domain to distribute to the regmap domains */
+ da9052-virq = irq_domain_add_linear(NULL, ARRAY_SIZE(da9052_irqs),
+ da9052_domain_ops, da9052);
+
On Wed, Oct 03, 2012 at 01:04:33PM -0300, Fabio Estevam wrote:
On Mon, Oct 1, 2012 at 7:22 AM, Mark Brown
I don't understand what this irq_chip or the custom domain you're adding
are for?
I declared da9052_irq_chip because I do the following:
irq_set_chip_and_handler(virq
On Wed, Oct 03, 2012 at 07:03:13PM +0530, Ashish Jangam wrote:
Fix for da9052-core driver probe fail on a mx53qsb dt-kernel
da9052 1-0048: DA9052 ADC IRQ failed ret=-22
Signed-off-by: Ashish Jangam ashish.jan...@kpitcummins.com
Reviwed-by: Mark Brown broo...@opensource.wolfsonmicro.com
On Thu, Sep 27, 2012 at 11:22:02PM +0200, Roland Stigge wrote:
The recurring task of providing simultaneous access to GPIO lines (especially
for bit banging protocols) needs an appropriate API.
This patch adds a kernel internal Block GPIO API that enables simultaneous
access to several GPIOs
On Thu, Oct 04, 2012 at 07:12:48AM +, Arnd Bergmann wrote:
On Thursday 04 October 2012, Fabio Estevam wrote:
+int da9052_enable_irq(struct da9052 *da9052, int irq)
+{
+ irq = da9052_map_irq(da9052, irq);
+ if (irq 0)
+ return irq;
+
+
interrupts.
Reviewed-by: Mark Brown broo...@opensource.wolfsonmicro.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
as the interrupt
number in request_threaded_irq() without da9052-irq_base.
Reviwed-by: Mark Brown broo...@opensource.wolfsonmicro.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
On Thu, Oct 04, 2012 at 12:15:09AM -0300, Fabio Estevam wrote:
From: Fabio Estevam fabio.este...@freescale.com
Convert to the new da9052 interrupt functions, so that we can get rid of
irq_base references.
Reviewed-by: Mark Brown broo...@opensource.wolfsonmicro.com
--
To unsubscribe from
The range code was written to check for return codes less than zero as
errors but throughout the rest of the API return codes not equal to zero
are errors. Change all these checks to match the house style.
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
---
drivers/base/regmap
This will support a subsequent update to allow bulk writes to cross window
boundaries.
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
---
drivers/base/regmap/regmap.c | 91 +++---
1 file changed, 51 insertions(+), 40 deletions(-)
diff --git
If a block write covers a paged memory region and crosses a window
boundary then rather than failing the write split the transfer up
into multiple writes, making the whole process more transparent for
drivers.
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
---
drivers/base/regmap
On Fri, Aug 17, 2012 at 02:47:30PM +0300, Aaro Koskinen wrote:
Delete soon-obsolete e-mail address.
Applied, thanks.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Fri, Oct 05, 2012 at 01:09:13PM +0200, Drasko DRASKOVIC wrote:
Looping GPIO maintainers...
Please follow the patch submission process in
Documentation/SubmittingPatches - the main thing here is to not send the
patch as an attachment.
--
To unsubscribe from this list: send the line unsubscribe
on the off chance that it's sensible.
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
---
drivers/base/firmware_class.c |5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
index 8154145..a14eb92 100644
On Thu, Oct 04, 2012 at 12:15:07AM -0300, Fabio Estevam wrote:
From: Fabio Estevam fabio.este...@freescale.com
Use the new da9052 irq functions and allow the driver to probe successfully.
Reviewed-by: Mark Brown broo...@opensource.wolfsonmicro.com
--
To unsubscribe from this list: send
On Thu, Oct 04, 2012 at 12:15:08AM -0300, Fabio Estevam wrote:
From: Fabio Estevam fabio.este...@freescale.com
Convert to the new da9052 interrupt functions, so that we can get rid of
irq_base references.
Reviewed-by: Mark Brown broo...@opensource.wolfsonmicro.com
--
To unsubscribe from
On Fri, Oct 05, 2012 at 06:20:44PM -0400, valdis.kletni...@vt.edu wrote:
On Wed, 03 Oct 2012 09:23:36 +0200, Paul Bolle said:
That is another way to silence GCC here.
That's probably a preferable approach - that way, if a bogus val_count gets
passed in, the caller will be informed of the
On Sat, Oct 06, 2012 at 11:57:36AM +0200, Paul Bolle wrote:
2) I hope to send in a second path shortly, changing 'num' to size_t. My
main doubt is whether its problematic that the loop index in
regmap_volatile_range() uses unsigned int too. If 'num' would exceed
UINT_MAX, that loop would
On Sun, Nov 04, 2012 at 01:19:46PM -0700, Alexey Khoroshilov wrote:
If regmap_read() failed, arizona_micdet() returns IRQ_NONE
leaving info-lock mutex locked as opposed to all other return paths.
Found by Linux Driver Verification project (linuxtesting.org).
Acked-by: Mark Brown broo
On Sat, Nov 03, 2012 at 02:32:59PM -0500, Joel A Fernandes wrote:
beaglebone_defconfig: Add dummy regulator to init tlv320aic3x
https://github.com/joelagnel/linux-kernel/commit/db5672dfe548d82625cf40ed688d05ba7cee5c93
This should never be done in production, you should ensure that the
1 - 100 of 30621 matches
Mail list logo
