From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Valentin Longchamp
<valentin.longchamp-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
Cc: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
Linux PowerPC Kernel
<linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Linux device trees
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Brunck,
Holger" <Holger.Brunck-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>,
"Boschung,
Rainer" <Rainer.Boschung-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH] i2c-qoriq: modified compatibility for correct prescaler
Date: Fri, 14 Nov 2014 09:28:33 +0100 [thread overview]
Message-ID: <20141114082832.GA2180@katana> (raw)
In-Reply-To: <5465B285.7070005-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
> >
> > If we're going to change the device tree I'd rather just add a property
> > to say what the prescaler is.
>
> We would however, leave the boards' device trees that use things like
> "fsl,mpc8543-i2c" as is and introduce the prescaler for the others requiring it.
>
>
> Now the drawback is that the driver would require a change, to parse this
> prescaler new prescaler property. Would this be OK from your point of view
> Wolfram ? If yes, I will send the patches for it.
I don't think it is OK. I'd think it can be deduced from the compatible
property. Let's ask the DT experts here. I'll follow their suggestion.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-14 8:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 9:27 [PATCH] i2c-qoriq: modified compatibility for correct prescaler Valentin Longchamp
[not found] ` <1413538026-15739-1-git-send-email-valentin.longchamp-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2014-10-28 23:08 ` Scott Wood
2014-10-29 8:59 ` Valentin Longchamp
[not found] ` <5450AC85.40302-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2014-11-06 21:58 ` Scott Wood
2014-11-13 0:34 ` Wolfram Sang
2014-11-14 7:43 ` Valentin Longchamp
[not found] ` <5465B285.7070005-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2014-11-14 8:28 ` Wolfram Sang [this message]
2014-11-18 1:28 ` Scott Wood
[not found] ` <1416274083.15957.96.camel-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-11-25 18:13 ` Wolfram Sang
2014-11-26 1:41 ` Scott Wood
[not found] ` <1416966097.15957.171.camel-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-11-30 4:30 ` Danielle Costantino
[not found] ` <CAAVjN7fJyOh64p5UGRmv-UTnF47cERDfbHyHTuzQmQj8xTDEOQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-01 17:23 ` Wolfram Sang
2014-12-11 13:44 ` Valentin Longchamp
[not found] ` <54899FB4.9010207-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2014-12-23 13:23 ` Valentin Longchamp
[not found] ` <54996CB5.8030808-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2014-12-23 13:49 ` Wolfram Sang
2014-12-27 2:43 ` Scott Wood
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=20141114082832.GA2180@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=Holger.Brunck-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org \
--cc=Rainer.Boschung-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=valentin.longchamp-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).