directory
> +- #pwm-cells: Should be 3. See pwm.yaml in this directory
>for a description of the cell format.
> - interrupts: one interrupt per PWM channel
For the SiFive PWM driver documentation:
Acked-by: Paul Walmsley
- Paul
Hi folks
just a brief comment on this one:
On Thu, 30 Apr 2015, Boris Brezillon wrote:
> Clock rates are stored in an unsigned long field, but ->round_rate()
> (which returns a rounded rate from a requested one) returns a long
> value (errors are reported using negative error codes), which can l
Hi Daniel,
On 05/12/2015 03:06 AM, Daniel Stone wrote:
> Hi Paul,
>
> On 12 May 2015 at 05:00, Paul Walmsley wrote:
>> Tegra124 Jetson TK1 hangs during boot in next-20150508 and beyond:
>>
>> http://nvt.pwsan.com/experimental/linux-next/testlogs/test_next-20150508/2
Hi folks
Tegra124 Jetson TK1 hangs during boot in next-20150508 and beyond:
http://nvt.pwsan.com/experimental/linux-next/testlogs/test_next-20150508/20150508101018/boot/tegra124-jetson-tk1/tegra124-jetson-tk1/tegra_defconfig_log.txt
http://nvt.pwsan.com/experimental/linux-next/testlogs/test_ne
;, "nvidia,tegra20-pcie"' where
is tegra30, tegra132, ..." [...] "You should attempt to
document known values of if you use it"
Signed-off-by: Paul Walmsley
Cc: Alexandre Courbot
Cc: Dylan Reid
Cc: Eduardo Valentin
Cc: Greg Kroah-Hartman
Cc: Hans de Goede
Cc: I
Add compatible strings for the SOR IP blocks present on several Tegra
chips. The primary objective here is to avoid checkpatch warnings,
per:
http://marc.info/?l=linux-tegra&m=142201349727836&w=2
Signed-off-by: Paul Walmsley
Cc: Thierry Reding
Cc: "Terje Bergström"
C
On Wed, 11 Dec 2013, Thierry Reding wrote:
> Perhaps unsigned long long would be a better choice for future
> compatibility?
Yes - at this point am planning to go straight to u64.
- Paul
On 12/10/2013 11:51 PM, Sascha Hauer wrote:
> On Mon, Dec 09, 2013 at 06:00:12PM -0800, Paul Walmsley wrote:
>> Treat both negative and zero return values from clk_round_rate() as
>> errors. This is needed since subsequent patches will convert
>> clk_round_rate()'s retu
ually, when calling clk_round_rate(), only a return value of zero
will be considered a error. All other values will be considered valid
rates. The comparison against values less than 0 is kept to preserve
the correct behavior in the meantime.
Signed-off-by: Paul Walmsley
Cc: Mikko Perttunen
Cc: