diff for duplicates of <200905190947.22972.kosmo@semihalf.com> diff --git a/a/1.txt b/N1/1.txt index 7e7d86b..a02a906 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,18 +1,20 @@ -Monday 18 May 2009 16:29:04 Wolfgang Grandegger napisał(a): +Monday 18 May 2009 16:29:04 Wolfgang Grandegger napisa=B3(a): > > I have simple question about bus speed setting support. Existing > > implementation uses default safe speed if there is no 'clock-frequency' > > property in i2c node. Comments in code suggest that this behaviour is -> > left for backward compatibility only. Should I make the 'clock-frequency' +> > left for backward compatibility only. Should I make the 'clock-frequenc= +y' > > property mandatory for a new type of I2C controller (MPC5121) ? > > I don't think so, for the same backward compatibility reason as for the > other boards. But the DTS file might be changed to use clock-frequency. In my opinion implementing "backward compatilility" for MPC5121 is not good -idea. MPC5121 I2C support is completly new thing in mainline. Simply, there is +idea. MPC5121 I2C support is completly new thing in mainline. Simply, there= + is=20 no DTS with which I have to be compatible. Adding backward compatibility with nothing may be confusing. --- +=2D-=20 Best Regards, -Piotr Zięcik +Piotr Zi=EAcik diff --git a/a/content_digest b/N1/content_digest index 4634b97..811adb6 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,35 +1,35 @@ "ref\01241640919-4650-1-git-send-email-wd@denx.de\0" "ref\0200905181557.11766.kosmo@semihalf.com\0" "ref\04A1170B0.5080203@grandegger.com\0" - "ref\04A1170B0.5080203-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org\0" - "From\0Piotr Zi\304\231cik <kosmo-nYOzD4b6Jr9Wk0Htik3J/w@public.gmane.org>\0" + "From\0Piotr Zi\304\231cik <kosmo@semihalf.com>\0" "Subject\0Re: [PATCH 08/12] mpc5121: Added I2C support.\0" "Date\0Tue, 19 May 2009 09:47:22 +0200\0" - "To\0Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>\0" - "Cc\0Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>" - Wolfgang Denk <wd-ynQEQJNshbs@public.gmane.org> - linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org - Detlev Zundel <dzu-ynQEQJNshbs@public.gmane.org> - " linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\0" + "To\0Wolfgang Grandegger <wg@grandegger.com>\0" + "Cc\0linuxppc-dev@ozlabs.org" + Wolfgang Denk <wd@denx.de> + Detlev Zundel <dzu@denx.de> + " linux-i2c@vger.kernel.org\0" "\00:1\0" "b\0" - "Monday 18 May 2009 16:29:04 Wolfgang Grandegger napisa\305\202(a):\n" + "Monday 18 May 2009 16:29:04 Wolfgang Grandegger napisa=B3(a):\n" "> > I have simple question about bus speed setting support. Existing\n" "> > implementation uses default safe speed if there is no 'clock-frequency'\n" "> > property in i2c node. Comments in code suggest that this behaviour is\n" - "> > left for backward compatibility only. Should I make the 'clock-frequency'\n" + "> > left for backward compatibility only. Should I make the 'clock-frequenc=\n" + "y'\n" "> > property mandatory for a new type of I2C controller (MPC5121) ?\n" ">\n" "> I don't think so, for the same backward compatibility reason as for the\n" "> other boards. But the DTS file might be changed to use clock-frequency.\n" "\n" "In my opinion implementing \"backward compatilility\" for MPC5121 is not good\n" - "idea. MPC5121 I2C support is completly new thing in mainline. Simply, there is \n" + "idea. MPC5121 I2C support is completly new thing in mainline. Simply, there=\n" + " is=20\n" "no DTS with which I have to be compatible. Adding backward compatibility\n" "with nothing may be confusing.\n" "\n" - "-- \n" + "=2D-=20\n" "Best Regards,\n" - "Piotr Zi\304\231cik" + Piotr Zi=EAcik -f6b27a168954acf299bb273c617c9fba2772f8b5168586aa7d328dd96841f628 +332b78b53490a9749eca7d4f84a8d8acb452ccb7a0e736ee0a5ab825210e4ba7
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.