e. As was discussed recently, there's several reasons
why the pinctrl call might fail, and not all are fatal (E.G. pinmux
already setup by bootloader):
http://article.gmane.org/gmane.linux.kernel/1399756
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe l
then we can reasonably assume that
Thierry> your second case can't happen, can't we?
Well, peripherals only need pinmuxing if the bootloader didn't already
set it up in advance. We could naturally enforce people to add
"redundant" pinmux info to their .dts files, but
hanks for CC'ing me. I also think da850-* should be
documented. See Documentation/devicetree/bindings/gpio/8xxx_gpio.txt for
an similar (old) example.
--
Bye, Peter Korsgaard
--
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/
wonder what was the point of adding it.
Sorry, don't recall. It's been quite a while, and I've haven't worked on
anything mpc8xxx for a few years by now. Most likely one of the other
gpio drivers did it like this back then.
I don't remember the details, but your description
>>>>> "Philip" == Philip Avinash writes:
Philip> DT field of "interrupts" was mentioned wrongly as "interrupt" in SPI
Philip> node. This went unnoticed as spi-omap2 driver not making use of
Philip> interrupt. Fixes the typo.
Philip>
>>>>> "Philip" == Philip Avinash writes:
Philip> As part of removing generalized dependency, replace
Philip> literal fields in DT compatible field with <52> for am335x
Philip> platforms.
Acked-by: Peter Korsgaard
--
Bye, Peter Korsgaard
--
To u
and not the more standard ~70 chars?
It would be good with some more detailed commit text. Is the flush done
somewhere else now? What happens on boards where you don't use the adc
part?
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel&
wires on touchscreen.
ti,wires seems redundant given ti,wire-config (E.G. number of elements
in array). It is not clear to me what the magic values in wire-config
mean?
P> +
P> +adc:
P> +- ti,adc-channels: Number of ADC channels used.
Is there ever any use case for this being something e
- mac-address : Specifies slave MAC address
Pantelis> +- disable-napi : Disables driver NAPI
napi is not a hardware feature, so it doesn't belong here (if anything,
it should be linux,disable-napi).
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "un
introduction mail:
1. ARMv7, 1.5GHz based board
Kernel: linux 3.4
Uncompressed Kernel Size: 14MB
Compressed Size Decompression Speed
LZO 6.7MB21.1MB/s
LZ4 7.3MB29.1MB/s, 45.6MB/s(UA)
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line
nterrupt-parent should be removed from the example as well to
>> match am33xx.dtsi
Matt> On second thought, I'm not sure we're going to get any direction
Matt> on this one so let's just do what feels right and make it reflect
Matt> common usage like you suggested.
Soun
hardware block is identical the dts should simply list:
compatible = "ti,da850-ecap", "ti,am33xx-ecap"
And the driver only bind to ti,am33xx-ecap (unless there ever needs to
be a da850 specific workarounde.
--
Bye, Peter Korsgaard
--
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/
status = "disabled";
P> };
P> + ehrpwm0: ehrpwm@01f0 {
P> + compatible = "ti,da850-ehrpwm";
This should be:
compatible = "ti,da850-ehrpwm", "ti,am33xx-ehrpwm";
P> + e
>>>>> "KC" == Kees Cook writes:
KC> This config item has not carried much meaning for a while now and is
KC> almost always enabled by default. As agreed during the Linux kernel
KC> summit, remove it.
Acked-by: Peter Korsgaard
KC> CC: Stephen Warren
KC&
at internally
Andreas> still uses platform_get_resource.
I have no idea why sparc is being odd in this regard, but assuming this
is how it's done, I'm fine with this change.
A quick grep doesn't find any other drivers doing this though:
git grep -l archdata.irqs drivers | xargs grep platform_ge
c-ocores.c
Andreas> +++ b/drivers/i2c/busses/i2c-ocores.c
Andreas> @@ -4,6 +4,9 @@
Andreas> *
Andreas> * Peter Korsgaard
Andreas> *
Andreas> + * Support for the GRLIB port of the controller by
Andreas> + * Andreas Larsson
Andreas> + *
Andreas> * This file
forms that
Andreas> have ioread/write32, but not ioread/write32be are frv and mn10300. Do
Andreas> you know if those platforms are using i2c-ocores?
Not to my knowledge, no. In that case:
Acked-by: Peter Korsgaard
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the li
>>>>> "Maxin" == Maxin B John writes:
Maxin> Fixes the wrong filename.
Maxin> Signed-off-by: Maxin B. John
Acked-by: Peter Korsgaard
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
>>>>> "Maxin" == Maxin B John writes:
Maxin> This drops a few lines of code and allows common APIs to handle
Maxin> those for us.
Maxin> Signed-off-by: Maxin B. John
Acked-by: Peter Korsgaard
--
Bye, Peter Korsgaard
--
To unsubscribe from this list
another error code. This error should be passed further
IN> instead of being ignored.
Two different fixes, so should be 2 separate patches. Other that that,
it looks good.
Acked-by: Peter Korsgaard
--
Sorry about disclaimer - It's out of my control.
Bye, Peter Korsgaard
This message is sub
>>>>> "IN" == Ionut Nicu writes:
IN> If the i2c-parent bus driver is not loaded, returning
IN> -EINVAL will force people to unload and then reload the
IN> module again to get it working.
IN> Signed-off-by: Ionut Nicu
Acked-by: Peter Korsgaard
--
So
>>>>> "IN" == Ionut Nicu writes:
IN> of_get_named_gpio could return -E_PROBE_DEFER or another
IN> error code. This error should be passed further instead
IN> of being ignored.
Acked-by: Peter Korsgaard
--
Sorry about disclaimer - It's out of my contro
>>
>> Signed-off-by: Ionut Nicu
WS> Doesn't the non-DT case need fixing, too?
Arguably yes.
--
Bye, Peter Korsgaard
This message is subject to the following terms and conditions: MAIL
DISCLAIMER<http://www.barco.com/en/maildisclaimer>
--
To unsubscribe from this li
>>>>> "IN" == Ionut Nicu writes:
IN> If the i2c-parent bus driver is not loaded, returning
IN> -ENODEV will force people to unload and then reload the
IN> module again to get it working.
IN> Signed-off-by: Ionut Nicu
Acked-by: Peter Korsgaard
--
So
>>>>> "Maxin" == Maxin B John writes:
Maxin> Hi Peter,
Maxin> This drops a few lines of code and allows common APIs to handle
Maxin> those for us.
Maxin> Signed-off-by: Maxin B. John
>> Acked-by: Peter Korsgaard
Maxin> Is there any upda
/ TYPE_GRLIB) and a 2nd of_device_id
entry with .data = TYPE_GRLIB, and then using that in the probe routine
would be nicer. Have a look at i2c-at91.c for an example of a driver
doing something like that.
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe
>> example of a driver doing something like that.
Andreas> Yes, that is a good idea. Do you think casting to and from
Andreas> void * in the following solution is too ugly and rather have a
Andreas> struct pointed to, or do you think that would be unnecessary?
I find the castin
; +
Andreas> + match = of_match_node(ocores_i2c_match, pdev->dev.of_node);
Andreas> + if (match)
Andreas> + return (int)match->data;
Can this ever fail? If not, you might as well do the of_match_node
inline in the probe instead of this helper.
Other than that
could even move to a single ops
structure), so it would be shorter to assign them at the same time:
if (!i2c->setreg || !i2c->getreg) {
switch (i2c->reg_io_width) {
case 1:
i2c->setreg = oc_setreg_8;
i2c->getreg = oc_getreg_8;
break;
case 2:
gt; + aic3xxx_free_irq(aic3xxx,
Mehar> +AIC3XXX_IRQ_HEADSET_DETECT, codec);
Mehar> + destroy_workqueue(aic3262->workqueue);
Mehar> +work_err:
Mehar> + kfree(aic3262->cfw_p);
Mehar> + return ret;
Mehar> +}
--
om
Andreas> grlib functions by setting the setreg and getreg function
Andreas> pointers.
Andreas> Signed-off-by: Andreas Larsson
Acked-by: Peter Korsgaard
Thanks!
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
327:12: originally declared
Shubhrajyoti> here
Shubhrajyoti> So delete the u8 tx as it is assigned and not
Shubhrajyoti> used(resigned afterwards).
Shubhrajyoti> Signed-off-by: Shubhrajyoti D
Acked-by: Peter Korsgaard
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send t
usbnet_resume,
Joseph> + .disable_hub_initiated_lpm = 1,
Joseph> +};
Joseph> +
Joseph> +module_usb_driver(dm9620_driver);
Joseph> +
Joseph> +MODULE_AUTHOR("Peter Korsgaard ");
I'm not the author of this file.
--
Bye, Peter Korsgaard
--
To unsubscribe from t
nt compare to DM9601 & DM9620. And will get the same
Joseph> issue.
If you can provide me with a dm9633 datasheet and a sample device then I
can look into writing a driver for it / extending dm9601.c. Please
contact me off list for that.
Thanks!
--
Bye, Peter Korsgaard
--
To unsubscribe
>>>>> "Philip" == Philip Avinash writes:
Philip> Update binding document of pwm-tiecap to reflect the usage of similar
Philip> modules in da850 and am3xx SOCs.
Acked-by: Peter Korsgaard
Philip> Signed-off-by: Philip Avinash
Philip> Cc: Grant Likely
>>>>> "Philip" == Philip Avinash writes:
Philip> Update binding document of pwm-tiehrpwm to reflect the usage of similar
Philip> modules in da850 and am3xx SOCs.
Acked-by: Peter Korsgaard
Philip> Signed-off-by: Philip Avinash
Philip> Cc: Grant Like
any significant work on that
driver since David..
--
Bye, Peter Korsgaard
--
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/
issue for Xorg, but it'd still be a good
Samuel> thing to at last apply it :)
Agreed.
--
Bye, Peter Korsgaard
--
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:
d-off-by: Evan Broder
Looks good to me. Samuel, thanks for picking this up again.
Acked-by: Peter Korsgaard
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo in
t; -#else
>> -#define OCORES_I2C_PM NULL
>> -#endif
>>
>> static struct platform_driver ocores_i2c_driver = {
>> .probe = ocores_i2c_probe,
>> @@ -490,7 +487,7 @@ static struct platform_driver ocores_i2c_driver = {
>> .owner = THIS_MODULE,
>
master is supported"?
Also there's a typo: s/use the claim/use to claim/
--
Bye, Peter Korsgaard
--
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/
he properties in the dts to provide the right values for the
Lars> gpmc driver.
Lars> Signed-off-by: Lars Poeschel
Acked-by: Peter Korsgaard
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord
t; +
Matt> +edma: edma@4900 {
Matt> +reg = <0x4900 0x1>;
Matt> +interrupt-parent = <&intc>;
Matt> +interrupts = <12 13 14>;
Probably interrupt-parent should be removed from the example as well to
match am33xx.dtsi
--
Bye, Pe
Philip>mac-address = [ 00 00 00 00 00 00 ];
Philip>};
Philip>};
Philip> +
Philip> + elm: elm@4808 {
Philip> + compatible = "ti,am33xx-elm";
Please d
ing 7 cs signals, I just realized
the difference in compatible string between the gpmc and elm. The gpmc
refers to a real device (which is afaik how it should be done), but the
elm compatible is simply ti,am33xx-elm.
Presumably it should have been ti,am3352-elm in the binding instead?
Other than that
>>>>> "Michal" == Michal Simek writes:
Michal> Clean coding style and sparse warnings.
Michal> Signed-off-by: Michal Simek
Acked-by: Peter Korsgaard
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel
>>>>> "Michal" == Michal Simek writes:
Michal> Use big and little endian accessors function to reflect system
Michal> configuration. Detection is done via control register in
Michal> ulite_request_port.
Acked-by: Peter Korsgaard
--
Bye, Peter Korsgaar
t 'correctable' misspelled.
I don't personally think these defines improve readability very much
compared to to just using 4/8, though.
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.k
oob 2..53):
http://www.ti.com/litv/pdf/spruh73f
I see the driver in the u-boot-am33x tree (ti81xx_nand.c) seems to use
4x14 bytes as well though, so perhaps that's a bug in the documentation
instead?
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscr
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> + * GNU General Public License for more details.
> + *
> + */
> +
> +#ifndef __ELM_H
> +#define __ELM_H
> +
> +enum bch_ecc {
er)
- Pinmux specified in dt
- Some kind of misconfiguration in dt
You could argue that devm_pinctrl_get_select_default() shouldn't return
an error for the first situation, but how should it be able to know the
difference between 2 and 4?
--
Bye, Peter Korsgaard
--
To unsubscribe from thi
ff-by: Julia Lawall <[EMAIL PROTECTED]>
Acked-by: Peter Korsgaard <[EMAIL PROTECTED]>
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
smc911x_phy_configure's error handling unconditionally unlocks the
spinlock even if it wasn't locked. Patch fixes it.
Signed-off-by: Peter Korsgaard <[EMAIL PROTECTED]>
---
drivers/net/smc911x.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
Index: linux-t
owland <[EMAIL PROTECTED]>
Acked-by: Peter Korsgaard <[EMAIL PROTECTED]>
--
Bye, Peter Korsgaard
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
y.
> Add a minimal driver for it that just claim the needed resources for the
> pipeline to operate properly.
> Signed-off-by: Maxime Ripard
Acked-by: Peter Korsgaard
--
Bye, Peter Korsgaard
>>>>> "Alexey" == Alexey Khoroshilov writes:
> clk_disable_unprepare() is missed on failure paths in ocores_i2c_probe().
> Found by Linux Driver Verification project (linuxtesting.org).
> Signed-off-by: Alexey Khoroshilov
Acked-by: Peter Korsgaard
--
Bye, Peter Korsgaard
ss
> pointers).
As the serial number is available on a separate i2c address, wouldn't
it be simpler to handle these as special (read only) device variants and
instantiate E.G. a 24c64 (for the normal data) and a 24cs64 (for the
serial)?
--
Bye, Peter Korsgaard
--
To unsubscribe from this
t; both memory blocks share the same address pointer.
> I'll resend the series.
But we're protected by the i2c bus lock, right? You do a single
i2c_transfer to read the serial number.
--
Venlig hilsen,
Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscrib
my bad. It needs to be fixed as
>> > both memory blocks share the same address pointer.
>>
>> > I'll resend the series.
>>
>> But we're protected by the i2c bus lock, right? You do a single
>> i2c_transfer to read the serial number.
> Wh
hanks!
> @Peter: since the patch is trivial and nice to have in 4.17 already, I
> took the liberty to apply it right away. Hope this is fine with you.
Sorry for the slow response - Yes it is indeed.
--
Bye, Peter Korsgaard
For some use cases it is handy to use a different printk log level than the
default (info) for the messages written to ttyprintk, so add a Kconfig
option similar to what we have for default console loglevel.
Signed-off-by: Peter Korsgaard
---
drivers/char/Kconfig | 8
drivers/char
it or not.
> Adding Peter to CC using his latest EMail address.
Thanks! I'll take a look at the patches now.
> Peter, you said you wanted to update MAINTAINERs with the new address?
Sorry, I forgot about it when I left on holidays. Will send now.
--
Bye, Peter Korsgaard
/*
> + * This is controlled by GPIOAO_9 we reserve this but
> + * claiming it as done bellow reset the board anyway
The 'bellow' typo is still here?
--
Bye, Peter Korsgaard
>>>>> "Jerome" == Jerome Brunet writes:
> From: Neil Armstrong
> Add Libretech aml-s805x-ac board (aka 'La Frite') support
> Signed-off-by: Neil Armstrong
> Signed-off-by: Jerome Brunet
Reviewed-by: Peter Korsgaard
--
Bye, Peter Korsgaard
we reserve this but
> + * claiming it as done bellow reset the board anyway
s/bellow/below/
> +&spifc {
> +status = "okay";
> +pinctrl-0 = <&nor_pins>;
> +pinctrl-names = "default";
> +
> +w25q32: spi-fla
cryptsetup luksOpen.
As the change was purely cosmetical, revert it to fix such breakage.
Signed-off-by: Peter Korsgaard
---
drivers/firmware/dmi_scan.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/firmware/dmi_scan.c b/drivers/firmware/dmi_scan.c
index
>>>>> "Peter" == Peter Korsgaard writes:
> This reverts commit 712ff25450bd01366301eef81c33e865d901e7b7.
> The output of dmi_save_uuid() is exposed to user space as
> /sys/devices/virtual/dmi/id/*_uuid, so this breaks backwards compatibility,
> E.G. I
>>>>> "Jean" == Jean Delvare writes:
> On Wed, 2018-12-05 at 22:13 +0100, Peter Korsgaard wrote:
>> This reverts commit 712ff25450bd01366301eef81c33e865d901e7b7.
>>
>> The output of dmi_save_uuid() is exposed to user space as
>> /sys/dev
4.19 has only recently become
>> LTS.
> I can't see how this is related with kernel 4.19 becoming LTS.
Only in the sense that that LTS kernels see wider use than non-LTS
kernels (E.G. I discovered this when moving from 4.14.x to 4.19.x).
> Look, you can imagine that I was perfectly aware of what I was doing
> when I made that change, and that I pondered the decision carefully at
> that time. And my decision was that the change should be made. As far
> as I'm concerned, this ship has sailed already, sorry.
Sorry, what is the perceived risk of reverting this change? Just the
minor inconsistency between the dmidecode and sysfs output? As stated
above, the RFC requires conforming parsers to handle upper case as well.
--
Bye, Peter Korsgaard
>>>>> "Peter" == Peter Korsgaard writes:
Hi Jean,
>> Look, you can imagine that I was perfectly aware of what I was doing
>> when I made that change, and that I pondered the decision carefully at
>> that time. And my decision was that the change
>>>>> "Jean" == Jean Delvare writes:
> On Tue, 2018-12-11 at 13:06 +0100, Peter Korsgaard wrote:
>> > > > > > "Peter" == Peter Korsgaard writes:
>>
>> Hi Jean,
>>
>> >> Look, you can imagine
For some use cases it is handy to use a different printk log level than the
default (info) for the messages written to ttyprintk, so add a Kconfig
option similar to what we have for default console loglevel.
Signed-off-by: Peter Korsgaard
---
Changes since v1:
- Leave [U] prefix in printk
s may run in
> atomic context where we can't sleep at all.
Great! BTW I noticed that your sleep_min calculation looked odd:
int sleep_min = (8/i2c->bus_clock_khz) * 1000; /* us for 8bits
bus_clock_khz almost certainly will be bigger than 8 (E.G. likely
100KHz), so the above set sleep_min to 0. Please move the * 1000 before
the division.
--
Bye, Peter Korsgaard
For some use cases it is handy to use a different printk log level than the
default (info) for the messages written to ttyprintk, so add a Kconfig
option similar to what we have for default console loglevel.
Signed-off-by: Peter Korsgaard
---
Changes since v1:
- Leave [U] prefix in printk
For some use cases it is handy to use a different printk log level than the
default (info) for the messages written to ttyprintk, so add a Kconfig
option similar to what we have for default console loglevel.
Signed-off-by: Peter Korsgaard
---
Changes since v1:
- Leave [U] prefix in printk
tion that the hardware is alive and what we read from
> oc_getreg() is correct. With this assumption, when there is a timeout this
> will happen:
> 1. STOP command (previous patch)
> 2. both TIP and BUSY will become zero at some point and we get out from the
> loop
> I can see now that there are cases when it may loop forever: for example if
> the device is broken and it does answer always with 0x: we should not
> break the host as well :)
> I can fix this.
Thanks!
--
Bye, Peter Korsgaard
>>>>> "Federico" == Federico Vaga writes:
Hi,
> I had another look at the HDL code and apparently my assumption was wrong,
> and
> STOP just do stop, and IACK is still necessary.
> So, yes, without try is better because we save an extra, useless,
ng - But I still
don't quite understand this trylock logic. If we end up here with the
lock taken, then that must mean that we are on SMP system. We still
need to ack the interrupt, so just spinning until the other CPU
releases the lock seems more sensible?
--
Bye, Peter Korsgaard
ction
> expects it to be read by the caller.
>
> Signed-off-by: Federico Vaga
Looks good.
Acked-by: Peter Korsgaard
--
Bye, Peter Korsgaard
_CTRL_IEN);
> + oc_setreg(i2c, OCI2C_CONTROL, ctrl);
This looks unrelated to $SUBJECT
>
> prescale = (i2c->ip_clock_khz / (5 * i2c->bus_clock_khz)) - 1;
> prescale = clamp(prescale, 0, 0x);
> @@ -277,12 +332,16 @@ static int ocores_init(struct device *dev, struct
> ocores_i2c *i2c)
> return -EINVAL;
> }
>
> +
Here as well.
> @@ -538,6 +600,8 @@ static int ocores_i2c_remove(struct platform_device *pdev)
> {
> struct ocores_i2c *i2c = platform_get_drvdata(pdev);
>
> + flush_scheduled_work();
> +
Why not cancel_work_sync(&i2c->xfer_work)?
--
Bye, Peter Korsgaard
On Fri, Sep 7, 2018 at 10:18 AM Peter Korsgaard wrote:
>
> For some use cases it is handy to use a different printk log level than the
> default (info) for the messages written to ttyprintk, so add a Kconfig
> option similar to what we have for default console loglevel.
>
> Si
iew since April 2014!
Hah, I'm pretty sure it dates back to 2010 atleast.
--
Bye, Peter Korsgaard
--
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/
the history, the device tree patch originally used a
custom "clock_khz" property until some guy told him to use
clock-frequency ;)
https://lists.ozlabs.org/pipermail/devicetree-discuss/2010-November/003650.html
As far as I can see I wasn't CC'ed on that patch.
--
Bye, Peter Korsg
>>>>> "Max" == Max Filippov writes:
> Allow bus clock specification as a common clock handle. This makes this
> controller easier to use in a setup based on common clock framework.
> Signed-off-by: Max Filippov
Looks sensible to me - Thanks.
Acked-by
>>>>> "Ricardo" == Ricardo Ribalda Delgado writes:
> This way we do not need to transverse the device tree manually.
> Cc: Linus Walleij
> Cc: Alexandre Courbot
> Cc: Grant Likely
> Cc: Rob Herring
> Cc: Peter Korsgaard
> Cc: device
>>>>> "Ricardo" == Ricardo Ribalda Delgado writes:
> This way we do not need to transverse the device tree manually.
> Cc: Linus Walleij
> Cc: Alexandre Courbot
> Cc: Grant Likely
> Cc: Rob Herring
> Cc: Peter Korsgaard
> Cc: device
Walleij
> Cc: Alexandre Courbot
> Cc: Peter Korsgaard
> Signed-off-by: Ricardo Ribalda Delgado
> ---
> drivers/gpio/gpio-mpc8xxx.c | 28 +++-
> 1 file changed, 23 insertions(+), 5 deletions(-)
> diff --git a/drivers/gpio/gpio-mpc8xxx.c b/
message when a driver
>> requests probe deferral, so this can be traced in the logs
>> without these error prints.
>>
>> This patch removes the error messages for these deferral cases.
>>
>> Signed-off-by: Ionut Nicu
AS> Acked-by: Alexander Sverdlin
Acked-by:
The IRQF_SAMPLE_RANDOM
Theodore> flag was scheduled to be removed in 2009 on the
Theodore> feature-removal-schedule, so this patch is preparation for the final
Theodore> removal of this flag.
Theodore> Signed-off-by: "Theodore Ts'o"
Theodore> Cc: Peter K
gt; is defined on the command line.
> What happens in my case is console_on_rootfs() doesn't find
> /dev/console and switching to ttynull. /dev is not present because
> devtmpfs doesn't automount for initramfs.
But our initramfs/cpio logic ensures that the initramfs has a static
/dev/console device node, so how can that be?
https://git.buildroot.net/buildroot/tree/fs/cpio/cpio.mk#n25
--
Bye, Peter Korsgaard
>>>>> "Jingoo" == Jingoo Han writes:
> Use devm_clk_get() to make cleanup paths simpler.
> Signed-off-by: Jingoo Han
Acked-by: Peter Korsgaard
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel
>>>>> "Jingoo" == Jingoo Han writes:
> Use devm_ioremap_resource() in order to make the code simpler,
> and remove redundant return value check of platform_get_resource()
> because the value is checked by devm_ioremap_resource().
> Signed-off-by: J
ashfs/cramfs/readonly ext2/.. on a NOR flash?
--
Bye, Peter Korsgaard
--
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/
ta.n_gpios; i++)
IN> - gpio_set_value(mux->gpio_base + mux->data.gpios[i],
IN> - val & (1 << i));
IN> + gpio_set_value_cansleep(mux->gpio_base + mux->data.gpios[i],
IN> + val & (1 << i
>>>>> "Boris" == Boris Brezillon writes:
> Use clk_prepapre_enable/_disable_unprepare instead of clk_enable/disable
> to work properly with the CCF.
s/prepapre/prepare/
Other than that, looks fine to me.
Acked-by: Peter Korsgaard
> Signed-off-by: Boris
>>>>> "Boris" == Boris Brezillon writes:
> Add DT support.
> Make the driver depend on CONFIG_OF as at91sam9g45 was the only SoC making
> use of the TRNG block and this SoC is now fully migrated to DT.
> Signed-off-by: Boris Brezillon
Acked-by: Peter
h of the register set of this block
> +- interrupts : the interrupt number for the TRNG block
The interrupt isn't strictly speaking required as it isn't used by the
driver, but as 9G45 has the signal wired up I guess it makes sense.
Acked-by: Peter Korsgaard
--
Bye, Peter Korsg
der to wait for data as
> requested by hwrng code when the wait argument is true).
> Thus I prefer to keep it as required.
Ok, fine by me.
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.k
eak after some time.
> Signed-off-by: Wolfram Sang
Acked-by: Peter Korsgaard
--
Bye, Peter Korsgaard
--
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/
= 0; i < 10; i++) {
It would be good to add a note about the slow jtag variant here.
Otherwise:
Acked-by: Peter Korsgaard
> +timeout = jiffies + msecs_to_jiffies(1000);
> +while (1) {
> val = uart_in32(ULITE_STATUS, port);
>
1 - 100 of 141 matches
Mail list logo
