lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 28 Jul 2014 09:58:22 -0700
From:	Olof Johansson <>
To:	caesar <>
Cc:	Doug Anderson <>,
	Thierry Reding <>,,
	"" <>,
	"" <>,
	"" <>
Subject: Re: [PATCH v2 2/2] pwm: add this patch to support the new pwm of
 Rockchip SoCs

On Mon, Jul 28, 2014 at 4:19 AM, caesar <> wrote:
> Doug,
> 在 2014年07月28日 12:01, Doug Anderson 写道:
>> Caesar,
>> On Sun, Jul 27, 2014 at 7:00 AM, caesar <>
>> wrote:
>>> /*I think will be show the faill log:->
>>> * rockchip-pwm ff9301a0.pwm: can't request region for resource [mem
>>> 0xff9301a0-0xff93019f]
>>> */
>>> pc->base = devm_ioremap_resource(dev, regs);
>> Did you actually code this up and try it and get this error?
> Yeah.
>> I hadn't
>> tried it but I researched other dts files and it looked as if there
>> was one example that was doing this.  ...but perhaps it wasn't
>> actually doing the ioremap_resource on both ranges.
>> I'd imagine that this is _probably_ equivalent to what Thierry was
>> suggesting, so if it didn't work then maybe Thierry's won't work
>> either?
>> I don't have any other great suggestions other than doing two memory
>> ranges for lcdc:
>>           lcdc@...30000 {
>>                   compatible = "rockchip,rk3288-lcdc";
>>                   reg = <0xff930000 0x1a0>, <0xff9301b0 0xfe50>;
>>                   ...
>>           };
>>           pwm@...301a0 {
>>                   compatible = "rockchip,vop-pwm";
>>                   reg = <0xff9301a0 0x10>;
>>                   ...
>>           };
>> ...but I am certainly nowhere near an expert on this stuff...
>> -Doug
> I has solve in lcdc driver,but I always feel awkward. I think a good way to
> solve in pwm driver.
> Unfortunately that  so far ,I have not a good idle in pwm driver.
> Maybe,I  let do it that way in lcdc driver.

I think there's an easier way to do this, by not focusing _too_ much
on the device tree:

* Define a platform_data structure for the PWM driver, which contains
readl/writel accessors as well as the device type (i.e. what you use
the compatible field and the lookup table for today).
* Populate the platform_device in the clcd driver, and register that
* Make the PWM driver probe as a regular platform device if pdata is passed
* Make a readl/writel wrapper that either falls back to native
readl/writel when there aren't any passed in, or make the DT code fill
in the pdata with the native versions in that case.

Going full MFD on this seems overkill, unless there is also a shared
interrupt that needs to be handled.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists