From: Geert Uytterhoeven <geert@linux-m68k.org> To: linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] [RFC] ARM: shmobile: Add early debugging support using SCIF(A) Date: Mon, 06 Oct 2014 09:18:10 +0000 [thread overview] Message-ID: <CAMuHMdWm=4zqgUXypLZtck1=vx7S7nBtn_cBr32ODViccOY3cA@mail.gmail.com> (raw) In-Reply-To: <CANqRtoTJNb7a9J05U0chrGoxBV7e1s6o0Xxeup0p1sOUZhE+vA@mail.gmail.com> Hi Magnus, On Mon, Oct 6, 2014 at 1:36 AM, Magnus Damm <magnus.damm@gmail.com> wrote: >> - On armadillo-multiplatform there may be a period while garbage data >> is output. >> This happens because sh_mobile_i2c_init() enables and disables its >> clock during probing. As iic0 and scifa1 share the same parent >> clock, this causes the scifa1 clock to no longer receive clock >> ticks. >> On armadillo-legacy, this is mitigated by the pre-CCF clock driver, >> which never really disables clocks during boot-up for exactly this >> reason. Cfr. "One example of this is the handling of the Mackerel >> serial console output that shares clock with the I2C controller.", >> in commit 794d78fea51504ba ("drivers: sh: late disabling of clocks >> V2"). >> I'm wondering whether this can be fixed in the i2c driver? Does it >> really have to enable and disable the clock? > > I've seen this issue on several SoCs actually, and as you describe the > main issue seems to be that there are clock topologies that present > for devices used during boot (like serial) but this clock topology is > not yet managed by software. This does not trigger on all SoCs though. To work perfectly, (a) everything must be described correctly in DT, and (b) this information must be used correctly. IMHO we can live with the deficiencies for DEBUG_LL. > It is my opinion that it has very little todo with the other devices > that happen to be using the same parent clock. The legacy clock > framework solved this by not allowing clocks to be disabled until all > devices were registered. Not allowing clocks to be disabled until all devices were registered has its own problems (some hardware requires disabling clocks for various reasons). A similar horse is currently being beaten to death in the "simplefb" threads... Read on if you feel bored ;-) Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
From: geert@linux-m68k.org (Geert Uytterhoeven) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] [RFC] ARM: shmobile: Add early debugging support using SCIF(A) Date: Mon, 6 Oct 2014 11:18:10 +0200 [thread overview] Message-ID: <CAMuHMdWm=4zqgUXypLZtck1=vx7S7nBtn_cBr32ODViccOY3cA@mail.gmail.com> (raw) In-Reply-To: <CANqRtoTJNb7a9J05U0chrGoxBV7e1s6o0Xxeup0p1sOUZhE+vA@mail.gmail.com> Hi Magnus, On Mon, Oct 6, 2014 at 1:36 AM, Magnus Damm <magnus.damm@gmail.com> wrote: >> - On armadillo-multiplatform there may be a period while garbage data >> is output. >> This happens because sh_mobile_i2c_init() enables and disables its >> clock during probing. As iic0 and scifa1 share the same parent >> clock, this causes the scifa1 clock to no longer receive clock >> ticks. >> On armadillo-legacy, this is mitigated by the pre-CCF clock driver, >> which never really disables clocks during boot-up for exactly this >> reason. Cfr. "One example of this is the handling of the Mackerel >> serial console output that shares clock with the I2C controller.", >> in commit 794d78fea51504ba ("drivers: sh: late disabling of clocks >> V2"). >> I'm wondering whether this can be fixed in the i2c driver? Does it >> really have to enable and disable the clock? > > I've seen this issue on several SoCs actually, and as you describe the > main issue seems to be that there are clock topologies that present > for devices used during boot (like serial) but this clock topology is > not yet managed by software. This does not trigger on all SoCs though. To work perfectly, (a) everything must be described correctly in DT, and (b) this information must be used correctly. IMHO we can live with the deficiencies for DEBUG_LL. > It is my opinion that it has very little todo with the other devices > that happen to be using the same parent clock. The legacy clock > framework solved this by not allowing clocks to be disabled until all > devices were registered. Not allowing clocks to be disabled until all devices were registered has its own problems (some hardware requires disabling clocks for various reasons). A similar horse is currently being beaten to death in the "simplefb" threads... Read on if you feel bored ;-) Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
next prev parent reply other threads:[~2014-10-06 9:18 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-02 19:02 [PATCH] [RFC] ARM: shmobile: Add early debugging support using SCIF(A) Geert Uytterhoeven 2014-10-02 19:02 ` Geert Uytterhoeven 2014-10-03 0:04 ` Khiem Nguyen 2014-10-03 0:04 ` Khiem Nguyen 2014-10-03 7:21 ` Geert Uytterhoeven 2014-10-03 7:21 ` Geert Uytterhoeven 2014-10-03 10:19 ` Khiem Nguyen 2014-10-03 10:19 ` Khiem Nguyen 2014-10-03 11:28 ` Geert Uytterhoeven 2014-10-03 11:28 ` Geert Uytterhoeven 2014-10-05 22:18 ` Laurent Pinchart 2014-10-05 22:18 ` Laurent Pinchart 2014-10-06 6:03 ` Wolfram Sang 2014-10-06 6:03 ` Wolfram Sang 2014-10-06 6:14 ` Magnus Damm 2014-10-06 6:14 ` Magnus Damm 2014-10-06 8:56 ` Geert Uytterhoeven 2014-10-06 8:56 ` Geert Uytterhoeven 2014-10-06 9:01 ` Wolfram Sang 2014-10-06 9:01 ` Wolfram Sang 2014-10-06 9:08 ` Geert Uytterhoeven 2014-10-06 9:08 ` Geert Uytterhoeven 2014-10-07 10:37 ` Ian Molton 2014-10-07 10:37 ` Ian Molton 2014-10-07 11:07 ` Geert Uytterhoeven 2014-10-07 11:07 ` Geert Uytterhoeven 2014-10-07 12:39 ` Geert Uytterhoeven 2014-10-07 12:39 ` Geert Uytterhoeven 2014-10-05 23:36 ` Magnus Damm 2014-10-05 23:36 ` Magnus Damm 2014-10-06 9:18 ` Geert Uytterhoeven [this message] 2014-10-06 9:18 ` Geert Uytterhoeven 2014-10-07 10:49 ` Arnd Bergmann 2014-10-07 10:49 ` Arnd Bergmann 2014-10-07 11:46 ` Geert Uytterhoeven 2014-10-07 11:46 ` Geert Uytterhoeven
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAMuHMdWm=4zqgUXypLZtck1=vx7S7nBtn_cBr32ODViccOY3cA@mail.gmail.com' \ --to=geert@linux-m68k.org \ --cc=linux-arm-kernel@lists.infradead.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.