On 01/28/2015 03:50 AM, Tomeu Vizoso wrote:
Patches are on its way to add a config file to alsaucm for the Nyan
boards. Use the same card ID that alsaucm will expect.
diff --git a/arch/arm/boot/dts/tegra124-nyan-big.dts
b/arch/arm/boot/dts/tegra124-nyan-big.dts
sound {
-
On Sat, Jan 31, 2015 at 05:24:42PM +0530, varsharamt wrote:
The task was to fix a warning which was shown while compiling a driver
called NVEC. I wrote a brief description about how to enable support for
a nVidya complaint embedded controller.
Please note that NVIDIA is spelled/capitalized
On 01/27/2015 04:13 AM, Tomeu Vizoso wrote:
On 15 January 2015 at 18:26, Stephen Warren wrote:
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
To silence a warning on Nyan boards.
Signed-off-by: Tomeu Vizoso
---
arch/arm/boot/dts/tegra124-nyan-big.dts | 1 +
1 file changed, 1 insertion
On 01/27/2015 04:13 AM, Tomeu Vizoso wrote:
On 15 January 2015 at 18:26, Stephen Warren swar...@wwwdotorg.org wrote:
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
To silence a warning on Nyan boards.
Signed-off-by: Tomeu Vizoso tomeu.viz...@collabora.com
---
arch/arm/boot/dts/tegra124-nyan
On 01/20/2015 06:59 AM, Tomeu Vizoso wrote:
On 15 January 2015 at 18:25, Stephen Warren wrote:
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
Google has submitted a board config for the pinmux programming of the
Nyan Big board. Use the whole of it as it's generated to make it easier
to update
On 01/20/2015 06:59 AM, Tomeu Vizoso wrote:
On 15 January 2015 at 18:25, Stephen Warren swar...@wwwdotorg.org wrote:
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
Google has submitted a board config for the pinmux programming of the
Nyan Big board. Use the whole of it as it's generated to make
On 01/19/2015 10:41 AM, Dmitry Osipenko wrote:
19.01.2015 20:26, Stephen Warren пишет:
Hopefully this works out. I suppose it's unlikely anyone will be
running code on
the AVP upstrem, so any potential conflict with AVP's usage of IRAM
isn't likely
to occur.
I don't see how it can conflict
On 01/19/2015 07:12 AM, Thierry Reding wrote:
On Thu, Jan 15, 2015 at 01:58:57PM +0300, Dmitry Osipenko wrote:
Commit 7232398abc6a ("ARM: tegra: Convert PMC to a driver") changed
tegra_resume()
location storing from late to early and, as a result, broke suspend on Tegra20.
PMC scratch register
Acked-by: Stephen Warren
This seems sane to me. One thing I should have asked: What compatible
values does the RPi Foundation's downstream for all these cases?
Aligning with that would be nice if possible.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
On 01/16/2015 02:01 AM, Tomeu Vizoso wrote:
On 16 January 2015 at 09:50, Tomeu Vizoso wrote:
On 15 January 2015 at 18:22, Stephen Warren wrote:
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
Patches are on its way to add a config file to alsaucm for the Nyan
boards. Use the same card ID
Acked-by: Stephen Warren swar...@wwwdotorg.org
This seems sane to me. One thing I should have asked: What compatible
values does the RPi Foundation's downstream for all these cases?
Aligning with that would be nice if possible.
--
To unsubscribe from this list: send the line unsubscribe linux
On 01/19/2015 07:12 AM, Thierry Reding wrote:
On Thu, Jan 15, 2015 at 01:58:57PM +0300, Dmitry Osipenko wrote:
Commit 7232398abc6a (ARM: tegra: Convert PMC to a driver) changed
tegra_resume()
location storing from late to early and, as a result, broke suspend on Tegra20.
PMC scratch register
On 01/16/2015 02:01 AM, Tomeu Vizoso wrote:
On 16 January 2015 at 09:50, Tomeu Vizoso tomeu.viz...@collabora.com wrote:
On 15 January 2015 at 18:22, Stephen Warren swar...@wwwdotorg.org wrote:
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
Patches are on its way to add a config file to alsaucm
On 01/19/2015 10:41 AM, Dmitry Osipenko wrote:
19.01.2015 20:26, Stephen Warren пишет:
Hopefully this works out. I suppose it's unlikely anyone will be
running code on
the AVP upstrem, so any potential conflict with AVP's usage of IRAM
isn't likely
to occur.
I don't see how it can conflict
On 01/16/2015 09:49 AM, Stefan Wahren wrote:
> This patch converts all bcm2835 dts files to use the pinctrl
> header file.
Aside from the one comment I made, the series,
Acked-by: Stephen Warren
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
On 01/16/2015 09:48 AM, Stefan Wahren wrote:
> This patch adds root compatible properties for the following boards:
> - Raspberry Pi Model B
> - Raspberry Pi Model B+
We may as well add all the models while at it. I think the following is
a complete list so far:
"model-b-i2c0": early model B
On 01/16/2015 09:48 AM, Stefan Wahren wrote:
This patch adds root compatible properties for the following boards:
- Raspberry Pi Model B
- Raspberry Pi Model B+
We may as well add all the models while at it. I think the following is
a complete list so far:
model-b-i2c0: early model B with
On 01/16/2015 09:49 AM, Stefan Wahren wrote:
This patch converts all bcm2835 dts files to use the pinctrl
header file.
Aside from the one comment I made, the series,
Acked-by: Stephen Warren swar...@wwwdotorg.org
--
To unsubscribe from this list: send the line unsubscribe linux-kernel
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
The Nyan boards have a Marvell 88w8897 wifi card connected through SDIO
that need the reset line to be hold active for several milliseconds.
diff --git a/arch/arm/boot/dts/tegra124-nyan.dtsi
b/arch/arm/boot/dts/tegra124-nyan.dtsi
+
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
Signed-off-by: Tomeu Vizoso
Ah, having read the explanation in the next patch, I think ...
diff --git a/Documentation/devicetree/bindings/mmc/mmc,pwrseq-simple.txt
b/Documentation/devicetree/bindings/mmc/mmc,pwrseq-simple.txt
+- delay : delay
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
Signed-off-by: Tomeu Vizoso
Some explanation of why such a delay might be useful would be ... useful!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
In preparation for adding the DT for the nyan-blaze board.
"git format-patch -C" might help here; hopefully it'd highlight that
arch/arm/boot/dts/tegra124-nyan.dtsi was a copy from
arch/arm/boot/dts/tegra124-nyan-big.dts, with just a few small
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
To silence a warning on Nyan boards.
Signed-off-by: Tomeu Vizoso
---
arch/arm/boot/dts/tegra124-nyan-big.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/tegra124-nyan-big.dts
b/arch/arm/boot/dts/tegra124-nyan-big.dts
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
Google has submitted a board config for the pinmux programming of the
Nyan Big board. Use the whole of it as it's generated to make it easier
to update as the configuration gets fixed in the future.
Submitted to where? I assume you mean
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
Patches are on its way to add a config file to alsaucm for the Nyan
boards. Use the same card ID that alsaucm will expect.
Signed-off-by: Tomeu Vizoso
---
arch/arm/boot/dts/tegra124-nyan-big.dts | 4 ++--
1 file changed, 2 insertions(+), 2
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
Signed-off-by: Tomeu Vizoso tomeu.viz...@collabora.com
Some explanation of why such a delay might be useful would be ... useful!
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
Signed-off-by: Tomeu Vizoso tomeu.viz...@collabora.com
Ah, having read the explanation in the next patch, I think ...
diff --git a/Documentation/devicetree/bindings/mmc/mmc,pwrseq-simple.txt
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
The Nyan boards have a Marvell 88w8897 wifi card connected through SDIO
that need the reset line to be hold active for several milliseconds.
diff --git a/arch/arm/boot/dts/tegra124-nyan.dtsi
b/arch/arm/boot/dts/tegra124-nyan.dtsi
+
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
To silence a warning on Nyan boards.
Signed-off-by: Tomeu Vizoso tomeu.viz...@collabora.com
---
arch/arm/boot/dts/tegra124-nyan-big.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/tegra124-nyan-big.dts
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
Google has submitted a board config for the pinmux programming of the
Nyan Big board. Use the whole of it as it's generated to make it easier
to update as the configuration gets fixed in the future.
Submitted to where? I assume you mean
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
Patches are on its way to add a config file to alsaucm for the Nyan
boards. Use the same card ID that alsaucm will expect.
Signed-off-by: Tomeu Vizoso tomeu.viz...@collabora.com
---
arch/arm/boot/dts/tegra124-nyan-big.dts | 4 ++--
1 file changed,
On 01/15/2015 09:12 AM, Tomeu Vizoso wrote:
In preparation for adding the DT for the nyan-blaze board.
git format-patch -C might help here; hopefully it'd highlight that
arch/arm/boot/dts/tegra124-nyan.dtsi was a copy from
arch/arm/boot/dts/tegra124-nyan-big.dts, with just a few small diffs?
On 01/14/2015 02:18 AM, Bart Tanghe wrote:
To probe the bcm2835-pwm driver properly, this dts bindings has to be added
to the bcm2835 dtsi file.
In expectation of a bcm2835 clock driver, I've added fixed-clock clock binding.
---
Changes in v3:
- node added by reg value
The pwm node still
On 01/14/2015 02:18 AM, Bart Tanghe wrote:
To probe the bcm2835-pwm driver properly, this dts bindings has to be added
to the bcm2835 dtsi file.
In expectation of a bcm2835 clock driver, I've added fixed-clock clock binding.
---
Changes in v3:
- node added by reg value
The pwm node still
On 01/13/2015 08:40 AM, Bart Tanghe wrote:
On 01/10/2015 05:38 PM, Stephen Warren wrote:
On 01/05/2015 08:33 AM, Bart Tanghe wrote:
To probe the bcm2835-pwm driver properly, this dts bindings has to be added
to the bcm2835 dtsi file.
In expectation of a bcm2835 clock driver, I've added fixed
On 01/13/2015 08:40 AM, Bart Tanghe wrote:
On 01/10/2015 05:38 PM, Stephen Warren wrote:
On 01/05/2015 08:33 AM, Bart Tanghe wrote:
To probe the bcm2835-pwm driver properly, this dts bindings has to be added
to the bcm2835 dtsi file.
In expectation of a bcm2835 clock driver, I've added fixed
On 01/05/2015 08:33 AM, Bart Tanghe wrote:
> To probe the bcm2835-pwm driver properly, this dts bindings has to be added
> to the bcm2835 dtsi file.
> In expectation of a bcm2835 clock driver, I've added fixed-clock clock
> binding.
> To change the status of the gpio pins into pwm output pins,
ls = <2>;
> + status = "disabled";
> + };
Can the nodes be kept sorted by reg value; I think this should be added
between the existing i2c@20205000 and sdhci@7e30 nodes.
Aside from that,
Acked-by: Stephen Warren
--
To unsubscribe from this list: s
On 01/05/2015 08:33 AM, Bart Tanghe wrote:
To probe the bcm2835-pwm driver properly, this dts bindings has to be added
to the bcm2835 dtsi file.
In expectation of a bcm2835 clock driver, I've added fixed-clock clock
binding.
To change the status of the gpio pins into pwm output pins, some
the nodes be kept sorted by reg value; I think this should be added
between the existing i2c@20205000 and sdhci@7e30 nodes.
Aside from that,
Acked-by: Stephen Warren swar...@wwwdotorg.org
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord
On 01/09/2015 01:52 PM, Paul Walmsley wrote:
Hi Thierry
On Fri, 9 Jan 2015, Thierry Reding wrote:
On Tue, Dec 16, 2014 at 12:38:29PM -0800, Paul Walmsley wrote:
This patch is based on several patches from others:
1. a patch from Peter De Schrijver:
by an unknown key
On Mon, Dec 22, 2014 at 11:00:16AM -0700, Stephen Warren wrote:
On 12/22/2014 10:27 AM, Dmitry Osipenko wrote:
22.12.2014 19:17, Stephen Warren пишет:
On 12/21/2014 03:52 PM, Dmitry Osipenko wrote:
Commit 7232398abc6a ("ARM: tegra: Convert PMC to a driver") changed
te
by an unknown key
On Mon, Dec 22, 2014 at 11:00:16AM -0700, Stephen Warren wrote:
On 12/22/2014 10:27 AM, Dmitry Osipenko wrote:
22.12.2014 19:17, Stephen Warren пишет:
On 12/21/2014 03:52 PM, Dmitry Osipenko wrote:
Commit 7232398abc6a (ARM: tegra: Convert PMC to a driver) changed
tegra_resume
On 01/09/2015 01:52 PM, Paul Walmsley wrote:
Hi Thierry
On Fri, 9 Jan 2015, Thierry Reding wrote:
On Tue, Dec 16, 2014 at 12:38:29PM -0800, Paul Walmsley wrote:
This patch is based on several patches from others:
1. a patch from Peter De Schrijver:
On 01/08/2015 08:40 PM, Kuninori Morimoto wrote:
>
> Hi Stephen, Olof, Arnd, Rob, Andrew
>
> I'm sending this "of: replace Asahi Kasei Corp vendor prefix" during
> half-year (since Jun 2014) , many times. But, no-one care it.
> I don't know who is the best maintainer.
> - Stephen : because it
On 01/08/2015 08:40 PM, Kuninori Morimoto wrote:
Hi Stephen, Olof, Arnd, Rob, Andrew
I'm sending this of: replace Asahi Kasei Corp vendor prefix during
half-year (since Jun 2014) , many times. But, no-one care it.
I don't know who is the best maintainer.
- Stephen : because it has Tegra
On 01/07/2015 01:06 AM, Tomeu Vizoso wrote:
On 6 January 2015 at 18:09, Stephen Warren wrote:
On 01/06/2015 03:37 AM, Tomeu Vizoso wrote:
Following 6dbaff2b, the kernel expects that the bootloader has correctly
programmed the Tegra pinmux.
DTs for the Jetson and the Venice2 had been updated
On 01/07/2015 01:06 AM, Tomeu Vizoso wrote:
On 6 January 2015 at 18:09, Stephen Warren swar...@wwwdotorg.org wrote:
On 01/06/2015 03:37 AM, Tomeu Vizoso wrote:
Following 6dbaff2b, the kernel expects that the bootloader has correctly
programmed the Tegra pinmux.
DTs for the Jetson
On 01/06/2015 03:37 AM, Tomeu Vizoso wrote:
In preparation for adding the DT for the nyan-blaze board.
"git format-patch -M" and/or "git format-patch -C" should make this
patch a lot easier to review, since it'll show the patch as a file
copy/rename rather than a full-file cut/paste.
--
To
On 01/06/2015 03:37 AM, Tomeu Vizoso wrote:
Following 6dbaff2b, the kernel expects that the bootloader has correctly
programmed the Tegra pinmux.
DTs for the Jetson and the Venice2 had been updated already but this one
was left behind.
So this setup is true for NVIDIA-controlled
On 01/06/2015 03:37 AM, Tomeu Vizoso wrote:
In preparation for adding the DT for the nyan-blaze board.
git format-patch -M and/or git format-patch -C should make this
patch a lot easier to review, since it'll show the patch as a file
copy/rename rather than a full-file cut/paste.
--
To
On 01/06/2015 03:37 AM, Tomeu Vizoso wrote:
Following 6dbaff2b, the kernel expects that the bootloader has correctly
programmed the Tegra pinmux.
DTs for the Jetson and the Venice2 had been updated already but this one
was left behind.
So this setup is true for NVIDIA-controlled
On 12/23/2014 11:36 AM, Felipe Balbi wrote:
On Thu, Dec 04, 2014 at 01:06:07PM +0100, Thierry Reding wrote:
From: Thierry Reding
Commit 1290a958d48e ("usb: phy: propagate __of_usb_find_phy()'s error on
failure") broke platforms that rely on deferred probing to order probing
of PHY and host
On 12/23/2014 11:36 AM, Felipe Balbi wrote:
On Thu, Dec 04, 2014 at 01:06:07PM +0100, Thierry Reding wrote:
From: Thierry Reding tred...@nvidia.com
Commit 1290a958d48e (usb: phy: propagate __of_usb_find_phy()'s error on
failure) broke platforms that rely on deferred probing to order probing
of
On 12/22/2014 10:27 AM, Dmitry Osipenko wrote:
22.12.2014 19:17, Stephen Warren пишет:
On 12/21/2014 03:52 PM, Dmitry Osipenko wrote:
Commit 7232398abc6a ("ARM: tegra: Convert PMC to a driver") changed
tegra_resume()
location storing from late to early and as result broke suspend
On 12/21/2014 03:52 PM, Dmitry Osipenko wrote:
Commit 7232398abc6a ("ARM: tegra: Convert PMC to a driver") changed
tegra_resume()
location storing from late to early and as result broke suspend on tegra20.
PMC scratch register 41 was used by tegra lp1 suspend core code for storing
physical
On 12/21/2014 03:52 PM, Dmitry Osipenko wrote:
Commit 7232398abc6a (ARM: tegra: Convert PMC to a driver) changed
tegra_resume()
location storing from late to early and as result broke suspend on tegra20.
PMC scratch register 41 was used by tegra lp1 suspend core code for storing
physical memory
On 12/22/2014 10:27 AM, Dmitry Osipenko wrote:
22.12.2014 19:17, Stephen Warren пишет:
On 12/21/2014 03:52 PM, Dmitry Osipenko wrote:
Commit 7232398abc6a (ARM: tegra: Convert PMC to a driver) changed
tegra_resume()
location storing from late to early and as result broke suspend on tegra20.
PMC
On 12/14/2014 09:48 PM, Tim Kryger wrote:
On Sat, Dec 13, 2014 at 11:22 PM, Bjorn Andersson wrote:
...
Or simply; what is vmmc (in the code) supposed to represent?
Hi Bjorn,
VMMC is the supply that delivers power out to the SD card itself (aka VDD).
It is not the internal power rail/power
On 12/14/2014 09:48 PM, Tim Kryger wrote:
On Sat, Dec 13, 2014 at 11:22 PM, Bjorn Andersson bj...@kryo.se wrote:
...
Or simply; what is vmmc (in the code) supposed to represent?
Hi Bjorn,
VMMC is the supply that delivers power out to the SD card itself (aka VDD).
It is not the internal
On 12/08/2014 09:51 AM, Lee Jones wrote:
On Mon, 08 Dec 2014, Stephen Warren wrote:
...
The primary purpose of the kernel.org linux-rpi.git repo is for
staging patches into arm-soc/linux-next. As such, just like any
other similar repo, users should expect at least the for-xxx (e.g.
for-next
On 12/08/2014 06:49 AM, Lee Jones wrote:
On Mon, 08 Dec 2014, Arnd Bergmann wrote:
On Monday 08 December 2014 13:00:09 Lee Jones wrote:
On Mon, 08 Dec 2014, Arnd Bergmann wrote:
On Monday 08 December 2014 12:06:19 Stephen Rothwell wrote:
Hi Stephen,
Today's linux-next merge of the bcm2835
On 12/08/2014 06:49 AM, Lee Jones wrote:
On Mon, 08 Dec 2014, Arnd Bergmann wrote:
On Monday 08 December 2014 13:00:09 Lee Jones wrote:
On Mon, 08 Dec 2014, Arnd Bergmann wrote:
On Monday 08 December 2014 12:06:19 Stephen Rothwell wrote:
Hi Stephen,
Today's linux-next merge of the bcm2835
On 12/08/2014 09:51 AM, Lee Jones wrote:
On Mon, 08 Dec 2014, Stephen Warren wrote:
...
The primary purpose of the kernel.org linux-rpi.git repo is for
staging patches into arm-soc/linux-next. As such, just like any
other similar repo, users should expect at least the for-xxx (e.g.
for-next
On 11/19/2014 08:29 AM, Lee Jones wrote:
The model B and B+ differ in the GPIO lines for ACT and PWR leds, and the
I2S interface.
Signed-off-by: Matthias Klein
---
Changes in v2:
- move the common parts between the B and B+ model into the new
bcm2835-rpi.dtsi file
- add the I2S signals to
On 11/19/2014 08:29 AM, Lee Jones wrote:
The model B and B+ differ in the GPIO lines for ACT and PWR leds, and the
I2S interface.
Signed-off-by: Matthias Klein matthias.kl...@linux.com
---
Changes in v2:
- move the common parts between the B and B+ model into the new
bcm2835-rpi.dtsi file
-
On 11/14/2014 03:03 PM, Anatol Pomozov wrote:
Hi
On Thu, Nov 13, 2014 at 2:46 PM, Thomas Gleixner wrote:
On Mon, 10 Nov 2014, Anatol Pomozov wrote:
On Mon, Nov 10, 2014 at 1:53 AM, Thierry Reding
wrote:
On Fri, Nov 07, 2014 at 11:34:15AM -0800, Anatol Pomozov wrote:
ARM timekeeping
On 11/14/2014 03:03 PM, Anatol Pomozov wrote:
Hi
On Thu, Nov 13, 2014 at 2:46 PM, Thomas Gleixner t...@linutronix.de wrote:
On Mon, 10 Nov 2014, Anatol Pomozov wrote:
On Mon, Nov 10, 2014 at 1:53 AM, Thierry Reding
thierry.red...@gmail.com wrote:
On Fri, Nov 07, 2014 at 11:34:15AM -0800,
On 11/12/2014 05:20 AM, Thierry Reding wrote:
On Tue, Nov 11, 2014 at 12:49:30PM -0800, Olof Johansson wrote:
There are general changes pending to make the /aliases/serial* entries
number the serial ports on the system. On tegra, so far the ports have been
just numbered dynamically as they are
On 11/12/2014 05:20 AM, Thierry Reding wrote:
On Tue, Nov 11, 2014 at 12:49:30PM -0800, Olof Johansson wrote:
There are general changes pending to make the /aliases/serial* entries
number the serial ports on the system. On tegra, so far the ports have been
just numbered dynamically as they are
On 11/11/2014 03:45 PM, Olof Johansson wrote:
[again in plain text mode. Sigh]
On Tue, Nov 11, 2014 at 1:14 PM, Stephen Warren wrote:
On 11/11/2014 01:49 PM, Olof Johansson wrote:
There are general changes pending to make the /aliases/serial* entries
number the serial ports on the system
On 11/11/2014 01:49 PM, Olof Johansson wrote:
There are general changes pending to make the /aliases/serial* entries
number the serial ports on the system. On tegra, so far the ports have been
just numbered dynamically as they are configured so that makes them change.
To avoid this, add
On 11/11/2014 01:49 PM, Olof Johansson wrote:
There are general changes pending to make the /aliases/serial* entries
number the serial ports on the system. On tegra, so far the ports have been
just numbered dynamically as they are configured so that makes them change.
To avoid this, add
On 11/11/2014 03:45 PM, Olof Johansson wrote:
[again in plain text mode. Sigh]
On Tue, Nov 11, 2014 at 1:14 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 11/11/2014 01:49 PM, Olof Johansson wrote:
There are general changes pending to make the /aliases/serial* entries
number the serial
On 11/07/2014 10:12 AM, Gordon Hollingworth wrote:
> Resend: HTML less...
> On 7 November 2014 17:07, Gordon Hollingworth wrote:
>> On 7 November 2014 16:20, Noralf Tronnes wrote:
...
>>> From the HAT specification:
>>> GPIO pins ID_SC and ID_SD (GPIO0 and GPIO1) are reserved for use solely
>>>
On 11/07/2014 09:20 AM, Noralf Tronnes wrote:
> Den 07.11.2014 05:22, skrev Stephen Warren:
>> On 11/06/2014 12:36 PM, Noralf Tronnes wrote:
>>> Den 06.11.2014 00:45, skrev Matthias Klein:
>>>> The model B and B+ differ in the GPIO lines for ACT and PWR leds,
&
On 11/07/2014 09:20 AM, Noralf Tronnes wrote:
Den 07.11.2014 05:22, skrev Stephen Warren:
On 11/06/2014 12:36 PM, Noralf Tronnes wrote:
Den 06.11.2014 00:45, skrev Matthias Klein:
The model B and B+ differ in the GPIO lines for ACT and PWR leds,
and the
I2S interface.
...
+i2c0
On 11/07/2014 10:12 AM, Gordon Hollingworth wrote:
Resend: HTML less...
On 7 November 2014 17:07, Gordon Hollingworth gor...@holliweb.co.uk wrote:
On 7 November 2014 16:20, Noralf Tronnes no...@tronnes.org wrote:
...
From the HAT specification:
GPIO pins ID_SC and ID_SD (GPIO0 and GPIO1) are
On 11/06/2014 12:36 PM, Noralf Tronnes wrote:
> Den 06.11.2014 00:45, skrev Matthias Klein:
>> The model B and B+ differ in the GPIO lines for ACT and PWR leds, and the
>> I2S interface.
>>
>> Signed-off-by: Matthias Klein
>> ---
>> Changes in v2:
>> - move the common parts between the B and B+
On 11/06/2014 05:21 PM, Anatol Pomozov wrote:
> register_persistent_clock() are in different headers in arm/arm64
>
> Tested: Compiled the driver on 64bit platform and make sure that
> it works
I assume "it works" refers to "it compiles" not "it executes successfully"?
I think it'd be better to
On 11/06/2014 05:25 PM, Anatol Pomozov wrote:
> +Stephen
>
> This patch is for tegra20_timer that uses register_persistent_clock().
> I did not find any way to share the same arch code for arm/arm64.
>
> Actually this register_persistent_clock() does not look arm specific
> at all. Would it be
On 11/06/2014 11:15 AM, Matthias Klein wrote:
Am 06.11.2014 um 06:29 schrieb Stephen Warren:
I guess we should have separate device trees for those, since there are
some differences in the GPIO and I2C channel usage. That'd leave us with:
bcm2835-rpi-b.dts (Pin3=GPIO0, Pin5=GPIO1, Pin13
On 11/06/2014 11:15 AM, Matthias Klein wrote:
Am 06.11.2014 um 06:29 schrieb Stephen Warren:
I guess we should have separate device trees for those, since there are
some differences in the GPIO and I2C channel usage. That'd leave us with:
bcm2835-rpi-b.dts (Pin3=GPIO0, Pin5=GPIO1, Pin13
On 11/06/2014 05:25 PM, Anatol Pomozov wrote:
+Stephen
This patch is for tegra20_timer that uses register_persistent_clock().
I did not find any way to share the same arch code for arm/arm64.
Actually this register_persistent_clock() does not look arm specific
at all. Would it be better
On 11/06/2014 05:21 PM, Anatol Pomozov wrote:
register_persistent_clock() are in different headers in arm/arm64
Tested: Compiled the driver on 64bit platform and make sure that
it works
I assume it works refers to it compiles not it executes successfully?
I think it'd be better to make the
On 11/06/2014 12:36 PM, Noralf Tronnes wrote:
Den 06.11.2014 00:45, skrev Matthias Klein:
The model B and B+ differ in the GPIO lines for ACT and PWR leds, and the
I2S interface.
Signed-off-by: Matthias Klein matthias.kl...@linux.com
---
Changes in v2:
- move the common parts between the B
On 11/05/2014 04:45 PM, Matthias Klein wrote:
> The model B and B+ differ in the GPIO lines for ACT and PWR leds, and the
> I2S interface.
BTW, according to:
http://raspberryalphaomega.org.uk/2013/02/06/automatic-raspberry-pi-board-revision-detection-model-a-b1-and-b2/
... there are actually 2
On 11/05/2014 04:45 PM, Matthias Klein wrote:
> The model B and B+ differ in the GPIO lines for ACT and PWR leds, and the
> I2S interface.
Tested-by: Stephen Warren
(On a model B rev 2, UART, SD card, and enumeration of built-in USB
devices works fine)
Lee, how do you want to handle p
On 11/05/2014 12:00 AM, Scott Branden wrote:
> On 14-11-04 08:59 PM, Stephen Warren wrote:
>> On 10/30/2014 12:36 AM, Scott Branden wrote:
>>> Add a verify option to driver to print out an error message if a
>>> potential back to back write could cause a clock domain
On 11/05/2014 12:02 AM, Scott Branden wrote:
> On 14-11-04 09:00 PM, Stephen Warren wrote:
>> On 10/30/2014 12:36 AM, Scott Branden wrote:
>>> SDHCI_QUIRK_MULTIBLOCK_READ_ACMD12 is missing and needed for this
>>> controller.
>>
>> This seems fine, alt
On 11/04/2014 11:55 PM, Scott Branden wrote:
> On 14-11-04 08:57 PM, Stephen Warren wrote:
>> On 10/30/2014 12:36 AM, Scott Branden wrote:
>>> The bcm2835 has clock domain issues when back to back writes to certain
>>> registers are written. The existing dri
On 11/04/2014 11:55 PM, Scott Branden wrote:
On 14-11-04 08:57 PM, Stephen Warren wrote:
On 10/30/2014 12:36 AM, Scott Branden wrote:
The bcm2835 has clock domain issues when back to back writes to certain
registers are written. The existing driver works around this issue with
udelay
On 11/05/2014 12:02 AM, Scott Branden wrote:
On 14-11-04 09:00 PM, Stephen Warren wrote:
On 10/30/2014 12:36 AM, Scott Branden wrote:
SDHCI_QUIRK_MULTIBLOCK_READ_ACMD12 is missing and needed for this
controller.
This seems fine, although any explanation of why this quirk is needed
would
On 11/05/2014 12:00 AM, Scott Branden wrote:
On 14-11-04 08:59 PM, Stephen Warren wrote:
On 10/30/2014 12:36 AM, Scott Branden wrote:
Add a verify option to driver to print out an error message if a
potential back to back write could cause a clock domain issue.
index f8c450a..11af27f 100644
On 11/05/2014 04:45 PM, Matthias Klein wrote:
The model B and B+ differ in the GPIO lines for ACT and PWR leds, and the
I2S interface.
Tested-by: Stephen Warren swar...@nvidia.com
(On a model B rev 2, UART, SD card, and enumeration of built-in USB
devices works fine)
Lee, how do you want
On 11/05/2014 04:45 PM, Matthias Klein wrote:
The model B and B+ differ in the GPIO lines for ACT and PWR leds, and the
I2S interface.
BTW, according to:
http://raspberryalphaomega.org.uk/2013/02/06/automatic-raspberry-pi-board-revision-detection-model-a-b1-and-b2/
... there are actually 2
On 10/30/2014 12:36 AM, Scott Branden wrote:
> SDHCI_QUIRK_MULTIBLOCK_READ_ACMD12 is missing and needed for this controller.
This seems fine, although any explanation of why this quirk is needed
would be useful.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On 10/30/2014 12:36 AM, Scott Branden wrote:
> Add a verify option to driver to print out an error message if a
> potential back to back write could cause a clock domain issue.
> index f8c450a..11af27f 100644
> +#ifdef CONFIG_MMC_SDHCI_BCM2835_VERIFY_WORKAROUND
> + struct sdhci_pltfm_host
On 10/30/2014 12:36 AM, Scott Branden wrote:
> The bcm2835 has clock domain issues when back to back writes to certain
> registers are written. The existing driver works around this issue with
> udelay. A more efficient method is to store the 8 and 16 bit writes
> to the registers affected and
On 10/30/2014 12:36 AM, Scott Branden wrote:
> Make the shift calculations consistent rather than having different
> implementations to calculate the same thing.
> diff --git a/drivers/mmc/host/sdhci-bcm2835.c
> b/drivers/mmc/host/sdhci-bcm2835.c
> +#define REG_OFFSET_IN_BITS(reg) ((reg) << 3 &
601 - 700 of 5773 matches
Mail list logo
