overed in U-Boot where the issue can be reproduced by
writing any size that is 1 byte less than a page-size multiple.
For example, on a NAND with 2K page (0x800):
=> nand erase.part
=> nand write $loadaddr 7ff
Signed-off-by: Hector Palacios <hector.palac...@digi.com>
overed in U-Boot where the issue can be reproduced by
writing any size that is 1 byte less than a page-size multiple.
For example, on a NAND with 2K page (0x800):
=> nand erase.part
=> nand write $loadaddr 7ff
Signed-off-by: Hector Palacios
---
drivers/mtd/nand/nand_base
cribe linux-iio" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Best regards,
--
Hector Palacios
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to major
linux-iio in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Best regards,
--
Hector Palacios
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
Dear Alexandre,
On 08/22/2013 12:13 AM, Alexandre Belloni wrote:
Hi Pawel,
On 14/08/2013 16:44, Pawel Moll wrote:
On Tue, 2013-08-13 at 22:23 +0100, Jonathan Cameron wrote:
On 07/22/13 15:04, Hector Palacios wrote:
Some LRADC channels have fixed pre-dividers so they can measure
different
Dear Alexandre,
On 08/22/2013 12:13 AM, Alexandre Belloni wrote:
Hi Pawel,
On 14/08/2013 16:44, Pawel Moll wrote:
On Tue, 2013-08-13 at 22:23 +0100, Jonathan Cameron wrote:
On 07/22/13 15:04, Hector Palacios wrote:
Some LRADC channels have fixed pre-dividers so they can measure
different
Hi Marcel,
On 07/29/2013 06:43 PM, Marcel Holtmann wrote:
Hi Hector,
The Atheros firmware download driver is not dependent on HCI
USB driver. This driver is needed to complement any Atheros
driver like BT_HCIUART_ATH3K.
Signed-off-by: Hector Palacios
CC: Suraj Sumangala
CC: Vikram
Hi Marcel,
On 07/29/2013 06:43 PM, Marcel Holtmann wrote:
Hi Hector,
The Atheros firmware download driver is not dependent on HCI
USB driver. This driver is needed to complement any Atheros
driver like BT_HCIUART_ATH3K.
Signed-off-by: Hector Palacios hector.palac...@digi.com
CC: Suraj
The Atheros firmware download driver is not dependent on HCI
USB driver. This driver is needed to complement any Atheros
driver like BT_HCIUART_ATH3K.
Signed-off-by: Hector Palacios
CC: Suraj Sumangala
CC: Vikram Kandukuri
---
drivers/bluetooth/Kconfig | 1 -
1 file changed, 1 deletion
The Atheros firmware download driver is not dependent on HCI
USB driver. This driver is needed to complement any Atheros
driver like BT_HCIUART_ATH3K.
Signed-off-by: Hector Palacios hector.palac...@digi.com
CC: Suraj Sumangala su...@atheros.com
CC: Vikram Kandukuri vikram.kanduk...@atheros.com
Dear Lars,
On 07/23/2013 10:46 AM, Lars-Peter Clausen wrote:
On 07/22/2013 04:04 PM, Hector Palacios wrote:
[...]
+static ssize_t mxs_lradc_show_scale_available_ch(struct device *dev,
+ struct device_attribute *attr,
+ char *buf,
+ int ch
Hello Marek,
On 07/23/2013 12:36 AM, Marek Vasut wrote:
Dear Hector Palacios,
Adds in_voltageX_scale_available file for every channel to read
the different available scales.
There are two scales per channel:
[0] = divider_by_two disabled (default)
[1] = divider_by_two enabled
The scale
Hello Marek,
On 07/23/2013 12:36 AM, Marek Vasut wrote:
Dear Hector Palacios,
Adds in_voltageX_scale_available file for every channel to read
the different available scales.
There are two scales per channel:
[0] = divider_by_two disabled (default)
[1] = divider_by_two enabled
The scale
Dear Lars,
On 07/23/2013 10:46 AM, Lars-Peter Clausen wrote:
On 07/22/2013 04:04 PM, Hector Palacios wrote:
[...]
+static ssize_t mxs_lradc_show_scale_available_ch(struct device *dev,
+ struct device_attribute *attr,
+ char *buf,
+ int ch
-by: Hector Palacios
---
drivers/staging/iio/adc/mxs-lradc.c | 112 +++-
1 file changed, 111 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/iio/adc/mxs-lradc.c
b/drivers/staging/iio/adc/mxs-lradc.c
index 5037577..5d332b1 100644
--- a/drivers/staging/iio
platform.
Could someone please test on an i.MX23?
Hector Palacios (5):
iio: mxs-lradc: change the realbits to 12
ARM: dts: add reference voltage property for MXS LRADC
iio: mxs-lradc: add scale attribute to channels
iio: mxs-lradc: add scale_available file to channels
iio: mxs-lradc: add
)
- allows to read the scaling attribute (computed from the Vref)
Signed-off-by: Hector Palacios .
Acked-by: Marek Vasut
---
drivers/staging/iio/adc/mxs-lradc.c | 77 +
1 file changed, 53 insertions(+), 24 deletions(-)
diff --git a/drivers/staging/iio/adc/mxs-lradc.c
Some LRADC channels have fixed pre-dividers so they can measure
different voltages at full scale. The reference voltage allows to
expose a scaling attribute through the IIO sysfs so that a user can
compute the real voltage out of a measured sample value.
Signed-off-by: Hector Palacios
Acked
.
Besides, the driver was using an 18 bit mask (LRADC_CH_VALUE_MASK) to
report touch coordinates to userland. A 12 bit mask should be used instead
or else the touch libraries will expect a coordinates range between 0
and 0x3 (18 bits), instead of between 0 and 0xfff (12 bits).
Signed-off-by: Hector
Added write_raw function to manipulate the optional divider_by_two
through the scaling attribute out of the available scales.
Signed-off-by: Hector Palacios
---
drivers/staging/iio/adc/mxs-lradc.c | 56 -
1 file changed, 55 insertions(+), 1 deletion(-)
diff
I'm happy either way.
I prefer the struct approach, it removes one dimension to the array and I find
it cleaner.
Best regards,
--
Hector Palacios
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
Hi Marek,
On 07/22/2013 09:42 AM, Marek Vasut wrote:
Dear Hector Palacios,
Hi Marek,
On 07/19/2013 06:14 PM, Marek Vasut wrote:
Dear Hector Palacios,
Dear Marek,
On 07/19/2013 04:30 PM, Marek Vasut wrote:
@@ -228,39 +230,12 @@ struct mxs_lradc {
#define LRADC_RESOLUTION
Hi Alexandre,
On 07/19/2013 07:06 PM, Alexandre Belloni wrote:
Hi Hector,
On 19/07/2013 11:13, Hector Palacios wrote:
Some LRADC channels have fixed pre-dividers and all have an optional
divider by two which allows a maximum input voltage of VDDIO - 50mV.
This patch
- adds the scaling info
Hi Marek,
On 07/19/2013 06:14 PM, Marek Vasut wrote:
Dear Hector Palacios,
Dear Marek,
On 07/19/2013 04:30 PM, Marek Vasut wrote:
@@ -228,39 +230,12 @@ struct mxs_lradc {
#define LRADC_RESOLUTION 12
#define LRADC_SINGLE_SAMPLE_MASK ((1
Hi Marek,
On 07/19/2013 06:14 PM, Marek Vasut wrote:
Dear Hector Palacios,
Dear Marek,
On 07/19/2013 04:30 PM, Marek Vasut wrote:
@@ -228,39 +230,12 @@ struct mxs_lradc {
#define LRADC_RESOLUTION 12
#define LRADC_SINGLE_SAMPLE_MASK ((1
Hi Alexandre,
On 07/19/2013 07:06 PM, Alexandre Belloni wrote:
Hi Hector,
On 19/07/2013 11:13, Hector Palacios wrote:
Some LRADC channels have fixed pre-dividers and all have an optional
divider by two which allows a maximum input voltage of VDDIO - 50mV.
This patch
- adds the scaling info
Hi Marek,
On 07/22/2013 09:42 AM, Marek Vasut wrote:
Dear Hector Palacios,
Hi Marek,
On 07/19/2013 06:14 PM, Marek Vasut wrote:
Dear Hector Palacios,
Dear Marek,
On 07/19/2013 04:30 PM, Marek Vasut wrote:
@@ -228,39 +230,12 @@ struct mxs_lradc {
#define LRADC_RESOLUTION
the struct approach, it removes one dimension to the array and I find
it cleaner.
Best regards,
--
Hector Palacios
--
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
.
Besides, the driver was using an 18 bit mask (LRADC_CH_VALUE_MASK) to
report touch coordinates to userland. A 12 bit mask should be used instead
or else the touch libraries will expect a coordinates range between 0
and 0x3 (18 bits), instead of between 0 and 0xfff (12 bits).
Signed-off-by: Hector
Added write_raw function to manipulate the optional divider_by_two
through the scaling attribute out of the available scales.
Signed-off-by: Hector Palacios hector.palac...@digi.com
---
drivers/staging/iio/adc/mxs-lradc.c | 56 -
1 file changed, 55 insertions
)
- allows to read the scaling attribute (computed from the Vref)
Signed-off-by: Hector Palacios hector.palac...@digi.com.
Acked-by: Marek Vasut ma...@denx.de
---
drivers/staging/iio/adc/mxs-lradc.c | 77 +
1 file changed, 53 insertions(+), 24 deletions(-)
diff --git
Some LRADC channels have fixed pre-dividers so they can measure
different voltages at full scale. The reference voltage allows to
expose a scaling attribute through the IIO sysfs so that a user can
compute the real voltage out of a measured sample value.
Signed-off-by: Hector Palacios
-by: Hector Palacios hector.palac...@digi.com
---
drivers/staging/iio/adc/mxs-lradc.c | 112 +++-
1 file changed, 111 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/iio/adc/mxs-lradc.c
b/drivers/staging/iio/adc/mxs-lradc.c
index 5037577..5d332b1 100644
platform.
Could someone please test on an i.MX23?
Hector Palacios (5):
iio: mxs-lradc: change the realbits to 12
ARM: dts: add reference voltage property for MXS LRADC
iio: mxs-lradc: add scale attribute to channels
iio: mxs-lradc: add scale_available file to channels
iio: mxs-lradc: add
mask', right? Yeah, I think I had resolved that one
before submitting, but looks like I didn't.
The other check is not resolved afaik. We agreed to remove it, but on a
different patch.
Otherwise:
Acked-by: Marek Vasut
Marek Vasut
Best regards,
--
Hector Palacios
--
To unsubscribe from thi
was rejected and I was told
to use the scale_available descriptor instead, which is the common interface the rest
of drivers use.
Best regards,
--
Hector Palacios
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.ke
Dear Marek,
On 07/19/2013 04:39 PM, Marek Vasut wrote:
Dear Hector Palacios,
Added write_raw function to manipulate the optional divider_by_two
through the scaling attribute out of the available scales.
Signed-off-by: Hector Palacios
---
drivers/staging/iio/adc/mxs-lradc.c | 55
Added write_raw function to manipulate the optional divider_by_two
through the scaling attribute out of the available scales.
Signed-off-by: Hector Palacios
---
drivers/staging/iio/adc/mxs-lradc.c | 55 -
1 file changed, 54 insertions(+), 1 deletion(-)
diff
. The
second adds the channels reference voltages to the DT.
The following add the scale read operation, scale_available read
operation, and scale write operation.
This was tested on a custom i.MX28 platform.
Could someone please test on an i.MX23?
Hector Palacios (5):
iio: mxs-lradc: change
Adds in_voltageX_scale_available file for every channel to read
the different available scales.
There are two scales per channel:
[0] = divider_by_two disabled (default)
[1] = divider_by_two enabled
Signed-off-by: Hector Palacios
---
drivers/staging/iio/adc/mxs-lradc.c | 103
)
- allows to read the scaling attribute (computed from the Vref)
Signed-off-by: Hector Palacios .
---
drivers/staging/iio/adc/mxs-lradc.c | 81 -
1 file changed, 52 insertions(+), 29 deletions(-)
diff --git a/drivers/staging/iio/adc/mxs-lradc.c
b/drivers/staging/iio
.
Besides, the driver was using an 18 bit mask (LRADC_CH_VALUE_MASK) to
report touch coordinates to userland. A 12 bit mask should be used instead
or else the touch libraries will expect a coordinates range between 0
and 0x3 (18 bits), instead of between 0 and 0xfff (12 bits).
Signed-off-by: Hector
Some LRADC channels have fixed pre-dividers so they can measure
different voltages at full scale. The reference voltage allows to
expose a scaling attribute through the IIO sysfs so that a user can
compute the real voltage out of a measured sample value.
Signed-off-by: Hector Palacios
Some LRADC channels have fixed pre-dividers so they can measure
different voltages at full scale. The reference voltage allows to
expose a scaling attribute through the IIO sysfs so that a user can
compute the real voltage out of a measured sample value.
Signed-off-by: Hector Palacios
Adds in_voltageX_scale_available file for every channel to read
the different available scales.
There are two scales per channel:
[0] = divider_by_two disabled (default)
[1] = divider_by_two enabled
Signed-off-by: Hector Palacios hector.palac...@digi.com
---
drivers/staging/iio/adc/mxs-lradc.c
)
- allows to read the scaling attribute (computed from the Vref)
Signed-off-by: Hector Palacios hector.palac...@digi.com.
---
drivers/staging/iio/adc/mxs-lradc.c | 81 -
1 file changed, 52 insertions(+), 29 deletions(-)
diff --git a/drivers/staging/iio/adc/mxs-lradc.c
.
Besides, the driver was using an 18 bit mask (LRADC_CH_VALUE_MASK) to
report touch coordinates to userland. A 12 bit mask should be used instead
or else the touch libraries will expect a coordinates range between 0
and 0x3 (18 bits), instead of between 0 and 0xfff (12 bits).
Signed-off-by: Hector
. The
second adds the channels reference voltages to the DT.
The following add the scale read operation, scale_available read
operation, and scale write operation.
This was tested on a custom i.MX28 platform.
Could someone please test on an i.MX23?
Hector Palacios (5):
iio: mxs-lradc: change
Added write_raw function to manipulate the optional divider_by_two
through the scaling attribute out of the available scales.
Signed-off-by: Hector Palacios hector.palac...@digi.com
---
drivers/staging/iio/adc/mxs-lradc.c | 55 -
1 file changed, 54 insertions
Dear Marek,
On 07/19/2013 04:39 PM, Marek Vasut wrote:
Dear Hector Palacios,
Added write_raw function to manipulate the optional divider_by_two
through the scaling attribute out of the available scales.
Signed-off-by: Hector Palacios hector.palac...@digi.com
---
drivers/staging/iio/adc/mxs
was told
to use the scale_available descriptor instead, which is the common interface the rest
of drivers use.
Best regards,
--
Hector Palacios
--
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
, I think I had resolved that one
before submitting, but looks like I didn't.
The other check is not resolved afaik. We agreed to remove it, but on a
different patch.
Otherwise:
Acked-by: Marek Vasut ma...@denx.de
Marek Vasut
Best regards,
--
Hector Palacios
--
To unsubscribe from
Dear Maxime,
On 07/11/2013 10:24 AM, maxime.rip...@free-electrons.com wrote:
Hi Hector,
On Thu, Jul 11, 2013 at 09:30:34AM +0200, Hector Palacios wrote:
Greetings,
Linux 2.6.35 had a driver for sysfs access to the MXS persistent
bits (drivers/misc/mxs-persistent.c).
Freescale's 2.6.35 I
On 07/11/2013 09:30 AM, Hector Palacios wrote:
Greetings,
Linux 2.6.35 had a driver for sysfs access to the MXS persistent bits
(drivers/misc/mxs-persistent.c).
I haven't seen this is supported upstream. Is anybody working on that?
Where would such a driver fit?
Adding Steffen Trumtrar, as I
Greetings,
Linux 2.6.35 had a driver for sysfs access to the MXS persistent bits
(drivers/misc/mxs-persistent.c).
I haven't seen this is supported upstream. Is anybody working on that?
Where would such a driver fit?
Best regards,
--
Hector Palacios
--
To unsubscribe from this list: send
Greetings,
Linux 2.6.35 had a driver for sysfs access to the MXS persistent bits
(drivers/misc/mxs-persistent.c).
I haven't seen this is supported upstream. Is anybody working on that?
Where would such a driver fit?
Best regards,
--
Hector Palacios
--
To unsubscribe from this list: send
On 07/11/2013 09:30 AM, Hector Palacios wrote:
Greetings,
Linux 2.6.35 had a driver for sysfs access to the MXS persistent bits
(drivers/misc/mxs-persistent.c).
I haven't seen this is supported upstream. Is anybody working on that?
Where would such a driver fit?
Adding Steffen Trumtrar, as I
Dear Maxime,
On 07/11/2013 10:24 AM, maxime.rip...@free-electrons.com wrote:
Hi Hector,
On Thu, Jul 11, 2013 at 09:30:34AM +0200, Hector Palacios wrote:
Greetings,
Linux 2.6.35 had a driver for sysfs access to the MXS persistent
bits (drivers/misc/mxs-persistent.c).
Freescale's 2.6.35 I
On 06/18/2013 10:32 AM, maxime.rip...@free-electrons.com wrote:
Hi Hector,
On Fri, Jun 07, 2013 at 11:02:28AM +0200, maxime.rip...@free-electrons.com
wrote:
On Fri, Jun 07, 2013 at 10:10:39AM +0200, Hector Palacios wrote:
For a combination of 18bit LCD data bus width and a color
mode
://lkml.org/lkml/2013/5/23/220
Signed-off-by: Hector Palacios
Acked-by: Juergen Beisert
Acked-by: Maxime Ripard
---
drivers/video/mxsfb.c | 26 --
1 file changed, 26 deletions(-)
diff --git a/drivers/video/mxsfb.c b/drivers/video/mxsfb.c
index 21223d4..d2c5105 100644
://lkml.org/lkml/2013/5/23/220
Signed-off-by: Hector Palacios hector.palac...@digi.com
Acked-by: Juergen Beisert j...@pengutronix.de
Acked-by: Maxime Ripard maxime.rip...@free-electrons.com
---
drivers/video/mxsfb.c | 26 --
1 file changed, 26 deletions(-)
diff --git a/drivers
On 06/18/2013 10:32 AM, maxime.rip...@free-electrons.com wrote:
Hi Hector,
On Fri, Jun 07, 2013 at 11:02:28AM +0200, maxime.rip...@free-electrons.com
wrote:
On Fri, Jun 07, 2013 at 10:10:39AM +0200, Hector Palacios wrote:
For a combination of 18bit LCD data bus width and a color
mode
://lkml.org/lkml/2013/5/23/220
Signed-off-by: Hector Palacios
Acked-by: Juergen Beisert
---
drivers/video/mxsfb.c | 26 --
1 file changed, 26 deletions(-)
diff --git a/drivers/video/mxsfb.c b/drivers/video/mxsfb.c
index 21223d4..d2c5105 100644
--- a/drivers/video/mxsfb.c
,
--
Hector Palacios
--
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://www.tux.org/lkml/
,
--
Hector Palacios
--
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://www.tux.org/lkml/
://lkml.org/lkml/2013/5/23/220
Signed-off-by: Hector Palacios hector.palac...@digi.com
Acked-by: Juergen Beisert j...@pengutronix.de
---
drivers/video/mxsfb.c | 26 --
1 file changed, 26 deletions(-)
diff --git a/drivers/video/mxsfb.c b/drivers/video/mxsfb.c
index 21223d4
Hello,
Am I right in assuming that the MXS USB on-the-go port does not currently support the
device (gadget) functionality?
Anybody out there working on that?
Regards,
--
Héctor Palacios
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hello,
Am I right in assuming that the MXS USB on-the-go port does not currently support the
device (gadget) functionality?
Anybody out there working on that?
Regards,
--
Héctor Palacios
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
Hi Juergen,
On 05/24/2013 12:28 PM, Juergen Beisert wrote:
Hector Palacios wrote:
Hi Juergen,
On 05/23/2013 03:31 PM, Juergen Beisert wrote:
Hi Maxime,
maxime.rip...@free-electrons.com wrote:
On Thu, May 23, 2013 at 01:55:28PM +0200, Hector Palacios wrote:
I'm using an i.MX28 based board
Hi Juergen,
On 05/24/2013 12:28 PM, Juergen Beisert wrote:
Hector Palacios wrote:
Hi Juergen,
On 05/23/2013 03:31 PM, Juergen Beisert wrote:
Hi Maxime,
maxime.rip...@free-electrons.com wrote:
On Thu, May 23, 2013 at 01:55:28PM +0200, Hector Palacios wrote:
I'm using an i.MX28 based board
Hi Juergen,
On 05/23/2013 03:31 PM, Juergen Beisert wrote:
Hi Maxime,
maxime.rip...@free-electrons.com wrote:
On Thu, May 23, 2013 at 01:55:28PM +0200, Hector Palacios wrote:
I'm using an i.MX28 based board with lcd connected with 18bits data bus.
My platform uses 32 bits per pixel
Hello,
I'm using an i.MX28 based board with lcd connected with 18bits data bus.
My platform uses 32 bits per pixel:
mxsfb_pdata.default_bpp = 32;
mxsfb_pdata.ld_intf_width = STMLCDIF_18BIT;
With these settings the mxsfb.c driver sets flag DATA_FORMAT_24_BIT at HW_LCDIF_CTRL
Hello,
I'm using an i.MX28 based board with lcd connected with 18bits data bus.
My platform uses 32 bits per pixel:
mxsfb_pdata.default_bpp = 32;
mxsfb_pdata.ld_intf_width = STMLCDIF_18BIT;
With these settings the mxsfb.c driver sets flag DATA_FORMAT_24_BIT at HW_LCDIF_CTRL
Hi Juergen,
On 05/23/2013 03:31 PM, Juergen Beisert wrote:
Hi Maxime,
maxime.rip...@free-electrons.com wrote:
On Thu, May 23, 2013 at 01:55:28PM +0200, Hector Palacios wrote:
I'm using an i.MX28 based board with lcd connected with 18bits data bus.
My platform uses 32 bits per pixel
Dear Fabio,
On 05/17/2013 04:07 PM, Fabio Estevam wrote:
On 05/17/2013 10:57 AM, Hector Palacios wrote:
On the MX28EVK board with the Seiko 4.3" LCD, I do not see the penguin
or any image in v3.8 or v3.9 though the framebuffer device is present
and correctly loaded and backlight on.
Thi
Dear Fabio,
On 05/17/2013 04:07 PM, Fabio Estevam wrote:
On 05/17/2013 10:57 AM, Hector Palacios wrote:
On the MX28EVK board with the Seiko 4.3 LCD, I do not see the penguin
or any image in v3.8 or v3.9 though the framebuffer device is present
and correctly loaded and backlight on.
This LCD
Hello,
I was testing the framebuffer on an i.MX28 based platform and found out that the lcdif
clock is actually bypassed to use the ref_xtal of 24MHz, which makes the
clk_set_rate() call in the driver useless (as well as the pixclock settings in
fb_videomode variables in mach-mxs.c):
static
Hello,
I was testing the framebuffer on an i.MX28 based platform and found out that the lcdif
clock is actually bypassed to use the ref_xtal of 24MHz, which makes the
clk_set_rate() call in the driver useless (as well as the pixclock settings in
fb_videomode variables in mach-mxs.c):
static
Hello,
I had the feeling that the MXS SPI driver was rather useless due to the SPI being only
half-duplex on i.MX28, but it looks like people's using it so I was wondering what
kind of SPI devices can be driven with it, or if there is any trick that allows
bi-directional communication.
Hello,
I had the feeling that the MXS SPI driver was rather useless due to the SPI being only
half-duplex on i.MX28, but it looks like people's using it so I was wondering what
kind of SPI devices can be driven with it, or if there is any trick that allows
bi-directional communication.
On 04/09/2013 12:51 PM, Marek Vasut wrote:
Hi Hector,
Dear Marek Vasut,
On 04/09/2013 10:15 AM, Marek Vasut wrote:
Dear Hector Palacios,
Dear Marek Vasut,
On 04/08/2013 06:28 PM, Marek Vasut wrote:
Dear Shawn Guo,
On Mon, Apr 08, 2013 at 03:58:05PM +0200, Hector Palacios wrote:
On 04
On Tue 09 Apr 2013 06:34:10 PM CEST, Marc Kleine-Budde wrote:
On 04/09/2013 05:21 PM, Hector Palacios wrote:
On 04/09/2013 05:14 PM, Hector Palacios wrote:
@@ -95,7 +97,8 @@ static int mxs_mmc_get_cd(struct mmc_host *mmc)
struct mxs_mmc_host *host = mmc_priv(mmc);
struct
On Tue 09 Apr 2013 06:34:10 PM CEST, Marc Kleine-Budde wrote:
On 04/09/2013 05:21 PM, Hector Palacios wrote:
On 04/09/2013 05:14 PM, Hector Palacios wrote:
@@ -95,7 +97,8 @@ static int mxs_mmc_get_cd(struct mmc_host *mmc)
struct mxs_mmc_host *host = mmc_priv(mmc);
struct
On 04/09/2013 12:51 PM, Marek Vasut wrote:
Hi Hector,
Dear Marek Vasut,
On 04/09/2013 10:15 AM, Marek Vasut wrote:
Dear Hector Palacios,
Dear Marek Vasut,
On 04/08/2013 06:28 PM, Marek Vasut wrote:
Dear Shawn Guo,
On Mon, Apr 08, 2013 at 03:58:05PM +0200, Hector Palacios wrote:
On 04
On 04/09/2013 05:14 PM, Hector Palacios wrote:
@@ -95,7 +97,8 @@ static int mxs_mmc_get_cd(struct mmc_host *mmc)
struct mxs_mmc_host *host = mmc_priv(mmc);
struct mxs_ssp *ssp = >ssp;
- return !(readl(ssp->base + HW_SSP_STATUS(ssp)) &
+ return host->
Dear Marc Kleine-Budde,
On 04/05/2013 02:47 PM, Marc Kleine-Budde wrote:
Some boards have non removable cards like eMMC. Handle such case.
Acked-by: Shawn Guo
Signed-off-by: Marc Kleine-Budde
---
changes since v1:
- fix removeable typo
drivers/mmc/host/mxs-mmc.c | 10 +++---
1 file
Dear Marek Vasut,
On 04/09/2013 10:15 AM, Marek Vasut wrote:
Dear Hector Palacios,
Dear Marek Vasut,
On 04/08/2013 06:28 PM, Marek Vasut wrote:
Dear Shawn Guo,
On Mon, Apr 08, 2013 at 03:58:05PM +0200, Hector Palacios wrote:
On 04/08/2013 02:48 PM, Shawn Guo wrote:
On Mon, Apr 08, 2013
Dear Marek Vasut,
On 04/08/2013 06:28 PM, Marek Vasut wrote:
Dear Shawn Guo,
On Mon, Apr 08, 2013 at 03:58:05PM +0200, Hector Palacios wrote:
On 04/08/2013 02:48 PM, Shawn Guo wrote:
On Mon, Apr 08, 2013 at 12:12:20PM +0200, Hector Palacios wrote:
MicroSD card sockets don't usually have
Dear Marek Vasut,
On 04/08/2013 06:28 PM, Marek Vasut wrote:
Dear Shawn Guo,
On Mon, Apr 08, 2013 at 03:58:05PM +0200, Hector Palacios wrote:
On 04/08/2013 02:48 PM, Shawn Guo wrote:
On Mon, Apr 08, 2013 at 12:12:20PM +0200, Hector Palacios wrote:
MicroSD card sockets don't usually have
Dear Marek Vasut,
On 04/09/2013 10:15 AM, Marek Vasut wrote:
Dear Hector Palacios,
Dear Marek Vasut,
On 04/08/2013 06:28 PM, Marek Vasut wrote:
Dear Shawn Guo,
On Mon, Apr 08, 2013 at 03:58:05PM +0200, Hector Palacios wrote:
On 04/08/2013 02:48 PM, Shawn Guo wrote:
On Mon, Apr 08, 2013
Dear Marc Kleine-Budde,
On 04/05/2013 02:47 PM, Marc Kleine-Budde wrote:
Some boards have non removable cards like eMMC. Handle such case.
Acked-by: Shawn Guo shawn@linaro.org
Signed-off-by: Marc Kleine-Budde m...@pengutronix.de
---
changes since v1:
- fix removeable typo
On 04/09/2013 05:14 PM, Hector Palacios wrote:
@@ -95,7 +97,8 @@ static int mxs_mmc_get_cd(struct mmc_host *mmc)
struct mxs_mmc_host *host = mmc_priv(mmc);
struct mxs_ssp *ssp = host-ssp;
- return !(readl(ssp-base + HW_SSP_STATUS(ssp))
+ return host-non_removable
ot;/dev/watchdog", O_RDWR);
flags = WDIOS_DISABLECARD;
ioctl(wd_fd, WDIOC_SETOPTIONS, );
close(wd_fd);
Signed-off-by: Hector Palacios
---
Changes from v1:
- Make it less intrusive with 'if/else if' clauses.
- Change the logic of 'err' variable for better readabilit
On 04/08/2013 03:41 PM, Guenter Roeck wrote:
On Mon, Apr 08, 2013 at 11:10:58AM +0200, Hector Palacios wrote:
A watchdog device may be stopped from userspace using WDIOC_SETOPTIONS
ioctl and flag WDIOS_DISABLECARD. If the device is closed after this
operation, watchdog_release() is called
On 04/08/2013 02:48 PM, Shawn Guo wrote:
On Mon, Apr 08, 2013 at 12:12:20PM +0200, Hector Palacios wrote:
MicroSD card sockets don't usually have card detect line. This pin
is actually not needed for the MMC to work and it is more of a
platform design decission to have it.
The card detect pin
and let
platforms to include it or not depending on whether the card detect
line is routed to the SD socket.
Signed-off-by: Hector Palacios
---
Hello,
All imx28 based platforms except 'bluegiga,apx4devkit' and
'schulercontrol,imx28-sps1', use 'mmc0_cd_cfg' in their mmc configuration
so please check
ot;/dev/watchdog", O_RDWR);
flags = WDIOS_DISABLECARD;
ioctl(wd_fd, WDIOC_SETOPTIONS, );
close(wd_fd);
Signed-off-by: Hector Palacios
---
Changes from v1:
- Make it less intrusive with 'if/else if' clauses
- Change the logic of 'err' variable for better readabil
On 04/08/2013 10:16 AM, Guenter Roeck wrote:
On Mon, Apr 08, 2013 at 09:48:57AM +0200, Hector Palacios wrote:
On 04/05/2013 08:34 PM, Guenter Roeck wrote:
On Fri, Apr 05, 2013 at 06:09:44PM +0200, Hector Palacios wrote:
A watchdog device may be stopped from userspace using WDIOC_SETOPTIONS
On 04/05/2013 08:34 PM, Guenter Roeck wrote:
On Fri, Apr 05, 2013 at 06:09:44PM +0200, Hector Palacios wrote:
A watchdog device may be stopped from userspace using WDIOC_SETOPTIONS
ioctl and flag WDIOS_DISABLECARD. If the device is closed after this
operation, watchdog_release() is called
On 04/05/2013 08:34 PM, Guenter Roeck wrote:
On Fri, Apr 05, 2013 at 06:09:44PM +0200, Hector Palacios wrote:
A watchdog device may be stopped from userspace using WDIOC_SETOPTIONS
ioctl and flag WDIOS_DISABLECARD. If the device is closed after this
operation, watchdog_release() is called
1 - 100 of 118 matches
Mail list logo
