Hi Heiko,
On 13-12-2013 08:42, Heiko Stübner wrote:
But Jose, you should really really look into moving to devicetree with your
platform, if you're not already doing so. Pinctrl support is already present,
and I'm hopefull the move to the common clock framework I posted a few days
ago might
The Samsung serial driver currently does not support setting the
RTS pin with an ioctl(TIOCMSET) call. This patch adds this support.
Changes in v2:
- Preserve the RTS pin's manual setting in set_termios() also when
enabling CRTSCTS.
Signed-off-by: José Miguel Gonçalves jose.goncal
Hi Tomasz,
On 17-09-2013 11:18, Tomasz Figa wrote:
Hi José,
Please see my comments below.
On Wednesday 11 of September 2013 11:08:27 José Miguel Gonçalves wrote:
The Samsung serial driver currently does not support setting the
RTS pin with an ioctl(TIOCMSET) call. This patch adds
On 17-09-2013 16:21, Tomasz Figa wrote:
I had the following scenario in mind:
1) enable CRTSCTS,
2) set RTS status using the IOCTL,
3) disable CRTSCTS,
4) do something,
5) enable CRTSCTS again.
I would expect that the value set in point 2 would be still valid after
point 5, while it will be
Some GPIO line limits are incorrectly set which, for instance,
does not allow nRTS1 (GPH11) configuration on a S3C2416 chip.
Signed-off-by: José Miguel Gonçalves jose.goncal...@inov.pt
---
arch/arm/mach-s3c24xx/include/mach/gpio.h | 10 +-
drivers/gpio/gpio-samsung.c
Hi,
While migrating from kernel 3.8 to kernel 3.9 I've detected a problem on my
S3C2416 based board. I'm using UART 3 as console and with kernel 3.9 I'm unable to
have a getty working on that port and see a lot of these on dmesg:
samsung-uart s3c2440-uart.3: cannot get irq 94
Also WDT is
Hi Heiko,
On 27-06-2013 15:26, Heiko Stübner wrote:
Hi Jose,
Am Donnerstag, 27. Juni 2013, 13:59:07 schrieb José Miguel Gonçalves:
Hi,
While migrating from kernel 3.8 to kernel 3.9 I've detected a problem on my
S3C2416 based board. I'm using UART 3 as console and with kernel 3.9 I'm
unable
On 15-10-2012 15:58, Sylwester Nawrocki wrote:
Hi Heiko,
On 10/02/2012 02:43 PM, Heiko Stübner wrote:
Commit a5238e360b71 (spi: s3c64xx: move controller information into driver
data) introduced separate device names for the different subtypes of the
spi controller but forgot to set these in
Hi,
I'm trying to use the HSSPI controller on a S3C2416 based board but I'm having
some problems.
I've added s3c64xx_device_spi0 to my array of platform devices and added a call
to s3c64xx_spi0_set_platdata(NULL, 0, 1) before platform_add_devices(). When the
kernel starts I see the
On 10/01/2012 08:18 PM, Heiko Stübner wrote:
Hi José,
Am Montag, 1. Oktober 2012, 19:32:15 schrieb José Miguel Gonçalves:
I'm trying to use the HSSPI controller on a S3C2416 based board but I'm
having some problems.
I've added s3c64xx_device_spi0 to my array of platform devices and added
On 10-05-2012 10:25, Kukjin Kim wrote:
José Miguel Gonçalves wrote:
While upgrading the kernel on a S3C2412 based board I've noted that it was
impossible to boot the board with a 2.6.32 or upper kernel.
I've tracked down the problem to the EBI virtual memory mapping that is in
conflict
-off-by: José Miguel Gonçalves jose.goncal...@inov.pt
---
arch/arm/plat-samsung/include/plat/map-s3c.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/plat-samsung/include/plat/map-s3c.h
b/arch/arm/plat-samsung/include/plat/map-s3c.h
index 7d04875..c0c70a8 100644
12 matches
Mail list logo
